00:16:22 i'm partly here because I maintain a package build script for an OS... but can anyone inform me if ##crawl gets quick notifications/topics of version updates? In that case I wouldn't need to be here unless getting help compiling to make the build script... 00:18:08 DarwinElf: no, I don't think we do notifications in ##crawl about version updates aside from individual trunk commits 00:18:18 the Cheibriados bot puts commits to trunk in that channel 00:19:12 but you could get the release info from github, as we always tag releases there 00:19:23 and announce them on crawl.develz.org/wordpress as well 00:19:25 in github, you can choose to watch "Releases Only" for a repository 00:19:32 you'll get an email any time a release is made 00:19:36 i may be subscribed to that but there's so much other talk, and I didn't always notice a version number in the topic... 00:19:43 oh... 00:19:46 yes, but we haven't historically done github releases 00:19:52 we did for 0.23 but not for 0.24 00:20:07 and 0.23 was the first one we ever did 00:20:57 it's something we could add to the release process, I suppose (making github releases), but if you just want to check for new releases, probably checking github for tags of the form of 0.XX? 00:20:57 what OS btw? 00:21:07 I'm not sure if you're trying to automate this, or something 00:21:19 i also have a tool, Project Version Checker (pvc, by Christoph Willing) that might be able to be configured to let me know... but it'd need a URL where releases are posted... 00:21:33 the tag is definitely made for every release no matter what 00:21:36 here 00:21:51 Slackware GNU/Linux. Well I just want to find out a.s.a.p. so I can download it and make the next build 00:22:11 DarwinElf: https://github.com/crawl/crawl/tags for tags that are not -a0 nor -b1 00:22:20 tags without those suffixes with be major or point releases 00:22:46 and of course you can just fetch tags from the actual github repo 00:23:03 for github releases specifically, we haven't reliably been doing that, but the tag we absolute do every release (our infrastructure and release process relies on it, so we must) 00:23:23 actually pvc informed me of 0.24... just it's a manual shell command 00:25:25 i must say though, my build is unofficial, at the quasi-official site SlackBuilds.org 00:26:12 wi was just about to ask :) 00:26:36 the package format seems very similar to the bsds, very simple 00:47:42 -!- amalloy_ is now known as amalloy 02:09:21 Windows builds of master branch on crawl.develz.org updated to: 0.25-a0-404-gc1b5a34 02:48:44 Monster database of master branch on crawl.develz.org updated to: 0.24-a0-443-g80245de 03:11:51 Unstable branch on crawl.beRotato.org updated to: 0.25-a0-404-gc1b5a34 (34) 03:52:08 -!- adibis is now known as aditya 08:09:38 03theJollySin02 07https://github.com/crawl/crawl/pull/1254 * 0.25-a0-366-g30272b2: Added some new arrival vaults 10(5 days ago, 2 files, 168+ 0-) 13https://github.com/crawl/crawl/commit/30272b2cfe13 08:09:38 03theJollySin02 07https://github.com/crawl/crawl/pull/1254 * 0.25-a0-367-gb60670a: Adding unstated arrival guideline via Ebering 10(12 hours ago, 1 file, 2+ 0-) 13https://github.com/crawl/crawl/commit/b60670a0f516 08:09:38 03theJollySin02 07https://github.com/crawl/crawl/pull/1254 * 0.25-a0-368-g3de2a78: Fixing outdated file reference 10(3 days ago, 1 file, 1+ 1-) 13https://github.com/crawl/crawl/commit/3de2a78b6803 09:28:30 Sinbi (L27 GrFi) ERROR: range check error (27000 / 2000) (Depths:3) 11:23:37 Stable (0.23) branch on underhound.eu updated to: 0.23.1-91-gf373564dc4 11:57:00 -!- amalloy is now known as amalloy_ 12:32:55 -!- amalloy_ is now known as amalloy 12:37:16 -!- jfcaron__ is now known as jfcaron 14:58:46 -!- Tiobot is now known as Guest89509 20:14:52 -!- amalloy is now known as amalloy_ 20:36:39 -!- amalloy_ is now known as amalloy 22:28:49 03Alex Jurkiewicz02 07https://github.com/crawl/crawl/pull/1253 * 0.25-a0-411-g8a22161: webtiles: Improve load_games documentation 10(2 days ago, 1 file, 20+ 10-) 13https://github.com/crawl/crawl/commit/8a22161c0811