/srv/irclogs.ubuntu.com/2009/06/17/#upstart.txt

hugo303Fiveby518410:43
hugo303*slaps his head, hard, and changes password10:45
Keybukd'oh10:46
rikardDoes anyone know how to get upstart 0.3.9 to work with multiple dependencies?12:30
Keybukit doesn't12:39
=== Keybuk changed the topic of #upstart to: Upstart 0.3.10 "Two minutes to Belgium" | Upstart 0.5.1 "Unexpected item in bagging area" | http://upstart.ubuntu.com/ | “Unable to set oom adjustment”? Mount /proc before running init.
sadmacKeybuk: I didn't know there was going to be a 0.3.10...14:26
* sadmac would have written a lot more patches14:26
Keybukheh14:27
KeybukI didn't necessarily plan one14:27
Keybukbut assert() bugs are always worth fixing14:27
sadmacdamn, you should have held it up. I could have fixed 10 minor annoyances over the weekend.14:27
sadmacRed Hat BZ is full of 3-liner "flag foo is missing from shutdown" type patches14:28
sadmacwell, its full of the complaints anyway14:28
Keybukthose don't seem worth fixing ;)14:30
Keybukonce you cave in and agree an option should exist, you have to keep it forever14:31
sadmacKeybuk: you did say "SysV compatible" when you released. RH Engineering is holding you to that quite rigorously.14:38
sadmacKeybuk: also, you could have cleaned up/taken the "preserve state across re-exec" patch14:38
sadmacfedora carries it14:39
Keybukno I didn't14:39
Keybukthat's obvious by the fact Upstart doesn't read /etc/inittab <g>14:39
Keybukpreserve state across re-exec -> then that would have to be supported by 0.5 and 0.1014:40
sadmacKeybuk: I seriously hope we're going to support that...14:40
Keybuksupport which?14:40
sadmacpreserving state across reload14:43
Keybukyes14:43
Keybukand once I do, that API will never be broken14:43
Keybukwhich is why I'm being slightly hesistant of writing down that API14:43
* Keybuk tries to figure out his branch mess14:47
Keybuk*ahem*14:47
sadmacKeybuk: I think introducing it into 0.3.* wouldn't be harmful. 0.5+ breaks from that in so many ways anyway14:47
sadmacby 0.10 state transfer between minors wouldn't even make sense. 0.10 state doesn't even look that much like 0.3.9 state14:48
Keybukexactly my point?14:57
sadmacKeybuk: so why not carry the 0.3 patch and retire the release in style?14:58
Keybukbetter question, why carry the patch?14:59
Keybukcarrying it will suddenly bless that API, and there will be bugs when it doesn't work in future15:00
Keybukit doesn't cost you anything to apply it in Fedora after all15:00
sadmacyou can close with ENOTSUPP15:00
Keybukbut it must be supported15:00
Keybukthe patch is in the release15:00
Keybuksee what I mean15:00
Keybukif I apply the patch and release with it, I'm declaring it supported15:00
sadmacwhich it will be, in the 0.3.9 series only15:00
sadmacacross minors, you can just say "no"15:01
Keybukhmm, it's not an unconvincing argument ;)15:07
Keybukif you could file a bug (target 0.3), clean up and attach the patch (making sure it has test cases) - I'll do a 0.3.11 with it15:07
sadmacsweet. I might compile a list of other things that might suit a 0.3.11. You can line-item those when I get them (they'll all be comparatively tiny)15:09
* sadmac wonders what else we're carrying in CVS...15:10
sadmacshouldn't be much...15:10
sadmacoh wow. 9 patches.15:11
sadmacforce-on-shutdown-reboot is a genuine bugfix. you'll want that.15:12
Keybuksure, file bugs on them15:12
sadmacwill do.15:12
Keybukuse the "Target to release" thingy to set them as 0.315:12
Keybuk(you can also tag 0.5 and trunk that way too)15:12
sadmacKeybuk: is ubuntu built on gcc43+ yet?15:13
sadmacwe're still carrying a patch to add a header file that needs15:13
Keybukyes15:13
Keybuklimits.h?15:13
Keybukthat one went into 0.3.1015:13
sadmacyeah15:13
sadmaccool15:13
Keybukas did an amd64 fix15:13
sadmacKeybuk: oh, want to roll our events.5 manpage into a general release?15:14
Keybuksure15:14
sadmaccool15:14
ion_CVS⁈15:15
sadmacI'll have all this filed by saturday (earlier if my date stands me up tonight)15:15
sadmacion_: don't remind me15:15
sadmacion_: Fedora packages are in CVS. We have one branch per release. Inside each branch is an rpm specfile and all the patches we apply (upstream tarballs are kept separate in a lookaside cache and pulled in when we build)15:19
sadmacits actually fairly easy to work with. we have a makefile that does the hard stuff.15:20
sadmaccahnge specfile, copy in patch, commit, make tag, make build15:21
* Keybuk tries to make util build again15:22
Keybukshutdown.c: In function ‘shutdown_now’:15:23
Keybukshutdown.c:490: error: too few arguments to function ‘nih_dbus_proxy_new’15:23
sadmacphantastiq15:23
Keybukbuilds now ;)15:28
sadmac5 minutes. Not bad. But can you do it in space?15:29
KeybukI _AM_ in space15:30
sadmacThe boss took you along on his vacation this year?15:31
KeybukI wish15:31
ion_I am in time.15:32
Keybukthe most we get for good behaviour is a ride in the jet15:32
sadmacI think Shuttleworth jokes are the equivalent of saying "your mom" to an Ubuntu dev.15:32
sadmacat least the spaceboy ones.15:32
KeybukYour CEO is so dull he worked for Delta 15:33
Keybuketc.15:33
sadmacJim's actually a lot more fun than I thought. Not as intimidating as Szulik, but he drinks the Kool-aid, which is nice15:35
sadmacruns rockbox on his iPod15:36
sadmaclook forward to the release of Red Hat Enterprise Music Bus soon15:36
sadmacecho -e '#include<pthread.h>\n#include<unistd.h>\nmain(){pthread_t15:39
sadmact;pthread_create(&t,NULL,pause,NULL);pause();}'|gcc -o t -x c - -pthread15:39
sadmacthats... a new way to specify a reproducer in BZ...15:39
KeybukBZ?15:44
Keybukoh, BugZilla15:45
Keybukdamnit, the 0.3 code is easier to read than the 0.515:46
sadmacKeybuk: what's the cause?15:50
Keybuksadmac: of the code being easier to read?16:03
sadmacKeybuk: rather of it being harder. Is there a particular disease?16:04
KeybukI don't like the way blocked stuff is done in 0.5 basically16:04
Keybukthen again, at least it work s:p16:05
Keybuk...with respawn of running while post-start process16:05
Keybuktest:job_process.c:1090: Assertion failed in job_process_terminated: job->state == JOB_POST_START16:05
Keybuk\o/16:05
sadmac |16:05
sadmac\16:05
sadmacthere's a regular on fedora-devel-list who's name is listed as King InuYasha16:06
sadmacI can't tell if he's serious or not16:06
Keybuknow, if distcheck would just pass ...18:45
sadmacKeybuk: what's up with it?18:47
Keybukjust taking its time18:48
Keybukthere's no reason it shouldn't pass18:48
Keybukbut I'm paranoid18:48
Keybukand out-of-tree builds hate me18:48
ion_A process too slow? Throw more hardware at it. :-)18:49
Keybuk/home/scott/co/upstart-0.5/upstart-0.5.2/_build/util/../../util/initctl.c:349: undefined reference to `job_get_name_sync'18:50
Keybuksee18:50
KeybukHATRE18:50
KeybukHATE18:50
sadmaccarpe odium18:50
* Keybuk waits again18:53
KeybukToo Many Test Cases18:53
sadmacKeybuk: we could probably parallellize a lot of them if we thought about how18:54
=== Keybuk changed the topic of #upstart to: Upstart 0.5.2 "Something, something, something, D-Bus" | Upstart 0.3.10 "Two minutes to Belgium" | http://upstart.ubuntu.com/
ion_Next up: 0.10. :-P19:12
sadmacKeybuk: we went to GPLv3? I thought your license preferences tended the other way19:13
sadmacKeybuk: you rewrote nih_dbus_tool in expat?19:15
sadmac*or rather in C19:15
keesjhttp://paste-it.net/raw/public/j16d3e1/ same kind of error  undefined reference to `dbus_message_iter_abandon_container'19:23
keesjthat one looks more like a dbus thing actualy19:23
mbieblIs that related to the D-Bus patch that Scott referenced in his announcement email?19:45
mbieblKeybuk: what bad things will happen, if this patch is not applied?19:46
Keybuksadmac: my licence preferences don't apply to Upstart19:47
Keybukthat's up to Canonical ;)19:47
Keybukkeesj: see NEWS19:47
Keybukmbiebl: Upstart won't combile, obv :)19:47
sadmacKeybuk: oic19:48
mbieblKeybuk: ah,ok. So keesj' problems are indeed related to this missing dbus patch19:48
Keybukyou can replace _abandon_ with _close_19:49
Keybukbut then libdbus will randomly assert() on you19:49
Keybukyou can remove the lines, but then you'll get a memory leak19:51
* sadmac is near to cleaning up the hideous locking in linux's wait*() syscalls19:51
sadmacno more quantum-critical sections!19:51
Keybukcisco in "whinging about licensing" again shocker19:58
keesjI have the same problem . I feel very sorry19:59
* keesj goes and reads the GPLV3 again20:02
Keybukkeesj: why?20:11
KeybukWhat is it about v2->v3 that you don't like?20:12
keesjI don't think is about liking or not. at least at work we gplv3 will be very hard(read impossible) to sell.20:14
Keybukyou don't ship any current versions of FSF software?20:14
Keybukwhat version of gcc do you use?20:14
keesjour company has booth hardware and things like maps they really like to sell20:15
Keybukyou can sell hardware with GPLv3 software on it20:15
keesjwe use recent gcc like 4.2 but that doesn't pose restrictions on the software we create 20:15
keesjI can sell a close source project compiled with gcc so that is not a good example20:16
Keybukgcc 4.2 is under the GPLv320:16
Keybukwhich version of coreutils do you use?20:16
keesjdon't know something relased with the code sourcery we use let met check20:17
KeybukCodeSourcery the company/products?20:17
keesjthe toolchain20:17
Keybukthey're partners of Canonical, and certainly include GPLv3 pieces20:17
keesjnope , well perhaps lgpl20:18
Keybuk(you know that GPLv2 software can't be linked with LGPLv3 right? :p20:19
Keybuk so every single piece of GPLv2+ software on a system linked to an LGPLv3 library is automatically GPLv3 :p)20:19
keesjwell I guess I need to find an other job :p20:20
Keybukseriously though20:20
Keybukwhy the concern?20:21
Keybukwe do work in the embedded and mobile spaces20:21
Keybukno GPLv3 trouble there20:21
keesjdear Mister GSM provider please provice us the source code for your GSM stack so we can abuse your network, and make your device not FCC compliant20:25
sadmacoh boy do people ever have some funny ideas about what this license means20:26
Keybukyou don't need the source any more than you do in GPLv220:26
Keybukyou can ship GPLv3 code in the same system as commercial code20:26
Keybukjust as you can with GPLv220:26
keesjno it's not about source it's about freedom for the devloper !20:27
Keybukhuh?20:28
sadmackeesj: what freedom do you think has gone missing?20:28
keesjwell the "tivoization" part for example or wanting keep control over what software runs on the embedded device20:29
sadmackeesj: what's wrong with that? I paid for the damn device.20:30
sadmacand LGPLv3 strikes all of that20:30
sadmacexplicitly20:30
sadmacbrb kernel20:31
keesjWell quite frankly I will check the license of the binutils and such but for the moment assume GPLV3 is not OK20:38
sadmacKeybuk: I don't see your patch in linus yet. Who said they took it?21:16
joshkis there a way to print something to tty0 even during a quiet boot?23:27
joshki have this /etc/rc.local file that takes a while to run23:27
joshki've tried: stderr, and log_*_msg from /lib/lsb/init-functions, and nothing shows up23:27
joshki guess upstart is filtering out all of stderr and stdout. There's no way to work around that?23:28

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!