=== cpaelzer_ is now known as cpaelzer
=== maclin1 is now known as maclin
[07:24] -queuebot:#ubuntu-release- Unapproved: snapd (xenial-proposed/main) [2.32.9 => 2.33] (desktop-core, ubuntu-server)
[07:29] -queuebot:#ubuntu-release- Unapproved: snapd (artful-proposed/main) [2.32.9+17.10 => 2.33+17.10] (desktop-core, ubuntu-server)
[07:29] -queuebot:#ubuntu-release- Unapproved: snapd (bionic-proposed/main) [2.32.9+18.04 => 2.33+18.04] (desktop-core, ubuntu-server)
[07:29] -queuebot:#ubuntu-release- Unapproved: snapd (trusty-proposed/universe) [2.32.9~14.04 => 2.33~14.04] (no packageset)
[08:12]  * apw is handling snapd ^
[08:16] <sil2100> apw: thanks!
[09:12] <caribou> Hello everyone, his this the appropriate place to get in touch with the SRU team or #ubuntu-devel is better ?
[09:27] <apw> caribou, you should find the SRU team here i recon
[09:27] <caribou> apw: morning, I'll repost my question here then :
[09:28] <caribou> There is a dependency issue b/w  kdump-tools (in -updates) and kexec-tools (-proposed) which makes the installation of the linux-crashdump meta-package to fail (Xenial)=
[09:28] <caribou> kdump-tools is depending on the version of kexec-tools which is still in -proposed
[09:28] <apw> that is bad
[09:29] <LocutusOfBorg> guys, does ubuntu 18.10 use merged usr?  https://salsa.debian.org/installer-team/debootstrap/merge_requests/5
[09:29] <gitlab-bot> Debian Installer bug (Merge request) 5 in debootstrap "Re-enable merged-usr by default (after stretch release)" (comments: 5) [Opened]
[09:29] <apw> sil2100, ^ i think you might have been playing along with those
[09:29] <caribou> apw: at least this is my two minute analysis of the situation; when I add -proposed to the sources.list, it installs correctly
[09:29] <LocutusOfBorg> lets not break debootstrap :)
[09:43] <LocutusOfBorg> maybe slangasek has an opinion on merged usr? https://wiki.ubuntu.com/FoundationsTeam/Specs/Quantal/UsrMerge
[09:54] <LocutusOfBorg> I would say to enable it, unless anybody speaks otherwise, it seems to have been done in quantal according to wiki, maybe just not enabled
[10:00] <sil2100> ugh
[10:00] <sil2100> apw, caribou: let me take a look
[10:00] <caribou> apw: thanks!
[10:01] <sil2100> Ah ah, this is unexpected
[10:02] <sil2100> apw: could you by any chance be able to verify LP: #1743529 ?
[10:02] <ubot5> Launchpad bug 1743529 in The Ubuntu-power-systems project "Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic -not syncing: Out of memory message when crash is triggered." [High,In progress] https://launchpad.net/bugs/1743529
[10:03] <sil2100> Since today I released makedumpfile which causes the issue, which got built in -proposed so against the new kexec-tools
[10:03] <sil2100> And we'd need to release that
[10:05] <sil2100> I guess we need to set phasing of makedumpfile to 0
[10:06]  * sil2100 looks into how to do that
[10:10] <sil2100> apw: ok, I guess I can use change-override to set the phased percentage - but do you know how to re-enable phasing afterwards?
[10:21] <sil2100> apw: ok, I have overriden the phased percentage of makedumpfile to 0 so that users don't encounter more upgrade problems
[10:22] <sil2100> caribou: ^
[10:22] <sil2100> Now we need someone to verify the kexec-tools package so we can release it
[10:22] <caribou> sil2100: ok, I'll check
[10:22] <sil2100> caribou: if you got the package then I guess this won't change a thing for you, but new users won't encounter the bug
[10:23] <sil2100> The real fix is getting kexec-tools verified and released ASAP
[10:26] <apw> sil2100, concur
[10:34] <caribou> @sil2100 I don't know if there is some kind of delay, but purging  cleaning, apt update & apt install does the same thing
[10:36] <sil2100> caribou: as said, if you got the update already, you probably will just have it
[10:38] <sil2100> But yeah, I don't know much about the phased upgrades mechanisms myself
[10:39] <caribou> sil2100: not sure that it is all the problem, I'm still looking at it
[10:46] <caribou> sil2100: yes, there is more to it :
[10:46] <caribou> apt install kdump-tools :
[10:46] <caribou> kdump-tools : Depends: kexec-tools (>= 1:2.0.10-2) but it is not going to be installed
[10:47] <caribou> if you apt install kdump-tools kexec-tools, there is even more details :
[10:47] <caribou> kdump-tools : Depends: kexec-tools (>= 1:2.0.10-2) but 1:2.0.10-1ubuntu2.5 is to be installed*
[10:49] <caribou> The SRU will release 1:2.0.16-1ubuntu1~16.04.1 which will still fail
[10:50] <caribou> oh, wait it .16 not .10
[10:52] <sil2100> Should work
[10:52] <caribou> @sil2100 so the answer is to override the phased percentage of kdump-tools as well (built from makedumpfile) which is the one that fails
[10:52] <caribou> yes it will, my mistake
[10:53] <sil2100> caribou: ah! And I did a mistake as well, I thought I have overriden all binaries of the source but I didn't
[10:53] <sil2100> Now it's good
[11:00] <sil2100> cascardo: hey! Maybe you could help out with getting LP: #1743529 verified?
[11:00] <ubot5> Launchpad bug 1743529 in The Ubuntu-power-systems project "Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic -not syncing: Out of memory message when crash is triggered." [High,In progress] https://launchpad.net/bugs/1743529
=== jibel_ is now known as jibel
[11:48] <cascardo> sil2100: so, the makedumpfile and kexec-tools updates are "interlocked"
[11:48] <cascardo> IIRC, makedumpfile in -proposed has a Breaks on kexec-tools on GA/-updates, so you have to release both of them from -proposed
[11:49] <cascardo> but I see, you want a verify of the kexec-tools bug so you can release it
[11:49] <apw> cascardo, one has already escaped ...
[11:50] <cascardo> apw: yah, I noticed that, not sure how one could have verified one without verifying the other, but will do the verification needed myself
[11:51] <apw> cascardo, indeed
[11:55] <sil2100> cascardo: if both had the same bug number and multiple tasks, I'd know not to release one without the other
[11:56] <sil2100> cascardo: but here they seemed disconnected, at least from the bug perspective - which is what I'm looking at mostly before releasing an update
[11:56] <sil2100> Maybe I should have drilled deeper
[11:57] <cascardo> sil2100: I could have warned about it first, as well
[11:57] <cascardo> booting xenial here so I can verify it, will do artful next
[12:06] <cascardo> sil2100: done on xenial
[12:08] <sil2100> cascardo: thanks!
[12:08] <sil2100> Now, I need to figure out how to remove the phased percentage override
[12:13] <sil2100> cjwatson: hey, maybe you'll know: I have overriden a package's phase percentage to 0 through change-override - are overrides of such things handled specially, e.g. do I need to somehow 'disable' the override for things to start phasing again?
[12:14] <sil2100> cjwatson: or does doing .changeOverride() only simply modify the value?
[12:16] <rbasak> There's a bzr branch for overriding phase stops IIRC
[12:16] <rbasak> One moment
[12:17] <rbasak> https://code.launchpad.net/~ubuntu-sru/+junk/phased-update-overrides
[12:17] <rbasak> sil2100: is that what you're after?
[12:17] <rbasak> Actually I think it isn't, sorry
[12:17] <cascardo> sil2100: now, also verified on artful
[12:18] <cjwatson> sil2100: .changeOverride() only sets the current value; actual phasing processes are handled outside Launchpad
[12:18] <cjwatson> I don't recall exactly where
[12:18] <sil2100> cjwatson: ah, ok then!
[12:18] <sil2100> rbasak: oh, didn't know about it, I already used change-override for this
[12:19] <sil2100> I guess my change only stopped it for one moment then
[12:19] <sil2100> ANyway, let me release makedumpfile, switch phasing of the other packages to 10 (as per default) and see how this goes
[12:19] <rbasak> sil2100: I think that has the inverse sense though. It's for override of automatic phasing stops
[12:19] <sil2100> s/makedumpfile/kexec-tools
[12:19] <sil2100> Ah, or that
[12:19] <apw> i thought setting phasing to 0 was the right thing to do to stop it letting anyone having it 'later'
[12:20] <apw> and that once it was 0 it didn't increment automatically any more
[12:20] -queuebot:#ubuntu-release- Unapproved: lastpass-cli (bionic-proposed/universe) [1.0.0-1.2ubuntu1 => 1.0.0-1.2ubuntu2] (no packageset)
[12:20] <apw> not that that stops anyone not using update-manager
[12:20] <rbasak> I wonder how that interacts with automatic phasing though
[12:20] <sil2100> apw: hm, would be good if we had that documented
[12:20] <rbasak> Does the automatic phaser "call" change-override?
[12:20] <sil2100> rbasak: the phaser I guess uses .changeOverride() directly
[12:20] <rbasak> bdmurray will know: ^
[12:20] <sil2100> Which is what change-override does
[12:21] <rbasak> That suggests to me that the phaser needs a second override "blacklist"
[12:21] <sil2100> Anyway, I'd really like these things to be documented, I saw nothing about stopping phasing on the SRU page
[12:21] <rbasak> Unless it automatically detects a phase of 0 means "don't touch"
[12:21] <sil2100> rbasak: from what apw is writing it might be doing just that
[12:21] <sil2100> But bdmurray will know more
[12:22] <apw> the code is in ubuntu-archive-tools
[12:22] <apw> and 0 does look to be special
[12:23] <rbasak> FWIW, we've had a similar problem with grub2-signed before. I think we should adjust sru-release to have a known list of sets that should go together and require a specific force to do anything but release them together
[12:24] <sil2100> britney would have caught this
[12:24] <apw> well we should be checking the britney output
[12:24] <apw> which is running and (as sil2000 says) should have been telling us to release them together
[12:25] <apw> i wonder if there is any way we could get that information surfaced in the penidng-sru report
[12:25] <apw> uggg, i sound like a manager
[12:25] <Laney> The end goal is presumably to *use* proposed-migration to release SRUs?
[12:26] <apw> yes, though we have been talking about that definatly happening for new releases for at least 2
[12:26] <sil2100> caribou: hopefully your problems should be over soon ;)
[12:26] <apw> i think it was deemed too gnarly to retrofit to releases we have simply sru-released a bunch of stuff to
[12:27] <Laney> I mean if people are going to work on SRU tooling, maybe those blockers would be a good use of effort
[12:27] <Laney> not that I'm (a) in the team (b) knowledgable of what the problems are
[12:27] <Laney> :P
[13:33] -queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (artful-proposed/partner) [1:20180508.1-0ubuntu0.17.10.1 => 1:20180607.1-0ubuntu0.17.10.1] (no packageset)
[13:34] -queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (trusty-proposed/partner) [1:20180508.1-0ubuntu0.14.04.1 => 1:20180607.1-0ubuntu0.14.04.1] (no packageset)
[13:34] -queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (bionic-proposed/partner) [1:20180508.1-0ubuntu1 => 1:20180607.1-0ubuntu0.18.04.1] (no packageset)
[13:34] -queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (xenial-proposed/partner) [1:20180508.1-0ubuntu0.16.04.1 => 1:20180607.1-0ubuntu0.16.04.1] (no packageset)
[13:44] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (bionic-proposed) [1:20180607.1-0ubuntu0.18.04.1]
[13:44] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (xenial-proposed) [1:20180607.1-0ubuntu0.16.04.1]
[13:45] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (trusty-proposed) [1:20180607.1-0ubuntu0.14.04.1]
[13:45] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (artful-proposed) [1:20180607.1-0ubuntu0.17.10.1]
=== freyes__ is now known as freyes
=== caribou_ is now known as caribo
=== caribo is now known as caribou
[14:22] -queuebot:#ubuntu-release- Unapproved: apache2 (bionic-proposed/main) [2.4.29-1ubuntu4.1 => 2.4.29-1ubuntu4.2] (ubuntu-server)
[14:24] -queuebot:#ubuntu-release- Unapproved: apache2 (artful-proposed/main) [2.4.27-2ubuntu4.1 => 2.4.27-2ubuntu4.2] (ubuntu-server)
[14:33] -queuebot:#ubuntu-release- Unapproved: gnome-online-accounts (bionic-proposed/main) [3.28.0-0ubuntu2 => 3.28.0-0ubuntu2.1] (ubuntu-desktop)
[14:35] -queuebot:#ubuntu-release- Unapproved: apache2 (xenial-proposed/main) [2.4.18-2ubuntu3.8 => 2.4.18-2ubuntu3.9] (ubuntu-server)
[16:10] <slangasek> LocutusOfBorg: merged usr was a topic of conversation at the Foundations engineering sprint this past week.  I believe the conclusion is that there's no value to our users in doing this by default in advance of Debian doing it.
[16:26] -queuebot:#ubuntu-release- Unapproved: ubiquity (bionic-proposed/main) [18.04.14.1 => 18.04.14.2] (core)
[16:37] <LocutusOfBorg> slangasek, isn't this the default now in Debian?
[16:38] <LocutusOfBorg> slangasek, isn't this the default now in Debian?
[16:38] <LocutusOfBorg> (see the pull request)
[16:39] <slangasek> what pull request?
[16:40] <slangasek> infinity, xnox: ^^ redirecting to you anyway, since this was primarily the two of you having that discussion
[16:41] <LocutusOfBorg> https://salsa.debian.org/installer-team/debootstrap/merge_requests/5
[16:41] <LocutusOfBorg> this one
[16:41] <gitlab-bot> Debian Installer bug (Merge request) 5 in debootstrap "Re-enable merged-usr by default (after stretch release)" (comments: 6) [Opened]
=== maclin1 is now known as maclin
[16:57] <slangasek> LocutusOfBorg: "according to @vorlon this has been implemented in Ubuntu quantal" - uhm what?
[16:57] <slangasek> LocutusOfBorg: the header on that wiki page says "draft"
[16:58] <slangasek> LocutusOfBorg: also, if you look at the page history, I didn't write any of this. :P
[17:01] -queuebot:#ubuntu-release- New: accepted ndctl [source] (cosmic-proposed) [60.1-0ubuntu1]
[17:03] -queuebot:#ubuntu-release- New binary: ndctl [amd64] (cosmic-proposed/none) [60.1-0ubuntu1] (no packageset)
[17:12] -queuebot:#ubuntu-release- New binary: golang-github-json-iterator-go [amd64] (cosmic-proposed/none) [1.0.6-1] (no packageset)
[17:13] -queuebot:#ubuntu-release- New binary: zypper [ppc64el] (cosmic-proposed/none) [1.14.6-1] (no packageset)
[17:14] -queuebot:#ubuntu-release- New binary: golang-github-modern-go-concurrent [amd64] (cosmic-proposed/universe) [1.0.3-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: zypper [amd64] (cosmic-proposed/universe) [1.14.6-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: zypper [i386] (cosmic-proposed/universe) [1.14.6-1] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: zypper [arm64] (cosmic-proposed/universe) [1.14.6-1] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: zypper [armhf] (cosmic-proposed/universe) [1.14.6-1] (no packageset)
[17:24] -queuebot:#ubuntu-release- New binary: zypper [s390x] (cosmic-proposed/universe) [1.14.6-1] (no packageset)
[17:41] -queuebot:#ubuntu-release- Unapproved: rejected initramfs-tools [source] (bionic-proposed) [0.130ubuntu3.1]
[17:41] -queuebot:#ubuntu-release- Unapproved: initramfs-tools (bionic-proposed/main) [0.130ubuntu3 => 0.130ubuntu3.1] (core)
[17:43] <LocutusOfBorg> slangasek, lol, your name was written on that page :)
[17:43] <LocutusOfBorg> I updated the ticket, please ack the change :)
[17:43] <slangasek> LocutusOfBorg: yes, xnox likes to blame me for a lot of things
[17:46] <LocutusOfBorg> :)
[17:46] <LocutusOfBorg> you should be proud of so many pokes! :)
[18:30] <xnox> slangasek, what the quantal?! LocutusOfBorg - your comment does not make sense at all.
[19:35] -queuebot:#ubuntu-release- Unapproved: shim-signed (bionic-proposed/main) [1.34.9 => 1.34.9.1] (core)
[19:53] -queuebot:#ubuntu-release- Unapproved: accepted python-apt [source] (bionic-proposed) [1.6.1]
[23:13] -queuebot:#ubuntu-release- New binary: myspell-lv [amd64] (cosmic-proposed/none) [0.9.6-8] (personal-gunnarhj, ubuntu-desktop)