[02:13] LocutusOfBorg1: hey, I think the "initial" state of bug 1513536 was correct in being a merge bug for jquery [02:13] bug 1513536 in jquery (Ubuntu) "[MIR] nodejs?" [Undecided,Incomplete] https://launchpad.net/bugs/1513536 [02:15] if you want to do the merge, you should let doko know, but I don't think he'd mind :) === shadeslayer_ is now known as shadeslayer === Guest13696 is now known as mfisch === mfisch is now known as Guest303 [05:55] 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] dasjoe: on a first guess, probably slangasek, xnox, infinity, or cyphermox would be 'best' for grub2 updates, [10:07] cyphermox, how can I merge something in main that depends from stuff in universe? [10:07] the merge will fail I guess [10:08] * LocutusOfBorg1 sometimes feels like he is missing something [11:06] 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) === _salem is now known as salem_ === salem_ is now known as _salem === _salem is now known as salem_ === salem_ is now known as _salem === shuduo_ is now known as shuduo [15:04] 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] cjwatson: I sent some info to the Debian bug, let me know if I can do anything else === larsu_ is now known as larus === larus is now known as larsu === _salem is now known as salem_ === salem_ is now known as _salem [16:54] slangasek: hey, if you're around, i have a q about pam-auth-update [16:54] specifically, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806841 correctly points out that files under /usr shouldn't be updated. [16:54] Debian bug 806841 in cgmanager "Lame suggestion in README.Debian" [Normal,Open] [16:55] 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] So I need to just ask them to update /etc/pam.d/common-session directly? [16:56] dasjoe: that's fine, thanks [16:56] sarnold: it's OK, I'll handle it (time permitting) [17:00] cyphermox: around? [17:00] lamont: yes [17:00] what's up? [17:03] sorry -meeting [17:05] 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] starting with trust or wily netinst and immediately do-release-upgrade to xenial, same issue [17:05] server install, of course, works just fine [17:05] where should I file the ubg? [17:05] bug [17:07] I don't know [17:07] if you get it after an upgrade too it seems likely that it would be my d-i merges that broke this [17:08] especially since I have yet to merge console-setup and kbd. [17:09] lamont: could you file it against systemd, and assign it to me? I'll try to reproduce it here and dig in [17:11] lamont: was that on a specific architecture? [17:19] cyphermox: amd64 vm [17:19] I'll even toss in the config [17:20] oh, cool [17:20] I already have an amd64 vm installing right now from netboot. [17:20] yeah - boring install... flat out booooooring [17:21] 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] hm [17:22] 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] ok [17:22] once I get back into the machine :( [17:25] oh [17:25] in a separate issue, sda died on the box where all this is happening [17:25] I wonder if that might be an issue with the recent plymouth merge [17:27] ah, got it [17:35] lamont: if you get in grub, edit the command line to remove $vt_handoff [17:36] (that may be doing things wrong, but it should get you a prompt until I make more sense of it all) [19:35] cyphermox: I "just" did my one-off install that I needed, via a server iso. [19:38] ok [19:42] I think my system would boot better if there were kernels in /boot :( [19:43] OTOH, lunch was good. [20:35] lamont: did you file that bug report? [20:55] 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] cyphermox: would pxelinux.0 differnces explain it? (as in using trusty's pxelinux.0 to boot xenial?) [21:01] lamont: I don't believe so [21:01] heh. [21:01] actually, I have this: -rw-r--r-- 1 root root 26461 Apr 23 2012 pxelinux.0 [21:01] I used a very recent mini.iso I built myself from our d-i branch to test console-setup [21:02] so make that a precise pxelinux.0 [21:02] plus what you're booting in the end should be the right-ish kernel for the release [21:03] 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] (so if you haven't filed the bug, perhaps make it against plymouth) [21:13] ah, I'm about "this close" and don't want to star tover... [21:27] https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1528956 <-- cyphermox - I'll let you reassign, if that's ok [21:27] Launchpad bug 1528956 in systemd (Ubuntu) "netinst produces an unusable system" [Undecided,New] [21:27] cyphermox: the fact that the server iso install works, leads me to suspect that it's deps or something ? === cpaelzer is now known as cpaelzer_afk === cpaelzer_afk is now known as cpaelzer === juliank is now known as Guest65871 === juliank0 is now known as juliank === juliank0 is now known as juliank === Unit193 is now known as JackFrost