[00:00] <krutoileshii> Yep, I tried replacing the parts that check for 2.6 to 3 and it compiled, but it failed to install
[00:01] <krutoileshii> Not sure what I missed yet, I'll do some investigating tomorrow. Thanks for the help.
[00:24] <slangasek> hallyn_: heh; vm-new tries to bring the VM up with virtio networking, which fails with 'failed to find romfile "pxe-virtio.bin"'.  are there some other options I'm supposed to be using?
[00:29] <jfi> Hello, I would like to know if a fix to bug #811003 is acceptable for Oneiric, or this kind of "bug" (more a feature) is generally delayed to the next release. I just want to know whether is usefull that I provide a debdiff or just wait the next sync from debian.
[00:30] <hallyn_> slangasek: oh?  that should spit an error, but not fail
[00:30] <hallyn_> slangasek: pxe-virtio is only for pxeboot over virtio
[00:31] <slangasek> hallyn_: ah.  well, I'm looking at logs because what I'm experiencing is that the VM never comes up after reboot
[00:31] <hallyn_> virsh list doesn't show it running?
[00:32] <slangasek> no, it *does* show it running
[00:32] <hallyn_> oh just ssh to it or gvncviewer :0
[00:32] <slangasek> but it's not meaningfully "up"
[00:32] <hallyn_> drat
[00:34] <slangasek> oh, it does seem to respond to ssh, hmm
[00:34] <slangasek> but vm-new doesn't finish because vm-ping fails?
[00:34] <hallyn_> yeah the reporting isn't perfect at vm-new.  but the big win with vm-tools is the vm-clone command
[00:34] <hallyn_> i don't use vm-new all that much
[00:34] <hallyn_> but clone every day
[00:34] <slangasek> well, I'm not sure if I should ^C this vm-new command...?
[00:34] <hallyn_> yes
[00:35] <hallyn_> look in / in the guest,
[00:35] <hallyn_> if there is still a post-install.sh, run it as root, otherwise you're done
[00:35] <hallyn_> so, your initramfs has 'udev.bak', will it run that?
[00:38] <cjwatson> jfi: it's too late for UI adjustments at this point, so we're probably best just taking the next sync from Debian in precise
[00:39] <cjwatson> jfi: although thank you for caring
[00:39] <jfi> cjwatson, thanks for the response
[00:42] <hallyn_> slangasek: scripts/init-bottom/udev is still not getting to the ps -ef (even when I add '|| /bin/true' after the pkill)
[00:43] <hallyn_> oops, missed the other line, lemme try a || true after udevadm control --exit
[00:43] <slangasek> hallyn_: Eduard points out on the bug that udevadm control --exit also exits non-zero if it hits the timeout... so you need a || true after that as well, sorry
[00:43] <slangasek> right
[00:44] <slangasek> hallyn_: udev.bak?
[00:44] <hallyn_> yes, init-bottom/udev.bak existed in the initramfs.
[00:44] <slangasek> uh
[00:45] <slangasek> shouldn't be from anything I did
[00:45] <hallyn_> don't nkow how that happened
[00:45] <slangasek> but if it's executable, it'd try to run that as well
[00:45] <hallyn_> it was
[00:45] <hallyn_> probably i messed it up before
[00:53] <hallyn_> haha no /bin/true in initrd
[00:55] <slangasek> right, should just be called as 'true'
[00:55] <slangasek> (shell builtin)
[00:57] <slangasek> hallyn_: and what's the right way to attach to the console?
[00:57] <slangasek> 'virsh console' doesn't give me anything useful
[01:01] <slangasek> ah, of course, there's a separate 'vm-view' command for that - sigh, why is all this separate from virt-manager
[01:05] <slangasek> hallyn_: vm-view doesn't provide much console scrollback... recommendations?
[01:37] <hallyn_> slangasek: i usually just use gvncviewer and store logs to scp off later.  But https://wiki.ubuntu.com/SergeHallyn_libvirtserial   should work
[01:37] <hallyn_> I used to do that for early boot kernel debugging...  Of course your vm then needs to define ttyS0 as a serial port in boot cmdline
[01:41] <slangasek> hallyn_: got it, thanks
[01:55] <slangasek> hallyn_: this hang-on-tty-event thing is just weirding me out.  what's /proc/cmdline for these boots?
[01:55] <slangasek> i.e., do you have a serial console configured when this happens?
[01:56] <slangasek> (because, once again, a tty is the last event processed)
[02:12] <hallyn_> slangasek: no, i don't change cmdline at all
[02:14] <hallyn_> slangasek: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-server root=UUID=442917ed-fe24-4f00-858a-152dbae9db58 ro quiet
[02:15] <hallyn_> yeah no idea why those are always there
[02:51] <slangasek> hallyn_: huzzah, I've reproduced it here - just took me a bit to realize I'd done so, since the initramfs script is fixed here to not die on udevadm timeout :)
[02:51] <slangasek> (which means /dev actually gets mounted properly)
[04:22] <bbigras__> It seems someone edited the main page of the wiki to create his own page. I reverted it and emailed him about it. I hope I did it right because I drank a bit.
[04:23] <slangasek> bbigras__: looks good now, thanks
[04:24] <slangasek> history also shows someone attaching their apt debugging logs to the page, heh
[04:25] <bbigras__> slangasek: Oh that's why I wasn't able to revert to those revisions.
[04:25] <slangasek> yeah, they aren't content changes to the page :)
[06:06] <SanbarComputing> I need to prototype an app for a client that implements peer-to-peer messaging over the internet.  Is there a specific channel for networking and internet oriented development on IRC anywhere?
[06:11] <SanbarComputing> this messaging is not intended for chat or social networking type application, but to enable the application to do peer-to-peer message passing for the purposes of the application functionality unrelated to internet messaging or whatever - just uses the messaging mechanism to communicate between peers
[06:12] <SanbarComputing> indeed ...
[09:05] <slangasek> hggdh, Daviey, hallyn_, adam_g: udev accepted into oneiric with a fix for at least *one* bug.  Please retest at your convenience so we can see what's left that needs stomping...
[11:21] <Laney> doko_: what happened to the maintainer of gdc-4.6 in debian?
[11:22] <doko_> Laney, ?
[11:22] <Laney> http://packages.qa.debian.org/g/gdc-4.6.html
[11:23] <doko_> oops ...
[11:25] <Laney> motu just got mailed about the ftbfs
[13:53] <fishor_> hallo all, please can any one point me to some instruction, how to add patches to debin/patches. and is it possible to use git formated patches? I know i can edit every thing manually, but may be there is some script to do it
[13:56] <penguin42> fishor_: Most of them use quilt I think, so searching for stuff on quilt and debian often finds it
[14:01] <frafu> Hi, In order to test whether a python program is running under GDM, I used the following command:
[14:01] <frafu> if os.environ.has_key('RUNNING_UNDER_GDM'):
[14:02] <frafu> Can anybody please tell me whether there is a similar command for lightdm?
[14:03] <frafu> Maybe:
[14:03] <frafu> if os.environ.has_key('RUNNING_UNDER_LIGHTDM')
[14:03] <frafu> ?
[14:05] <fishor_> penguin42, thank you. i found this manual https://wiki.ubuntu.com/PackagingGuide/PatchSystems
[15:42] <hggdh> slangasek: will do
[15:43] <hggdh> slangasek: will a new ISO be generated, or is it a 0-day?
[15:56] <infinity> hggdh: There will be new ISOs spun on Sunday.
[16:12] <hggdh> infinity: thank you
[16:13] <rhettnaxel> so...
[22:11] <bdrung> tumbleweed: around?
[22:17] <tumbleweed> bdrung: sort of
[22:17] <tumbleweed> (around, but up to my ears in pypy)
[22:19] <bdrung> tumbleweed: i pushed distro-info rearrangement
[22:19] <bdrung> tumbleweed: can you prepare the perl library for distro-info?
[22:25] <binarymutant> does xutils-dev provide xorg-macros?
[22:48] <tumbleweed> bdrung: pushed it, but haven't got to tests yet
[22:51] <bdrung> tumbleweed: now we have to split distro-info into three parts
[22:51] <tumbleweed> yeah
[22:52] <bdrung> tumbleweed: what's with the remove me item?
[22:53] <tumbleweed> oops, that was from debugging, sorry still have my head in pypy
[22:54] <bdrung> tumbleweed: do you want to update your ubuntu email address?
[22:57] <tumbleweed> bdrung: eh?
[22:58] <bdrung> tumbleweed: ubu VS deb mail
[22:59] <tumbleweed> aah, in copyright.
[22:59] <bdrung> tumbleweed: git grep it
[22:59] <bdrung> there are more places