[00:43] <doko> infinity, there's one more typo ... the setting in COMMON_CONFIGURE_ARGS is ignored
[00:43] <doko> will look at it tomorrow
[01:09] <stokachu> slangasek: fyi ^
[03:21] <phillw> Hi folks, will bug 1555237 be in tomorrow's cron respins (i.e. dated 3rd April) ?
[03:21] <ubot5`> bug 1555237 in systemd (Ubuntu) "Upgrade from 14.04.4→ 16.04 dies midway taking out the session." [Critical,Fix released] https://launchpad.net/bugs/1555237
[03:48] <infinity> Why did the bot just randomly barf a bug ref?
[03:56] <phillw> infinity: it did not, I asked if the fix released"
[03:57] <phillw> infinity: would be in 3rd April cron jobs
[04:35] <cyphermox> phillw: not really affecting the images so much, i suppose
[04:36] <cyphermox> oh, unless you were to try to upgrade from the CD, which probably needs some extra other bug fixes
[04:36] <cyphermox> in any case, it should all be in the next image, yes
[04:37] <phillw> cyphermox: thanks, I like to cover both bases as they are in the iso tracker for bug reporting and one tester has said it all failed... I asked him to re-try after the fix filtered down.
[04:38] <cyphermox> phillw: sure. like I said, I can see why upgrading from the CD might break in other fun ways, it needs testing
[04:39] <cyphermox> but at least the ugly bad failures should already be covered
[04:39] <phillw> cyphermox: no, he did the CLI command, and it failed
[04:39] <cyphermox> phillw: the issue is that this bug is too generic
[04:39] <cyphermox> we fixed one issue in dbus, and another completely unrelated issue in systemd
[04:39] <cyphermox> if there's more, we should have new bugs
[04:44] <phillw> cyphermox: indeed.. the guy is  a good tester, when he awakens, he will crawl all over it like a rash ,,, he is tsimonq2 and is pretty determined when you point him the right direction. He had various error messages, and synaptic package manger (GUI) failed to fix broken... So, I said I'd ask on here as to if things should be working okay. Should he tag onto the existing bug, or file a new one and have it brought to your guys' and gals' a
[04:45] <cyphermox> phillw: my preference is always a new bug, we can easily mark duplicates later, but it's hard to split things up after the fact
[04:46] <cyphermox> usually one bug per error message is a good plan; and one bug for synaptic not being able to fix broken packages
[04:47] <phillw> cyphermox: I concur, but it is always best to ask. Thank you for your time, and as this is logged channel, do you have any objection to my just copying and pasting our chat to him instead of him going through the logs?
[04:47] <cyphermox> not at all
[04:47] <cyphermox> I know tsimonq2
[04:49] <cyphermox> and on that, I log off now since it's very late :)
[04:49] <phillw> I gave him a VM for his 14th b/day present as part of apology for me going 'off topic'. He's doing well, only destryed it once :)
[07:59] <infinity> superm1: Bah.  I fixed the crc32 failure only to hit another failure in the testsuite afterward.  Done with my bored hacking for the night. :P
[09:55] <mapreri> can I poke for 2 RMs?  #1556226 #1556229
[10:26] <ginggs> mapreri: if no response, try on Monday
[10:34] <darkxst> infinity, still around? where does DistUpgradeQuirks get pulled from on a trusty upgrade, doesnt seem to use local copy?
[10:34] <darkxst> see bug 1565177
[10:34] <ubot5`> bug 1565177 in ubuntu-release-upgrader (Ubuntu) "screensaver is not disabled during release upgrade" [High,In progress] https://launchpad.net/bugs/1565177
[10:54] <mapreri> ginggs: Ok.
[10:57] <ginggs> mapreri: instead of hoping there are no rdeps, please include the output of 'reverse-depends src:scribus-ng' in the bug
[10:57] <ginggs> and the same for scribus-ng-doc
[13:14] <tsimonq2> cyphermox: hi, so I used gparted to partition my hard drive, so /dev/sda2 could be used, then I used https://help.ubuntu.com/lts/installation-guide/i386/apds04.html to install Trusty onto the system, along with lubuntu-desktop.
[13:16] <tsimonq2> cyphermox: booted into /dev/sda2 and tried a do-release-upgrade -d. It did not work as expected. It threw some dep errors that I have to Phill in a pastebin. Do I file the build-dep errors as a bug in each of the affected packages? Where do I file the bug?
[13:16] <tsimonq2> cyphermox: and yes, Phill made me try Synaptic (I hate GUI when it comes to package management) and it was not able to fix it, bug against that as well?
[13:19] <phillw> infinity: can you give me a ping, thanks.
[14:02] <superm1> infinity: yup rabbit hole 😃
[14:02] <phillw> superm1: as alice, or the mad hatter ?
[14:03] <superm1> Definitely mad hatter
[18:21] <infinity> darkxst: The dist-upgrader comes from the target release, not the one you're starting from.
[18:22] <infinity> superm1: It wouldn't be a rabbit hole if the testsuite wasn't a single C file with assetions. :/
[18:22] <infinity> superm1: Breaking out all the tests would let me see them all broken at once instead of "yay, I fixed it, oh nevermind, yay I fixed it, oh nevermind".
[18:24] <infinity> superm1: Anyhow, the crc failure is a simple one-liner.  The compiler warnings are a red herring and don't relate (though would be nice to get fixed some day).
[18:24] <infinity> superm1: Now that I'm awake again, I might look at the new failure that fixing the crc failure exposed. :P
[21:18] <superm1> infinity: if you can run interactivity, launching libdfu/dfu-self-test --debug-log --verbose should hopefully get more information about what what was happening since the next thing after CRC doesn't look as straightforward