[02:13] <cyphermox> LocutusOfBorg1: hey, I think the "initial" state of bug 1513536 was correct in being a merge bug for jquery
[02:15] <cyphermox> if you want to do the merge, you should let doko know, but I don't think he'd mind :)
[05:55] <sarnold> dasjoe: probably a bug report against grub2 https://launchpad.net/ubuntu/+source/grub2  would be best; during the next two weeks there's not going to be many people around
[05:57] <sarnold> dasjoe: on a first guess, probably slangasek, xnox, infinity, or cyphermox would be 'best' for grub2 updates,
[10:07] <LocutusOfBorg1> cyphermox, how can I merge something in main that depends from stuff in universe?
[10:07] <LocutusOfBorg1> the merge will fail I guess
[10:08]  * LocutusOfBorg1 sometimes feels like he is missing something
[11:06] <geser> LocutusOfBorg1: check if the other stuff can move to main and file a MainInclusionReport (the alternative is to check if you can drop the other stuff easily)
[15:04] <lamont> wily install and do-release-upgrade -d to xenial, last thing it prints in the rootfs fsck... I suspect there's a missing package, maybe?
[15:30] <dasjoe> cjwatson: I sent some info to the Debian bug, let me know if I can do anything else
[16:54] <hallyn> slangasek: hey, if you're around, i have a q about pam-auth-update
[16:54] <hallyn> specifically, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806841  correctly points out that files under /usr shouldn't be updated.
[16:55] <hallyn> So is there any clean way to ask users to update the shipped defaults?  There is no /etc copy of the /usr/share/pam-configs/ files right?
[16:55] <hallyn> So I need to just ask them to update /etc/pam.d/common-session directly?
[16:56] <cjwatson> dasjoe: that's fine, thanks
[16:56] <cjwatson> sarnold: it's OK, I'll handle it (time permitting)
[17:00] <lamont> cyphermox: around?
[17:00] <cyphermox> lamont: yes
[17:00] <cyphermox> what's up?
[17:03] <lamont> sorry -meeting
[17:05] <lamont> cyphermox: amusing note: current xenial netinst produces a machine that boots to a point where it goes idle, and never produces a prompt
[17:05] <lamont> starting with trust or wily netinst and immediately do-release-upgrade to xenial, same issue
[17:05] <lamont> server install, of course, works just fine
[17:05] <lamont> where should I file the ubg?
[17:05] <lamont> bug
[17:07] <cyphermox> I don't know
[17:07] <cyphermox> if you get it after an upgrade too it seems likely that it would be my d-i merges that broke this
[17:08] <cyphermox> especially since I have yet to merge console-setup and kbd.
[17:09] <cyphermox> lamont: could you file it against systemd, and assign it to me? I'll try to reproduce it here and dig in
[17:11] <cyphermox> lamont: was that on a specific architecture?
[17:19] <lamont> cyphermox: amd64 vm
[17:19] <lamont> I'll even toss in the config
[17:20] <cyphermox> oh, cool
[17:20] <cyphermox> I already have an amd64 vm installing right now from netboot.
[17:20] <lamont> yeah - boring install... flat out booooooring
[17:21] <lamont> and then after it fails, losetup -f -o 1048576 $DISKDEVICE and presto, you have a filesystem you can scrounge around in with /var/log/syslog and everything
[17:22] <cyphermox> hm
[17:22] <cyphermox> I did just get a prompt with an install where I basically just hit enter a couple gazillion times
[17:22]  * lamont will include his tftp/etc
[17:22] <cyphermox> ok
[17:22] <lamont> once I get back into the machine :(
[17:25] <cyphermox> oh
[17:25] <lamont> in a separate issue, sda died on the box where all this is happening
[17:25] <cyphermox> I wonder if that might be an issue with the recent plymouth merge
[17:27] <cyphermox> ah, got it
[17:35] <cyphermox> lamont: if you get in grub, edit the command line to remove $vt_handoff
[17:36] <cyphermox> (that may be doing things wrong, but it should get you a prompt until I make more sense of it all)
[19:35] <lamont> cyphermox: I "just" did my one-off install that I needed, via a server iso.
[19:38] <cyphermox> ok
[19:42] <lamont> I think my system would boot better if there were kernels in /boot :(
[19:43] <lamont> OTOH, lunch was good.
[20:35] <cyphermox> lamont: did you file that bug report?
[20:55] <lamont> cyphermox: not quite yet.  give me about 5 min and I'll be all over it... doing a little bit of headscratching on a different issue
[21:01] <lamont> cyphermox: would pxelinux.0 differnces explain it? (as in using trusty's pxelinux.0 to boot xenial?)
[21:01] <cyphermox> lamont: I don't believe so
[21:01] <lamont> heh.
[21:01] <lamont> actually, I have this: -rw-r--r-- 1 root root 26461 Apr 23  2012 pxelinux.0
[21:01] <cyphermox> I used a very recent mini.iso I built myself from our d-i branch to test console-setup
[21:02] <lamont> so make that a precise pxelinux.0
[21:02] <cyphermox> plus what you're booting in the end should be the right-ish kernel for the release
[21:03] <cyphermox> I think this is something that got changed in the kernel or in plymouth, related to the vt handoff, but I'd need to look harder at that
[21:03] <cyphermox> (so if you haven't filed the bug, perhaps make it against plymouth)
[21:13] <lamont> ah, I'm about "this close" and don't want to star tover...
[21:27] <lamont> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1528956 <-- cyphermox - I'll let you reassign, if that's ok
[21:27] <lamont> cyphermox: the fact that the server iso install works, leads  me to suspect that it's deps or something ?