[12:40] <johnnybuoy> does anyone know about a good documentation for upstart?
[01:02] <Seveas> johnnybuoy, the source code ;)
[01:04] <johnnybuoy> :D
[01:04] <johnnybuoy> thanks!
[04:37] !alindeman:*! Hi all.  A rotation server just hiccuped; we're looking into it
[06:03] <Keybuk> http://enterprise.linux.com/enterprise/06/09/18/1623244.shtml
[06:05] <thom> Keybuk: you sly dog, sneaking gratuitous self-agrandisement onto linux.com ;-)
[06:12] <smlgb1> Hi there. Did anybody of you try to install upstart on gentoo yet?
[06:12] <Keybuk> smlgb1: I believe there have been several attempts, at least one of which was successful
[06:12] <Keybuk> thom: and getting paid for it, too ;)
[06:14] <smlgb1> is there some online resource to check it out? I am trying for over a day now, but i cannot get it to do the right thing...
[06:15] <thom> Keybuk: you can buy me a beer at uds then
[06:16] <Keybuk> heh
[06:16] <Keybuk> thom: you're definitely coming?
[06:16] <Keybuk> cool
[06:17] <Keybuk> smlgb1: no idea, I don't know if anyone's written it down yet
[06:18] <smlgb1> ok, thanks. gotta keep trying.
[06:21] <wasabi_> Keybuk: sponsorship accepted. ;0
[06:21] <wasabi_> Yay for me!
[06:22] <wasabi_> I'm going to start writing up a ton of various use cases of complicated upstart event stuff, and start blowing out flow charts.
[06:22] <Keybuk> wasabi_: yeah, I saw a few weeks ago
[06:22] <Keybuk> I guess the mails finally went out then
[06:22] <wasabi_> Yeah.
[06:23] <wasabi_> whiprush sent in another recommendation because I'll be working on some directory integration stuff too
[06:23] <wasabi_> He didn't know you already had.
[07:09] <madduck> Keybuk: can you do s@/boot/grub/menu.lst@& (or if using grub2 - /boot/grub/grub.cfg)@ in the README?
[07:09] <madduck> bounce from a user forthcoming
[07:18] <Keybuk> madduck: err, -v ?
[07:18] <madduck> Keybuk: yeah, this is 0.1.1
[07:18] <madduck> Keybuk: if it does not apply anymore, all the better
[07:19] <Keybuk> I didn't understand the sed
[07:20] <Keybuk> and yeah, there's no README.Debian anymore in 0.2+
[07:22] <Keybuk> I suspect Debian will want to keep it though, unless you install upstart as /sbin/init
[07:23] <madduck> kinda. i am not maintainer anymore, it's up to mbiebl now. :)
[07:23] <mbiebl> Keybuk: 0.2.7 is currently in NEW again because of the new binary packages.
[07:24] <Keybuk> oh right, fair enough
[07:24] <mbiebl> It also replaces /sbin/init.
[07:24] <Keybuk> how did you package it?  ubuntu-style?
[07:24] <Keybuk> cool
[07:24] <Keybuk> shiny
[07:24] <mbiebl> It's based on your packages.
[07:24] <mbiebl> I want to keep it as close as possible.
[07:25] <mbiebl> sysvinit has been split up and other packages which still depedended on sysvinit have mostly been fixed.
[07:25] <Keybuk> could you use -Xdebian1 in your revisions, not just -1 though
[07:25] <madduck> yeah, this was pretty painless. i meant to blog about the whole process.
[07:25] <mbiebl> (bluez-utils being the most important one which still remains)
[07:25] <Keybuk> otherwise I'll have to blacklist it from the Ubuntu sync/merge process
[07:25] <Keybuk> which won't do either of us favours
[07:25] <madduck> Keybuk: why not try to stay in sync?
[07:26] <Keybuk> I don't mind if they don't differ
[07:26] <madduck> mbiebl: ?
[07:26] <mbiebl> Good question, still debian/control has to differ because of the different replaces.
[07:27] <madduck> mbiebl: then i guess it should really be -Xdebian1
[07:27] <mbiebl> Also pere chose to name sysvutils sysvinit-utils.
[07:27] <madduck> i think ubuntu will follow this choice of name, right Keybuk ?
[07:27] <Keybuk> we will in edgy+1, yeah
[07:27] <Keybuk> obviously we're frozen now
[07:28] <mbiebl> Keybuk: I already thought about naming them -Xdebian1. But I don't always copy debian/ on a new release of the Ubuntu package.
[07:28] <mbiebl> I copied them for 0.2.5 and then only synced in the necessary changes.
[07:29] <Keybuk> the main problem is if you, for what ever reason, race ahead of us
[07:29] <Keybuk> you do 0.3.0-1, so do we, but they differ
[07:29] <Keybuk> and you need to fix something, and do 0.3.0-2
[07:29] <Keybuk> Debian now has a higher version than Ubuntu, so our sync process will try and override our version with yours
[07:29] <Keybuk> which would be bad
[07:30] <Keybuk> the sync process recognises XubuntuY and XdebianY
[07:30] <mbiebl> Hm, right.
[07:30] <Keybuk> the former as an "Ubuntu patched version of a Debian-maintained package"
[07:30] <Keybuk> and the latter as a "Debian patched version of an Ubuntu-maintained package"
[07:30] <Keybuk> so it'd know not to override our version with a XdebianY
[07:31] <mbiebl> I just found it odd to name them -Xdebian1 also if they are not directly based on the corresponding Ubuntu version.
[07:31] <Keybuk> without that, I'd need to blacklist upstart from the sync process to avoid us suddenly ending up with the debian packages
[07:31] <Keybuk> name them -0debian1 then?
[07:31] <Keybuk> we use that in Ubuntu when we don't base things on the Debian version
[07:32] <Keybuk> it's not important though, if you don't want to use patches/merge.ubuntu.com etc.
[07:32] <Keybuk> or get diffs from the PTS
[07:33] <mbiebl> How do you usually handle syncs between Debian/Ubuntu?
[07:33] <mbiebl> Do you copy the Debian changelog?
[07:34] <mbiebl> Even if the packages evolve differently for some time.
[07:35] <Keybuk> if we branch the package, we add our entries to the top of the changelog
[07:35] <Keybuk> so you see -2ubuntu2, -2ubuntu1, -2, -1 etc.
[07:35] <Keybuk> then if we merge in Debian again, we add the new Debian at the top
[07:35] <Keybuk> (and a ubuntu1 for the merge)
[07:35] <Keybuk> -3ubuntu1, -3, -2ubuntu2, -2ubuntu1, -2, -1
[07:35] <Keybuk> if we abandon our patches, we sync the Debian version and drop the changelog diff
[07:38] <mbiebl> Ok, then I'll try to adopt a corresponding versioning scheme with -XdebianY for the Debian package.
[07:39] <Keybuk> if not, don't worry too much :)
[07:39] <Keybuk> I'm the guy that does the sync/merge stuff, so I'd quickly hit a button if I saw upstart in there ;)
[07:41] <mbiebl> Keybuk: The only issues I currently have with upstart on Debian is, that console-setup/console-tools don't work properly during boot up.
[07:41] <mbiebl> I know that you had the same problems on Edgy already, so maybe you could give me some pointers how you fixed that.
[07:42] <Keybuk> "don't work properly" ?
[07:42] <mbiebl> Font and keyboard are not setup during bootup.
[07:42] <Keybuk> with usplash?
[07:42] <mbiebl> Without.
[07:42] <Keybuk> Debian uses setupcon?
[07:43] <mbiebl> I can, it's optionally.
[07:43] <mbiebl> s/I/It/
[07:44] <Keybuk> does adding "console output" to rcS/rc2 help?
[07:44] <Keybuk> it "just works" here, don't really know much about it
[07:44] <Keybuk> I know Kamion spent ages transitioning us to setupcon
[07:45] <Keybuk> I assumed Debian had done the same before, he tends to prefer to keep us matched to Debian
[07:45] <mbiebl> I'll check that. I just know, that /etc/init.d/console-setup works when run from sysvinit, but not from upstart.
[07:46] <Keybuk> assuming you just copied the ubuntu jobs, you've probably got a silent startup with no console output
[07:46] <mbiebl> Right.
[07:46] <Keybuk> if whatever sets the console up just uses fd 0/1/2, then it won't do anything
[07:47] <mbiebl> Ah, so why does it work on Ubuntu then? It also uses the silent startup.
[07:48] <mbiebl> Have the changed the init scripts/setupcon?
[07:48] <Keybuk> we just call "setupcon -k --force"
[07:49] <Keybuk> it seems to dtrt here
[07:49] <Keybuk> oh, the -k is just if usplash is running
[07:50] <Keybuk> anyway, gym time, gotta run
[11:02] !Rez:*! Hi all!  You may notice some bots around the net attempting to exploit a bug in some routers (whereby they crash on a malformed DCC SEND string).  We're doing our best to mitigate the visibility of these bots, but if you're still being affected (i.e., disconnected) by them, please consider connecting to freenode on a non-IRC port, such as 8001.  Thanks!