Log for #openttdcoop.devzone on 17th September 2013:
Times are UTC Toggle Colours
03:29:33  *** Supercheese has quit IRC
06:07:03  *** Zuu has joined #openttdcoop.devzone
06:30:38  *** KenjiE20 has quit IRC
06:31:53  *** zooks has joined #openttdcoop.devzone
07:52:27  <Brot6> Bug #6415: Disabling fences-switch Xkyosuke1989X @
07:53:28  <Brot6> Feature #6416 (New): Level crossing overlay tracks for each railtype Xkyosuke1989X @
07:56:28  <Brot6> Feature #6417 (New): Sand-based wood sleeper rail graphics modification Xkyosuke1989X @
09:29:08  <Brot6> Feature #6417 (Closed): Sand-based wood sleeper rail graphics modification Xkyosuke1989X @
09:29:08  <Brot6> Feature #6417 (Closed): Sand-based wood sleeper rail graphics modification Xjuzza1X @
09:33:44  <Brot6> Feature #6416: Level crossing overlay tracks for each railtype Xjuzza1X @
09:48:01  <Brot6> Feature #6418 (Confirmed): Snow-aware level crossings Xjuzza1X @
10:18:04  *** KenjiE20 has joined #openttdcoop.devzone
11:10:02  <DevZone> Project Finnish Rail Infrastructure - Rails build #18-push: SUCCESS in 31 sec:
11:14:13  <juzza1> if i try to click at the filename of (diff) here , it gives me an error "Not found: $JOB_NAME/xxx/xxx/xxx
11:15:17  <juzza1> clickin "definitions.pnml" gives me this: Not found: $JOB_NAME/file/966b5db40b80/src/definitions.pnml
11:37:34  <DevZone> Project Finnish Rail Infrastructure - Rails build #19-push: SUCCESS in 25 sec:
11:44:51  <Brot6> Revision 19:966b5db40b80: Feature: Alternate, grayer gravel ballast, finnish tracks on sand balla... Xjuzza1X @
11:44:52  <Brot6> Revision 20:0612c38aa3f6: Merge Xjuzza1X @
11:44:52  <Brot6> Revision 21:7fac5173dcbb: Fix: Old gravel style included in tracks.psd Xjuzza1X @
11:52:54  <DevZone> Project Finnish Rail Infrastructure - Rails build #20-push: SUCCESS in 25 sec:
12:35:46  <TWerkhoven> is brot6 supposed to be in #openttdcoop.stable ?
12:36:55  <planetmaker> he, I guess not. but does it say anything there?
12:37:28  <TWerkhoven> nop
12:37:34  <TWerkhoven> just noticed his nick in the list
12:38:28  <V453000> I was wondering what is he doing in .bots :)
12:38:59  <planetmaker> well... it's a bot :-)
12:39:42  <V453000> no humie? :(
12:44:20  <Brot6> Revision 22:e0d113ee4ad0: Feature: Shading for tunnel heads Xjuzza1X @
12:59:34  <^Spike^> ....
13:00:42  *** Brot6 has quit IRC
13:08:58  <V453000> :) dump
13:23:07  *** Alberth has joined #openttdcoop.devzone
13:29:22  <DevZone> Project Finnish Rail Infrastructure - Rails build #21-push: SUCCESS in 26 sec:
13:41:22  *** zooks has quit IRC
14:50:38  *** zooks has joined #openttdcoop.devzone
15:49:00  *** TWerkhoven has quit IRC
15:49:17  *** TWerkhoven has joined #openttdcoop.devzone
15:59:34  <planetmaker> Alberth, what package do I need to build the eints manual? My python-sphinx doesn't provide me with sphinx-build-3.3
16:02:37  <planetmaker> Alberth, I also see no obvious package:
16:35:20  *** frosch123 has joined #openttdcoop.devzone
16:51:55  <Alberth> planetmaker: what sphinx do you get?
16:52:54  <Alberth> rpm -qf `which sphinx-build-3.3` -> gives  python3-sphinx-1.1.3-7.fc19.noarch
16:53:19  <Alberth> but version is not likely to be very important
16:56:58  <planetmaker> ah, hm, yes, sphinx 1.1.3. The culprit was that my system doesn't have any version info in the binary
16:57:21  <planetmaker> does the trick for me
17:00:41  <Alberth> that looks like the right solution to me
17:02:05  <Alberth> for some weird reason, fedora added the python version to the binary :(
17:13:54  <planetmaker> Alberth, so, shall I push that patch? Then I can configure the CF to build eints docs and publish them on bundles server
17:14:10  *** oskari89 has joined #openttdcoop.devzone
17:14:16  <Alberth> sure
17:15:01  <Alberth> it will stop working at my machine out-of-the-box, but I won't build it that much, or I'll make a link or so
17:15:37  <planetmaker> well. Could be done on the CF, too
17:15:53  <planetmaker> but indeed I think that including the python version in the binary name is less common
17:16:05  <planetmaker> fedora doesn't provide any symlink by default?
17:16:06  <Alberth> imho a version number in a binary is stupid, it shouldn't be there in the first place
17:16:43  <Alberth> no it doesn't, apparently
17:17:51  <Alberth> added a link to my ~/bin
17:18:19  <DevZone> Project NML - NewGRF Meta Language build #55-nightlies: SUCCESS in 1 min 5 sec:
17:22:45  <DevZone> Project Finnish Rail Infrastructure - Rails build #22-push: SUCCESS in 36 sec:
17:26:40  <planetmaker> Alberth, what is the content of the 'doctrees' dir?
17:26:58  <planetmaker> it's some kind of documentation surely. Should we publish it?
17:27:06  <planetmaker> or should we only publish the html?
17:28:25  <Alberth> afaik it is cached documentation info, link names and urls and so on
17:28:53  <Alberth> _build/html should be sufficient (perhaps that can be pruned as well)
17:28:56  <DevZone> Project eints build #1-nightlies: SUCCESS in 6.5 sec:
17:29:07  <planetmaker> no pruning. Too tedious :D
17:29:47  <planetmaker> hm.... html docs were not copied :S
17:30:00  <Alberth> I mean a link like "the source code of the docs" is not that useful, but you're right, tmwftlb
17:31:57  <DevZone> Project eints build #2-nightlies: SUCCESS in 6.4 sec:
17:33:08  <DevZone> Project eints build #3-nightlies: SUCCESS in 4.9 sec:
17:34:05  <DevZone> Project eints build #4-nightlies: SUCCESS in 12 sec:
17:34:16  <planetmaker> there we go
17:34:55  <DevZone> Project Finnish Rail Infrastructure - Rails build #23-push: SUCCESS in 27 sec:
17:35:13  <planetmaker> thus you have now a place you can refer to for docs :-)
17:35:33  <planetmaker>
17:35:56  <frosch123> <- i'll add that to the top panel of eints?
17:36:02  <Alberth> \o/
17:36:16  <frosch123> <- or only that one?
17:36:26  <planetmaker> link LATEST does not yet exist for unknown reasons. But yes
17:36:48  <frosch123> it does exist ‽
17:36:57  <Alberth> frosch123:  usage inside the translator is sufficient, I think
17:37:11  <frosch123> Alberth: yeah, but i guess we can even commit that link
17:37:13  <Alberth> the full docs could be added to the project perhaps
17:37:22  <frosch123> it makes generally sense to link the docs, not devzone specific
17:37:24  <planetmaker> oh, it *does* exist
17:37:28  <planetmaker> ok, then yes, LATEST
17:38:03  <frosch123> <- or that page?
17:38:11  <Alberth> frosch123: make it configurable or so?
17:38:24  <frosch123> what do you want to configure?
17:38:32  <Alberth> path to the docs
17:38:49  <frosch123> do you mean to be able to link a specific version instead of LATEST?
17:39:00  <Alberth> both usage and strings are useful imho
17:39:43  <Alberth> no, but ""   looks devzone specific to me, or do you want to add that to the repo?
17:40:10  <frosch123> documentation usually links to the original site
17:40:15  <frosch123> where you also have the bugtracker
17:40:23  <frosch123> i don't see why anyone would want to mirror the docs
17:40:50  <Alberth> ok, in that light, it's fine to commit those links
17:40:53  <planetmaker> Alberth, I disabled build on push + tags for now. Release builds can always be hand-triggered. Until I've solved the nightly-when-needed this makes sure that the link nightly/LATEST really is the latest nightly :-)
17:41:25  <frosch123> e.g. the "help" link at the top of devzone also links to
17:41:25  <Alberth> planetmaker: ok, the docs hardly change anyway
17:41:27  <planetmaker> (actually any revision can be built manually on demand, soo... )
17:42:03  <Alberth> r1000 would be nice to have :p
17:42:24  <planetmaker> sure :-). But... the versioning is like days-since-2000 :-P
17:42:30  <planetmaker> at least in the filenames ;-)
17:42:43  <Alberth> :D
17:43:20  <planetmaker> unless for tagged commits. They get named like the tag
17:43:25  <DevZone> Project Finnish Rail Infrastructure - Rails build #24-push: SUCCESS in 36 sec:
17:43:40  <planetmaker> probably in the hope that the tag contains no spaces :D
17:50:52  *** gelignite has joined #openttdcoop.devzone
18:00:11  *** zooks has quit IRC
18:03:02  *** gelignite has quit IRC
18:16:44  *** gelignite has joined #openttdcoop.devzone
18:25:51  <DevZone> Project Finnish Rail Infrastructure - Rails build #25-nightlies: SUCCESS in 37 sec:
18:29:31  <DevZone> Project Nutracks build #13-nightlies: SUCCESS in 17 sec:
18:46:55  <DevZone> Project Iron Horse build #162-nightlies: SUCCESS in 41 sec:
18:49:11  <^Spike^> dihedral you around?
19:03:03  <DevZone> Project OpenGFX build #23-nightlies: SUCCESS in 5 min 50 sec:
19:06:08  *** andythenorth has joined #openttdcoop.devzone
19:06:29  <Alberth> o/
19:10:31  <andythenorth> o/
19:32:39  *** Supercheese has joined #openttdcoop.devzone
19:41:19  <DevZone> Project Finnish Rail Infrastructure - Rails build #26-push: SUCCESS in 27 sec:
20:25:26  <DevZone> Project OpenGFX build #24-push: SUCCESS in 5 min 54 sec:
20:28:24  <DevZone> Project Iron Horse build #163-push: SUCCESS in 33 sec:
20:31:09  *** Alberth has left #openttdcoop.devzone
20:33:37  <DevZone> Project Iron Horse build #164-push: SUCCESS in 33 sec:
20:45:46  <frosch123> oh, lol, the first day i do not check up on eints scripts, it fails
20:46:20  <frosch123> planetmaker: ^Spike^: hg pull failed for all repos at 16:47 utc
20:46:29  <frosch123> did you change something, was something down at that point?
20:46:41  <planetmaker> uh, not that I know of
20:47:04  <planetmaker> maybe some backup stuff going on and hogging ressources? ^Spike^ ? dihedral ?
20:47:18  <frosch123> actually, it has been failing all day
20:48:27  <frosch123> 2013-09-16 20:05:01.123984 UTC <- that's the first time it failed yesterday
20:48:41  <frosch123> remote: Permission denied (publickey).
20:49:08  <frosch123> you removed access for eints to the repos? :p
20:50:04  <planetmaker> eh, no?
20:50:14  <planetmaker> not that I know
20:50:22  <planetmaker> what URL does it try to access?
20:50:33  <frosch123> ssh://<projectname>
20:50:36  <planetmaker> ssh://hg@hg.o.o/projectname?
20:50:48  <planetmaker> hm... ah. hm. maybe :-)
20:51:01  <planetmaker> I might have removed that inadvertly last night
20:51:11  <frosch123> between 20:00 and 20:05 utc :)
20:51:32  <planetmaker> yeah. how did you add the key? Just add to authorized_keys? And not place a file in hg-repos?
20:51:44  <frosch123> i generated it on the translator vm
20:51:47  <frosch123> ^Spike^ added it
20:52:18  <planetmaker> yes, he didn't add the key to the key list but directly to the file
20:52:33  <planetmaker> thus the generator script I ran yesterday adding bad_brett's key deleted it :-)
20:52:42  <frosch123> magic :p
20:55:16  <planetmaker> so... it should have access again
20:55:18  <DevZone> Project FISH is ships build #11-push: SUCCESS in 1 min 17 sec:
20:55:30  <frosch123> i wonder whether the eints scripts should have some method to complain :)
20:55:35  <frosch123> noone notices when they fail
20:56:01  <andythenorth>
20:56:02  <Webster> Title: Sentry • Ship With Confidence (at
20:56:19  <planetmaker> is there a way to check whether it works again?
20:56:35  <frosch123> yes, it works
20:56:39  <planetmaker> k, good
20:56:47  <frosch123> you fixed it just between dutchroadfurniture and isr :)
20:56:53  <planetmaker> :-)
20:59:10  <frosch123> [22:56] <planetmaker> is there a way to check whether it works again? <- but if you want to know anyway, alls eints stuff is logged to /var/log/eints on the translator vm
20:59:38  <frosch123> 1.2 MB per day
20:59:42  <frosch123> :p
21:00:48  <DevZone> Project Finnish Rail Infrastructure - Rails build #27-push: SUCCESS in 39 sec:
21:01:33  <planetmaker> hm, my central log service doesn't quite show me anything:
21:01:43  <frosch123> thought today it was 4 MB
21:02:07  <planetmaker> possibly not all translator stuff but only its /var/log/messages
21:02:24  <frosch123> i don't know about your logs :p
21:02:33  <frosch123> mine are on the translator vm
21:03:36  <planetmaker> spike setup a central logging VM which logs basically everything. So we can check on logs at one place for all VMs
21:04:01  <frosch123> yeah, but i doubt the eints logs are passed to that
21:04:19  <frosch123> i think he fetched the apache logs
21:04:44  <frosch123> but i have no idea about how the rest works, so i have no idea how to put the eints logs somewhere else
21:05:28  <andythenorth> bye
21:05:28  *** andythenorth has left #openttdcoop.devzone
21:12:02  <DevZone> Project FIRS Industry Replacement Set build #17-push: SUCCESS in 5 min 38 sec:
21:13:51  * ^Spike^ blames scripts for manaing ssh authorized_keys files :D
21:14:10  <^Spike^> managing*
21:17:45  <planetmaker> that script is convenient :-)
21:17:52  <planetmaker> just put each key in its file. and run script
21:18:07  <planetmaker> in either full or hg-repos
21:18:16  <planetmaker> it then even restricts access accordingly
21:18:37  <planetmaker> or move key to locked and run script again. And it's removed (but we still have key)
21:18:58  <Supercheese> Hmm, should I be incrementing the grf version every time a translation is updated?
21:22:53  <planetmaker> yes. no. It's recommended. As the new NewGRF is newer. And then OpenTTD will know it
21:22:56  <planetmaker> Only then
21:23:37  <Supercheese> I should probably figure a way to automate that via build-script-type stuff
21:23:52  <planetmaker> :-) I have a solution there, you know ;-)
21:24:03  <Supercheese> I bet you do :D
21:24:20  <planetmaker> though... I changed it to update newgrf version only once a day
21:24:53  <planetmaker> given that translation updates are pushed once a day, that suffices
21:26:41  <frosch123> we could change it to jupiter-days since 2000 :p
21:31:20  <planetmaker> :-)
21:35:22  <Supercheese> Yikes, my grf will jump from version: 4 to version: 5008
21:35:33  <Supercheese> ah well, what's in a number? :P
21:36:15  <DevZone> Project Finnish Rail Infrastructure - Rails build #28-push: SUCCESS in 28 sec:
21:36:40  <frosch123> i think the fact that the version numbers of different grfs are counted on the same base, might turn out useful
21:36:57  <frosch123> you see when you mix new with ancient stuff and such
21:37:12  *** Zuu has quit IRC
21:38:11  <planetmaker> yeah, the jump was large for many, Supercheese :-)
21:38:17  <planetmaker> least actually for FIRS :-)
21:38:33  <DevZone> Project Fake Subways build #9-push: SUCCESS in 32 sec:
21:38:37  <Supercheese> heh, makes sense
21:38:50  <Supercheese> aaand there we go
21:38:53  <planetmaker> but it needed something which works rather universally
21:39:12  <planetmaker> thus days of commit since 1st January 2000
21:39:22  <Supercheese> seems like a good solution :)
21:40:31  <frosch123> "utc" might be important for Supercheese :p
21:40:37  <planetmaker> :-)
21:40:39  <Supercheese> hehe
21:40:56  <planetmaker> I'd not bet my life on using that properly yet :D
21:41:00  <Supercheese> UTC... whatever happened to GMT anyway?
21:41:14  <planetmaker> GMT is one clock. UTC is calculated from many
21:41:41  <planetmaker> or something like that
21:42:23  *** gelignite has quit IRC
21:42:53  <^Spike^> ehm... UTC is not influenced by summer time crap? :)
21:42:54  <planetmaker> hm... "Coordinated Universal Time (UTC) is the primary time standard by which the world regulates clocks and time. It is one of several closely related successors to Greenwich Mean Time (GMT). For most purposes, UTC is synonymous with GMT, but GMT is no longer precisely defined by the scientific community."
21:42:55  <Supercheese> at least my offset is still the same..... except for daylight savings stuff
21:44:27  <frosch123> ^Spike^: have you read the man page on gettimeofday? :p
21:44:57  <frosch123> "Of  course  it turned out that the period in which Daylight Saving Time is in force cannot be given by a simple algorithm, one per country; indeed, this period is determined by unpredictable political decisions.  So this method of representing timezones has been abandoned"
21:45:13  <^Spike^> ....
21:45:40  <^Spike^> if there is one thing... that drives every computer in the whole world crazy: dst :)
21:45:40  <planetmaker> UTC has no summer time crap
21:45:57  <planetmaker> it has only leap or lapse seconds to adjust to Earth's rotation
21:46:10  <frosch123> ^Spike^: aren't leap seconds worse?
21:46:15  <planetmaker> 'only'
21:46:16  <^Spike^> nah...
21:46:24  <^Spike^> 1 second isn't as worse as a whole hour :)
21:46:35  <^Spike^> it will not understand why it goes from 1:59:59 to 3:00:00 :)
21:46:40  <planetmaker> hm, now I have an opengfx with palette issues
21:46:45  <^Spike^> or from 2:59:59 to 2:00:00 :)
21:47:24  <^Spike^> realize an application relying on time... have that... it might accidently overwrite one hour worth of data if made wrong :D
21:47:28  <frosch123> or from 23:59:59 to 23:59:59 :p
21:47:39  <^Spike^> or you get a 1 hour gap in your data out of nowhere.. :)
21:47:44  <^Spike^> UTC just well... doesn't care :)
21:47:47  <^Spike^> so computers are happy :D
21:47:52  <frosch123> how many things crashed during the last leap second?
21:49:25  <planetmaker> I believe leap (and lapse!) seconds are as worse as dst for computers
21:49:34  <DevZone> Project Iron Horse build #165-push: SUCCESS in 52 sec:
21:49:45  <^Spike^> well difference between 1 hour and 1 second for a program... :)
21:49:58  <^Spike^> i rather have it overwrite 1 second of data instead of 1 hour (should that be the case ;))
21:50:00  <planetmaker> tell that a RT monitoring app
21:50:21  <^Spike^> let's see... when do i have standby again next... :D
21:50:49  <DevZone> Project Iron Horse build #166-push: SUCCESS in 35 sec:
21:50:57  <^Spike^> damn.... :)
21:51:00  <^Spike^> during my standy... :D
21:51:02  <planetmaker> is for those :-)
21:51:03  <Webster> Title: International Atomic Time - Wikipedia, the free encyclopedia (at
21:51:07  <^Spike^> standby*
21:52:34  <DevZone> Project Iron Horse build #167-push: SUCCESS in 36 sec:
21:56:10  <DevZone> Project OpenGFX build #25-push: SUCCESS in 6 min 1 sec:
21:57:12  <DevZone> Project Iron Horse build #168-push: SUCCESS in 44 sec:
22:00:53  <DevZone> Project Iron Horse build #169-push: SUCCESS in 44 sec:
22:07:10  <frosch123> night
22:07:14  *** frosch123 has quit IRC
22:13:08  <planetmaker> good night
23:12:04  <oskari89> Hm, why does not jenkins build now when clicked "build now"
23:12:32  <Supercheese> I think it queues a build to start when you next update the repo?
23:12:43  <Supercheese> Just a guess
23:13:34  <oskari89> It *should* build when pushed
23:13:56  <oskari89> Last push to repo was 71 minutes ago
23:14:12  <oskari89> ...
23:14:14  <oskari89> :D
23:14:20  <oskari89> It's already there
23:14:39  <oskari89>
23:16:02  <oskari89> The 28 just distracted, current repo push rev is 30
23:23:48  <DevZone> Project Finnish Rail Infrastructure - Rails build #29-push: SUCCESS in 35 sec:

Powered by YARRSTE version: svn-trunk