[00:05] <Unit193> So it seems 20.04 shouldn't be our focal point, yet?
[08:42] <xnox> rbasak:  argh =) all of that is fixed with cgroups v2, but yeah, these changes look safe for xenial, to get cgroups agent going.
=== alan_g is now known as alan_g_
[10:17] <sil2100> ahasenack: hey! Just a late heads-up - I unblocked britney in bileto
[10:17] <sil2100> ahasenack: yesterday
[10:18] <sil2100> ahasenack: not sure how it broke but I know what broke: the lock file was constantly locked, probably some britney run didn't properly unlock it after some crash or something
[10:18] <sil2100> Never happened before, but hey
[10:18] <cpaelzer> thanks sil2100
[11:24] <dupondje> LocutusOfBorg: Guess its WAY to late to sync iwd a final time from testing? :)
[11:24] <dupondje> again many improvements in the 0.22 version
[11:26] <LocutusOfBorg> release is in some minutes
[11:26] <LocutusOfBorg> the 0.21 was already syncd during freeze IIRC
[11:26] <LocutusOfBorg> now its *really* too late... specially for the new features
[11:27] <rbasak> xnox: would you mind doing a code review of the patches please, and +1 them in one of the bugs? Then I'll rely on that for SRU review purposes rather than attempting it myself.
[11:27] <LocutusOfBorg> dupondje, unless you can explain why you want it... otherwise better SRU or wait for 20.04
[11:32] <rbasak> xnox: looking for any backporting issues with the patches in particular, such as any interactions introduced in newer upstream that might cause the backport to fail in some edge case.
[11:33] <dupondje> LocutusOfBorg: well nothing very important. But guess its a very infrequently used package :)
[11:33] <dupondje> But I'll just push it to my ppa :)
[11:34] <xnox> rbasak:  ok
[11:38] <rbasak> Thanks!
[12:06] <tomreyn> i ran "sudo apt install ubuntu-desktop-minimal^" on a 19.10 minimal install. I expected nothing to change, but a lot of packages were marked as manually installed (meaning they were previously automatically installed). Is this to be expected?
[12:07] <tomreyn> * previsouly marked as automatically installed
[12:08] <ahasenack> sil2100: thanks!
[12:26] <cjwatson> That matches my expectations of what installing a task does with current apt.  We always sort of wanted it to somehow record that you'd manually installed the task rather than every package in it, but it has no way to remember that
[12:30] <cpaelzer> coreycb: jamespage: do you have balloons defined by default and if so seen any issues migrating those https://bugs.launchpad.net/cloud-archive/+bug/1838569 ?
[12:30] <ubottu> Launchpad bug 1838569 in qemu (Ubuntu) "virtio-balloon change breaks post 4.0 upgrade" [Undecided,Confirmed]
[12:34] <coreycb> cpaelzer: I'm not sure I'd guess by that bug it is defined by default
[12:38] <cpaelzer> coreycb: jamespage: forked from the old bug to its own in https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1848497
[12:38] <ubottu> Launchpad bug 1848497 in qemu (Ubuntu) "virtio-balloon change breaks migration from qemu prior to 4.0" [Undecided,New]
[12:39] <cpaelzer> coreycb: jamespage: could you check if you a) define balloons by default and b) you have tested that for migration from prior to Trains - and then state so on the bug
[12:39] <jamespage> cpaelzer: looking
[12:39] <cpaelzer> I'll try to recreate on my own, but not sure I get to it today - so I wondered if maybe this already might be "in" your test matrix
=== ricab is now known as ricab|lunch
[13:16] <ubuking> hey
=== ricab|lunch is now known as ricab
=== Laney changed the topic of #ubuntu-devel to: Archive: Open | 19.10 Released! | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Trusty-Eoan | If you can't send messages here, authenticate to NickServ first | Patch Pilots:
=== Laney changed the topic of #ubuntu-devel to: Archive: Closed | 19.10 Released! | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Trusty-Eoan | If you can't send messages here, authenticate to NickServ first | Patch Pilots:
[17:30] <Laney> :>
[17:30] <sil2100> <3
[17:33] <tsimonq2> \o/
[20:23] <ahasenack> rbasak: question for tomorrow. What do we usually do, or should do, with the standards-version when backporting a package? Specifically, the upcoming certbot sru, which comes from cosmic. It uses a S-V that is not the current one for bionic
[20:25] <vorlon> S-V is informational only; there's no good reason to do extra work around it
[20:26] <ahasenack> ok