Log for #openttdcoop.devzone on 15th June 2014:
Times are UTC Toggle Colours
00:28:04  *** gelignite has quit IRC
07:09:44  *** Alberth has joined #openttdcoop.devzone
07:11:23  *** LSky` has joined #openttdcoop.devzone
07:16:24  *** Supercheese has quit IRC
07:54:18  *** Webster has joined #openttdcoop.devzone
08:49:47  *** gelignite has joined #openttdcoop.devzone
10:03:07  *** oskari89 has joined #openttdcoop.devzone
10:26:35  <Alberth> hmm, I used to know how to compile a Python C extension without much effort, but how did I do that?
10:26:56  <V453000> magic
10:32:31  <Alberth> hmm, yeah, computers are not so sensitive to my magic, I am afraid.
10:32:52  <Alberth> sounds like a nice cargo to make next to stuff and things, though :)
10:43:51  <V453000> :)
10:53:39  *** frosch123 has joined #openttdcoop.devzone
12:31:44  *** yorick has joined #openttdcoop.devzone
13:11:13  <Ammler> nml 0.3.1 source has hardcoded version in the path which makes it unbuildable without manual settings, is this a known issue?
13:11:45  <Ammler> -%setup -q
13:11:47  <Ammler> +%setup -q -n %{name}-%{version}.r5242-f6a3ae1163ab
13:13:47  <Ammler> meh, need to learn how bug tracking works again :-)
13:31:51  <Ammler> how did you guys resolve the python <2.7 issue?
14:11:31  <Alberth> hi
14:11:42  <Alberth> mostly by upgrading to python3, I think
14:51:09  <planetmaker> oh, an Ammler :) Hi
15:03:16  <DevZone> Project xussrset - Trains from Russia build #322-push: SUCCESS in 3 min 24 sec:
15:18:41  *** ODM has joined #openttdcoop.devzone
15:28:38  <V453000> hy Ammler (:
16:21:59  <DevZone> Project Japanese Buildings build #232-nightlies: SUCCESS in 19 sec:
16:25:25  <Rubidium> Alberth: at least heffer made a rant about that version thing in some way or another ;)
16:26:29  <Alberth> the "r5242-f6a3ae1163ab" thingie?
16:26:36  <Rubidium> yup
16:26:54  <Alberth> I have no idea how it got there
16:27:27  <Alberth> I didn't program any version string replacement stuff
16:27:54  <Alberth> planetmaker probably knows what happens there
16:30:16  <planetmaker> that was about the output file name iirc
16:30:42  <Rubidium> at least the folder name
16:32:12  <planetmaker> yes. I've a note / open issue somewhere to fix that
16:32:52  <planetmaker> to use a constant folder and filename. That changed with my fiddling with the versions and packaging. And I didn't think of people relying on the exact folder and filename staying constant
16:34:09  <DevZone> Project Finnish Rail Infrastructure - Rails build #346-nightlies: SUCCESS in 8 min 28 sec:
16:41:20  <DevZone> Project road-hog build #232-nightlies: SUCCESS in 40 sec:
16:48:27  <DevZone> Project Iron Horse build #911-nightlies: SUCCESS in 1 min 46 sec:
16:48:55  <DevZone> Project 2ccts build #154-push: SUCCESS in 2 min 8 sec:
16:49:06  <DevZone> Project Dutch Trackset build #29-push: SUCCESS in 37 sec:
16:49:40  <DevZone> Project ecs build #51-push: SUCCESS in 34 sec:
16:51:06  <DevZone> Project 2ccts build #155-push: SUCCESS in 1 min 25 sec:
16:52:31  <DevZone> Project xussrset - Trains from Russia build #323-push: SUCCESS in 3 min 35 sec:
16:54:47  <Ammler> planetmaker: having version in the path (archive) is fine, but the additional revision and hash breaks automatic building
16:55:04  <planetmaker> o/
16:55:08  <Ammler> :-)
16:55:13  <planetmaker> yeah, I think heffer complained about that, too
16:55:38  <Ammler> oh, yes, hello btw. :-P
16:56:36  <Ammler> I created a ticket too
16:56:47  <planetmaker> anyway, with respect to NML 0.4.0-rXXX and later: you need to use python3.2 or newer to build
16:57:24  <planetmaker> that will currently fail for an rpm with windows as there is no nml-dot-wine with python 3.2. Though I have the wine dir on the jenkins VM which allows that
16:57:31  <planetmaker> which actually allows both, 2.7 and 3.2
16:57:45  <planetmaker> got a bit big, but alas :P
16:57:57  <Ammler> the rpm with wine is a #openttdcoop buildserver thing only, so no big deal
16:58:30  <planetmaker> I didn't touch much the spec file as I don't have really good means to test that currently
16:58:49  <planetmaker> maybe you can help change that? So that we can build rpm and debs?
16:59:09  <Ammler> the issue is rather that python >=2.7 breaks SLE support
16:59:11  <planetmaker> would need creating the proper schroots, I guess. And then telling the build script to use it
16:59:31  <planetmaker> well, there are other rpms which provide it, no?
16:59:51  <planetmaker> SLE as well as RHEL don't have that yet, yes
17:00:06  <planetmaker> but I'm sure their next versions will, too
17:03:20  <Ammler> planetmaker: is there still wine needed to build nml, having native windows support not possible?
17:03:26  <Alberth> nml for servers?
17:03:59  <Ammler> I thought with the new buildsystem, you also will have windows and osx build hosts
17:04:07  <planetmaker> as the server didn't change, we don't have native windows support
17:04:28  <planetmaker> thus for nml on windows we still need the wine there
17:04:39  <Ammler> GOAL!
17:04:45  <Alberth> ?
17:05:06  <planetmaker> the new build system does not magically allow other VMs
17:05:17  <planetmaker> and we saw that KVM made our server unstable
17:05:23  <Ammler> Alberth: soccer :-P, you do not watch?
17:05:33  <planetmaker> jenkins could easily make use of those - if we had them, yes. But we don't
17:05:41  <planetmaker> wow. Now I see that, too
17:05:47  <planetmaker> quite a bit of lag
17:06:06  <Ammler> planetmaker: the windows host needs to be on our server?
17:06:12  <planetmaker> no, doesn't
17:06:28  <planetmaker> but we'll need administrative access
17:06:31  <Ammler> and abusing openttd windows host not possibe? Rubidium?
17:06:48  <Alberth> Ammler: no, I don't even have a provider for TV currently
17:06:50  <planetmaker> openttd uses bamboo, we use jenkins :)
17:07:08  <planetmaker> but as OpenTTD has a new server, maybe we could create such VM for this build service indeed
17:07:29  <planetmaker> Alberth, the internetzzzz has it all :P
17:07:40  <planetmaker> (but I guess that's why I know > 60s after Ammler :P )
17:08:05  <Alberth> planetmaker: the goal doesn't change in the mean time :p
17:08:12  <planetmaker> nope :P
17:08:50  <Ammler> planetmaker: using wine was always a ugly solution, imo.
17:08:58  <planetmaker> yes. But a working one
17:09:05  <Ammler> it was simply everything we could do at that time
17:09:25  <Ammler> I was not able to setup better cross compiler
17:09:57  <planetmaker> took me long enough to reproduce that with python 3.2 :)
17:10:40  <planetmaker> and I don't think there is a cross compiler for freezing python to exe on another system than windows
17:11:29  <planetmaker> at least I found no such solution for python programmes
17:11:31  <Ammler> well, why not as there are cross compilers for c++ etc. too, which look less cross plattform to me.
17:15:39  <Ammler> there is no official python 2.7 for SLE
17:17:08  <Ammler> there is official python 3 for opensuse
17:18:04  <Ammler> 3.3.5 and 3.4
17:18:38  <Ammler> no python3 for sle
17:20:07  <Ammler> but there are community repos, I might be able to work around...
17:22:02  <planetmaker> what python does SLE have, if no 3.x and no 2.7?!
17:22:10  <planetmaker> I'd not worry in those cases then
17:22:32  <planetmaker> <-- anyway, this is what I consider the most urgent things to do
17:23:10  <planetmaker> I'll not worry about building windows and OSX builds for now
17:23:32  <planetmaker> we can consider VMs for those when the current system builds in a sandbox :)
17:27:59  <planetmaker> he, offside
17:31:52  <Ammler> btw. openttd has a very nice tablet version
17:33:36  <Ammler> hmm, you still want to use the .devzone config?
17:34:10  <Ammler> [19:22] <planetmaker> what python does SLE have, if no 3.x and no 2.7?! <-- 2.5
17:34:41  <Ammler> I guess the same with centos or that might use 2.3
17:35:51  <Alberth> :O
17:36:12  <Ammler> I am not sure at all since sle is closed
17:36:19  <Ammler> but I know, it is <2.7
17:37:02  <planetmaker> Ammler, then just don't worry, I think
17:37:05  <Ammler> so there is also big support from the community to support sle, it was more a personal challenge
17:37:14  <Ammler> no*
17:37:17  <Ammler> planetmaker: yes
17:37:59  <planetmaker> I don't think many of our 'customers' use SLE or RHEL :)
17:38:12  <planetmaker> they rather use like opensuse or fedora
17:38:42  <Ammler> well, the important part was to get openttd to the main opensuse repo
17:38:56  <planetmaker> :)
17:38:59  <Ammler> so chances are good to get it into the next sle, if there will ever be one
17:39:17  <Ammler> they sill release sp
17:41:17  <Ammler> another advantage is that since openttd is in the main repos, it has other maintainers too, I only did the security update last december, the other updates were all done by others, I just reviewed
17:41:22  <planetmaker> so you're saying SLE is important for getting it into opensuse repo?
17:41:34  <Ammler> no
17:41:38  <planetmaker> ok :)
17:41:54  <Ammler> having it in the opensuse main repo might be helpful to get it into the next sle release
17:44:44  <Ammler> (which is the case of every supported opensuse now)
17:45:14  <planetmaker> well, but opensuse has python3 and proper ply and pillow :)
17:46:04  <Ammler> never used python3 yet, so no clue about
17:46:21  <Ammler> and python2 is still "default"
17:47:35  <Ammler> on my 13.1 at least
17:47:47  <Ammler> which is the most recent distro
17:48:02  <Ammler> is there a distro out already using python3 as standard?
17:48:58  <planetmaker> not sure. Not that I know. Maybe fedora will switch soon
17:49:19  <planetmaker> anyway, there's no reasonably new distro which does not have python3
17:49:25  <planetmaker> so using that is no issue at all
17:49:37  <Ammler> TOOOR!
17:49:37  <planetmaker> you can have both, python2 and python3 concurrently w/o any issue
17:49:48  <planetmaker> hey, don't tell me! :P
17:50:27  <Ammler> oh, no spoilers :-P
17:51:19  <planetmaker> now I see that, too :P
17:51:32  <Ammler> is nml 0.4 already useable to test?
17:51:49  <planetmaker> it works 100% according to my knowledge
17:51:58  <planetmaker> it's nml default branch
17:52:22  <planetmaker> thus it's what devzone builds as nightly / build-on-push
17:52:57  <planetmaker> and any future NML will be based on that. Except bug-fix releases to NML 0.3 branch
17:55:19  <planetmaker> btw, I'm considering to 'abandon' the nightly builds and just use build-on-push. And symlink the nightly folders on bundles server to push
17:55:23  <planetmaker> What do you think of that?
17:57:14  <Ammler> well, or simply "copy" the last build of the day if there is one
17:57:33  <planetmaker> yes. I thought of symlinks to keep the URLs active
17:57:45  <Ammler> the difference right now is that we keep nightlies around 90 days and pushes only around 7 iirc
17:58:37  <Ammler> is the "cleanup" script still in action?
17:58:45  <Ammler> "my"
17:58:46  <planetmaker> I don't think so
17:59:10  <Ammler> so who or how do you cleanup now?
17:59:37  <planetmaker> but the cleanup for builds definitely needs a review. It's a good question :)
18:00:17  <Ammler> I think, my script still works
18:00:55  <planetmaker> might be
18:01:44  <Ammler> <-- only 2 revisions
18:02:08  <Ammler> nightlies has a lot more, this is how I configured defaults
18:02:16  <planetmaker> yes, still active on root@bundles
18:03:04  <planetmaker> so the defaults should probably be adjusted :)
18:04:13  <Ammler> cleanup_releases
18:04:15  <Ammler> the minimum amount of releases to be published
18:04:16  <Ammler> default: 10 for nightlies, unlimited for releases, 1 for push
18:04:18  <Ammler> maximum: unlimited
18:04:19  <Ammler> unlimited = 0
18:04:21  <Ammler> Edit
18:04:22  <Ammler> cleanup_days
18:04:24  <Ammler> the minimum amount of days a release is published
18:04:25  <Ammler> default: 100 for nightlies
18:04:27  <Ammler> (if not set, cleanup_releases "counts", only)
18:04:28  <Ammler> Edit
18:05:21  <Ammler> well, it doesn't make much sense to keep 100 bundles from one day
18:05:29  <planetmaker> definitely not :)
18:05:39  <Ammler> so having "nightlies" as archive might still be useable
18:05:51  <planetmaker> well, push is really the new nightly
18:05:55  <Ammler> and simply copy oldest push bundle
18:06:00  <Ammler> newest*
18:06:21  <planetmaker> so keeping the amount of builds there as for nightlies previously makes most sense. And is easier than yet another indirection by copying
18:06:24  <Ammler> for building, nightlies could be removed
18:06:29  <planetmaker> it is actually
18:06:47  <Ammler> and cleanup script simply copies push to nightlies on cleanup
18:07:05  <planetmaker> ah, that way. hm. maybe
18:07:20  <planetmaker> might make sense :)
18:07:26  <Ammler> well, it is easier to manage imo
18:07:29  <planetmaker> yup
18:07:46  <Ammler> cleanup push builds but keep one per day might be complicated
18:08:09  <planetmaker> yeah, just copying the latest push to nightlies. And the the usual cleanup procedure
18:08:19  <planetmaker> s/the the/then the/
18:49:13  *** Supercheese has joined #openttdcoop.devzone
20:05:07  *** ODM has quit IRC
20:13:28  *** Alberth has left #openttdcoop.devzone
20:37:29  *** frosch123 has quit IRC
21:11:49  *** oskari89 has quit IRC
21:30:07  *** LSky` has quit IRC
23:15:09  *** gelignite has quit IRC

Powered by YARRSTE version: svn-trunk