[00:53] -queuebot:#ubuntu-release- Unapproved: grub2 (trusty-proposed/main) [2.02~beta2-9ubuntu1.15 => 2.02~beta2-9ubuntu1.15] (core)
[01:58] -queuebot:#ubuntu-release- Unapproved: nodejs (bionic-proposed/universe) [8.10.0~dfsg-2ubuntu0.2 => 8.10.0~dfsg-2ubuntu0.3] (kubuntu)
[04:44] -queuebot:#ubuntu-release- New: accepted libglvnd [amd64] (cosmic-proposed) [1.1.0-1]
[04:44] -queuebot:#ubuntu-release- New: accepted libglvnd [armhf] (cosmic-proposed) [1.1.0-1]
[04:44] -queuebot:#ubuntu-release- New: accepted libglvnd [ppc64el] (cosmic-proposed) [1.1.0-1]
[04:44] -queuebot:#ubuntu-release- New: accepted python-httpsig [amd64] (cosmic-proposed) [1.2.0-2]
[04:44] -queuebot:#ubuntu-release- New: accepted libglvnd [arm64] (cosmic-proposed) [1.1.0-1]
[04:44] -queuebot:#ubuntu-release- New: accepted libglvnd [s390x] (cosmic-proposed) [1.1.0-1]
[04:44] -queuebot:#ubuntu-release- New: accepted libglvnd [i386] (cosmic-proposed) [1.1.0-1]
[04:44] -queuebot:#ubuntu-release- New: accepted smrtanalysis [amd64] (cosmic-proposed) [0~20180814]
[05:49] -queuebot:#ubuntu-release- New: rejected zvmcloudconnector [source] (cosmic-proposed) [1.2.3-0ubuntu1]
[05:53] -queuebot:#ubuntu-release- New: rejected vaultlocker [source] (cosmic-proposed) [1.0.1-0ubuntu1]
[05:56] -queuebot:#ubuntu-release- New: accepted fwupd-signed [source] (cosmic-proposed) [1.0]
[05:58] -queuebot:#ubuntu-release- New: rejected jboss-annotations-1.2-api [source] (cosmic-proposed) [1.0.0-0ubuntu1]
[06:10] -queuebot:#ubuntu-release- New binary: jboss-annotations-1.2-api [amd64] (cosmic-proposed/none) [1.0.0-0ubuntu1] (no packageset)
[06:12] -queuebot:#ubuntu-release- New: accepted jboss-annotations-1.2-api [amd64] (cosmic-proposed) [1.0.0-0ubuntu1]
[06:22] -queuebot:#ubuntu-release- Unapproved: libglvnd (bionic-proposed/main) [1.0.0-2ubuntu2.1 => 1.0.0-2ubuntu2.2] (core)
[07:54] -queuebot:#ubuntu-release- New source: vaultlocker (cosmic-proposed/primary) [1.0.3-0ubuntu1]
[07:55] -queuebot:#ubuntu-release- Unapproved: tkblt (bionic-proposed/universe) [3.2.7-1 => 3.2.7-1ubuntu1] (no packageset)
[07:56] <tkamppeter> gutenprint is stuck in cosmic-proposed but it has already passed all the tests more than 24 hours ago. See http://people.canonical.com/~ubuntu-archive/proposed-migration/cosmic/update_excuses.html#gutenprint
[07:58] <acheronuk> tkamppeter: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt
[07:58] <acheronuk> trying: gutenprint
[07:58] <acheronuk> skipped: gutenprint (21, 0, 12)
[07:58] <acheronuk>     got: 16+0: a-3:a-2:a-4:i-3:p-2:s-2
[07:58] <acheronuk>     * i386: photoprint
[07:59] <acheronuk> so that is saying that migrating gutenprint to -release would break photoprint
[08:04] <acheronuk> photoprint depends libgutenprint2 (>= 5.2.13), whereas in gutenprint in -proposed libgutenprint2 lib package no longer exists. so I guess you need to rebuild photoprint against new gutenprint
[08:15] <tkamppeter> acheronuk thank you very much.
[08:15] <acheronuk> tkamppeter: sadly looks like current photoprint will FTBFS on a rebuild: https://launchpad.net/~rikmills/+archive/ubuntu/cosmic/+sourcepub/9332953/+listing-archive-extra
[08:24] <Laney> doko: any thoughts on removing transcode and the things which depend on it?
[08:24] <Laney> none of them in debian, not maintained in ubuntu apart from people patching transcode when it breaks with new ffmpeg like it is doing now
[09:05] <tkamppeter> acheronuk, I have found out this, too. For me it looks like that we should better remove it altogether, as its last release is from 2010, and I do not want to fix a stone-old package to unblock the progress on other packages.
[09:05] <tkamppeter> acheronuk, can we simply remove this obsolete package?
[09:07] <acheronuk> tkamppeter: up to archive admin (which I am not even close to). I would usually file a bug against the package as per: https://wiki.ubuntu.com/UbuntuDevelopment/PackageArchive#Removing_Packages
[09:08] <acheronuk> maybe ping AAs in here if it needs sorting quickly
=== JamieBennett_ is now known as JamieBennett
=== popey_ is now known as popey
[09:23] <tkamppeter> acheronuk, it needs to get fixed before Feature Freeze so that the new Gutenprint gets in.
[09:27] <acheronuk> tkamppeter: for the purposes of Feature Freeze, being in -proposed counts as 'in', so you would not need a freeze exception for current version in proposed or bugfix updates to it
[09:27] <tkamppeter> acheronuk, on https://wiki.ubuntu.com/UbuntuDevelopment/PackageArchive#Removing_Packages the paragraph "There is checkrdepends in ubuntu-archive-tools, but it needs a mirror to work with." can be removed, this utility and package do not exist any more.
[09:30] <acheronuk> tkamppeter: never used that. usually I just do something like https://paste.ubuntu.com/p/K6HWkM2GxM/
[09:32] <acheronuk> tkamppeter: checkrdepends is still in https://bazaar.launchpad.net/~ubuntu-archive/ubuntu-archive-tools/trunk/files , but as said not very easy to use for normal people!
[09:40] <tkamppeter> acheronuk: https://bugs.launchpad.net/ubuntu/+source/photoprint/+bug/1787146
[09:40] <ubot5> Ubuntu bug 1787146 in photoprint (Ubuntu) "[PLEASE REMOVE] PhotoPrint is not maintained any more and blocks Gutenprint update" [High,New]
[09:40] <tkamppeter> acheronuk, did I do this correctly or is there still anything missing?
[09:46] <acheronuk> tkamppeter: seems ok to me. since it's not removed in debian yet, AAs might conceivably want to demote to proposed rather than remove completely, but that would still let gutenprint though. would be flogging a dead horse IMO though
[09:46] <acheronuk> apw Laney: if you have a sec, does that look reasonable?
[09:47] <tkamppeter> Yes.
[10:10] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (bionic-proposed/main) [2.525.6 => 2.525.7] (desktop-core)
[11:05] <apw> tkamppeter, i've demoted it to -proposed in the first instance; your reasons for removal seem reaosnable but just don't have time to think on it properly
[11:05] <Laney> Probably a block-proposed tag on that bug would be a good idea
[11:05]  * Laney added
[11:11] -queuebot:#ubuntu-release- Unapproved: accepted appstream-glib [source] (xenial-proposed) [0.5.13-1ubuntu6]
[11:11] -queuebot:#ubuntu-release- New binary: verbiste [s390x] (cosmic-proposed/universe) [0.1.45-3] (no packageset)
[11:12] -queuebot:#ubuntu-release- New binary: verbiste [ppc64el] (cosmic-proposed/universe) [0.1.45-3] (no packageset)
[11:14] -queuebot:#ubuntu-release- New binary: verbiste [amd64] (cosmic-proposed/universe) [0.1.45-3] (no packageset)
[11:14] -queuebot:#ubuntu-release- New binary: verbiste [armhf] (cosmic-proposed/universe) [0.1.45-3] (no packageset)
[11:14] -queuebot:#ubuntu-release- New binary: verbiste [arm64] (cosmic-proposed/universe) [0.1.45-3] (no packageset)
[11:15] -queuebot:#ubuntu-release- New binary: verbiste [i386] (cosmic-proposed/universe) [0.1.45-3] (no packageset)
[11:29] <Laney> ah, emacs25 is replaced with emacs, that explains the upload failures
[11:29] <Laney> and of course emacs is blocked :<
[12:23] <tkamppeter> acheronuk, apw, Laney: Thank you very much. Gutenprint has advanced to the release now.
[12:47] <acheronuk> tkamppeter: :) your are welcome
[12:47] <acheronuk> *you
[13:15] -queuebot:#ubuntu-release- Unapproved: evince (bionic-proposed/main) [3.28.2-1 => 3.29.91-1ubuntu2] (ubuntu-desktop)
[13:16] -queuebot:#ubuntu-release- Unapproved: rejected samba [source] (trusty-proposed) [2:4.3.11+dfsg-0ubuntu0.14.04.15]
[13:16] -queuebot:#ubuntu-release- Unapproved: rejected samba [source] (xenial-proposed) [2:4.3.11+dfsg-0ubuntu0.16.04.14]
[13:18] <jbicha> please reject evince
[13:23] -queuebot:#ubuntu-release- Unapproved: rejected evince [source] (bionic-proposed) [3.29.91-1ubuntu2]
[13:23] <apw> jbicha, ^ ... wrong series ?
[13:25] <jbicha> yes, thanks :)
[13:25] <jbicha> I installed cosmic's devscripts now so "dch -r" does what I expect
[14:04] -queuebot:#ubuntu-release- New binary: fwupd-signed [amd64] (cosmic-proposed/universe) [1.1] (no packageset)
[14:04] -queuebot:#ubuntu-release- New binary: fwupd-signed [armhf] (cosmic-proposed/universe) [1.1] (no packageset)
[14:04] -queuebot:#ubuntu-release- New binary: fwupd-signed [arm64] (cosmic-proposed/universe) [1.1] (no packageset)
[14:04] -queuebot:#ubuntu-release- New binary: fwupd-signed [i386] (cosmic-proposed/universe) [1.1] (no packageset)
[14:07] <doko> Laney: could you have a look at gcc-6 triggered by binutils? still marked as running ...
[14:07] <Laney> doko: ok, swap you for my earlier question?
[14:07] <doko> and just ignore it
[14:07] <doko> Laney: what to dou want to swap for the brotli fix?
[14:07] <doko> yes, I'll look
[14:09] -queuebot:#ubuntu-release- New: accepted fwupd-signed [amd64] (cosmic-proposed) [1.1]
[14:09] -queuebot:#ubuntu-release- New: accepted fwupd-signed [armhf] (cosmic-proposed) [1.1]
[14:09] -queuebot:#ubuntu-release- New: accepted vaultlocker [source] (cosmic-proposed) [1.0.3-0ubuntu1]
[14:09] -queuebot:#ubuntu-release- New: accepted verbiste [arm64] (cosmic-proposed) [0.1.45-3]
[14:09] -queuebot:#ubuntu-release- New: accepted verbiste [i386] (cosmic-proposed) [0.1.45-3]
[14:09] -queuebot:#ubuntu-release- New: accepted verbiste [s390x] (cosmic-proposed) [0.1.45-3]
[14:09] -queuebot:#ubuntu-release- New: accepted fwupd-signed [arm64] (cosmic-proposed) [1.1]
[14:09] -queuebot:#ubuntu-release- New: accepted verbiste [amd64] (cosmic-proposed) [0.1.45-3]
[14:09] -queuebot:#ubuntu-release- New: accepted verbiste [ppc64el] (cosmic-proposed) [0.1.45-3]
[14:09] -queuebot:#ubuntu-release- New: accepted fwupd-signed [i386] (cosmic-proposed) [1.1]
[14:09] -queuebot:#ubuntu-release- New: accepted verbiste [armhf] (cosmic-proposed) [0.1.45-3]
[14:09] <doko> Laney: transcode, needs a bug report, subscribing ubuntu-archive, and checking for all rdepends
[14:10] <doko> I'm all for removing non-maintained stuff
[14:10] <Laney> ok, I wanted to know if it was an option
[14:10] <Laney> thx
[14:10]  * doko looks around for other archive admins ...
[14:11] <doko> ok, agreed =)
[14:11]  * apw looks up
[14:11] <Laney> it's a trap
[14:11]  * apw runs for the hills in his 7 league boots
[14:11] -queuebot:#ubuntu-release- New binary: vaultlocker [amd64] (cosmic-proposed/none) [1.0.3-0ubuntu1] (no packageset)
[14:12] -queuebot:#ubuntu-release- New: accepted vaultlocker [amd64] (cosmic-proposed) [1.0.3-0ubuntu1]
[14:17] <doko> Laney: emacs was a trap too, needs two MIRs =)
[14:18] <doko> isn't emacs25 obsolete by now?
[14:18] -queuebot:#ubuntu-release- Unapproved: samba (trusty-proposed/main) [2:4.3.11+dfsg-0ubuntu0.14.04.16 => 2:4.3.11+dfsg-0ubuntu0.14.04.17] (core)
[14:18] -queuebot:#ubuntu-release- Unapproved: samba (xenial-proposed/main) [2:4.3.11+dfsg-0ubuntu0.16.04.15 => 2:4.3.11+dfsg-0ubuntu0.16.04.16] (core)
[14:19] <Laney> should be once emacs can migrate
[14:19] -queuebot:#ubuntu-release- Unapproved: maas (bionic-proposed/main) [2.4.0-6981-g011e51b7a-0ubuntu1~18.04.1 => 2.4.1-7032-g11e4fa330-0ubuntu1~18.04.1] (ubuntu-server)
[14:20] <Laney> this is weird, I don't see the request for gcc-6/amd64
[14:20]  * Laney checks britney log
[14:22] <Laney> no error there...
[14:22] <Laney> ...
[14:30] <Laney> resubmitted
[14:33] <Laney> doko: https://bugs.launchpad.net/ubuntu/+source/subtitleripper/+bug/1787222
[14:33] <ubot5> Ubuntu bug 1787222 in transcode (Ubuntu) "Remove transcode and friends from cosmic" [Undecided,Confirmed]
[14:33] <Laney> going to upload to drop those recommends now
[14:34] <Laney> laney@bionic (master|✔)> head -1 debian/changelog                                                      ~/temp/k3b
[14:34] <Laney> k3b (2.0.2-6ubuntu1) raring-proposed; urgency=low
[14:34] <Laney> ...
[14:34] <Laney> guess they're not using that vcs :-)
[14:37] <Laney> although xjadeo has that in Debian too: should I add a delta to drop it or file a bug there and leave it?
[14:48] <Laney> doko: what are the MIRs you are after for emacs?
[14:49] <Laney> I can see that nox and gtk are in universe but they're built from the emacs source
[14:55] <acheronuk> Laney: thanks for doing k3b.
[14:55] <Laney> Nae bother
[14:56] <Laney> This transition is edging along but there's still a fair bit of work to do
[15:00] <acheronuk> Laney: I have KDEPIM and KDE framework uploads that I have basically been sitting on waiting for the Qt transition, since some packages depend on Qtbase/Qtdeclarative ABI. I assume that heaven forbid, should we cross over to feature freeze without this done, those uploads will be treated kindly for a FFE (they are well tested).
[15:02] <acheronuk> I assume they would. I guess this is more of a FYI that they are sitting there waiting, than anything else :)
[15:04] <Laney> We usually give flavours a decent degree of freedom over their own packages anyway
[15:07] <acheronuk> Laney: thanks. I guess I'm just seeking reassurance, as this release seem like I've done not much apart from waiting on Qt, and uploads I have done recently have all got wedged in proposed
[15:48] <apw> juliank, you appear to have disabled libnewt0.52-udeb in src:newt ... what was that about ?
[15:49] <apw> that seems to have broken debian-installer
[15:49] <juliank> apw: Did not want to introduce a new udeb we don't need
[15:49] <juliank> There was some transition in d-i upstream
[15:49] <apw> hmmm, it seems that d-i needs it already
[15:49] <juliank> Well, it was not there before, so I did not turn it on
[15:49] <apw> u wi
[15:50] <apw> i wonder why d-i suddenly knows about it ...
[15:50] <juliank> If it's needed now, feel free to enable it
[15:50] <apw> juliank, will do, thanks
[15:52] <Laney> apw: do you fancy looking at https://bugs.launchpad.net/ubuntu/+source/gmerlin-encoders/+bug/1787239 ?
[15:52] <ubot5> Ubuntu bug 1787239 in gmerlin-encoders (Ubuntu) "Kick gmerlin-encoders out to proposed" [Undecided,Confirmed]
[15:52]  * Laney isn't up for fixing all this broken sort of unmaintained stuff
[15:53] <apw> cirtainly that sounds like -proposed material to me
[15:55] <Laney> thx
[15:55] <Laney> so many broken things
[15:56] <Laney> sometimes you find one fix which makes a load of stuff go installable
[15:56] <Laney> but I didn't manage to do that sofar
[15:58] <apw> Laney, done
[15:58] <Laney> mwah
[15:58] <doko> Laney: http://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg xaw3d xutils-dev
[15:59] -queuebot:#ubuntu-release- Unapproved: rejected catfish [source] (bionic-proposed) [1.4.6-0ubuntu0.18.04.1]
[15:59] -queuebot:#ubuntu-release- New binary: newt [s390x] (cosmic-proposed/main) [0.52.20-4ubuntu3] (core)
[16:00] <superman1> I just upgraded from 16.04 to 18.04 and I was seeing lightdm fail to load and purple screen hang. I went to ctrl+alt+f2 and did a reinstall of lightdm. This brought me to login screen. But now I have no "network". ifconfig only returns the loopback interface.
[16:00] <superman1> Any suggestions?
[16:00] -queuebot:#ubuntu-release- New binary: newt [amd64] (cosmic-proposed/main) [0.52.20-4ubuntu3] (core)
[16:00] -queuebot:#ubuntu-release- New binary: newt [ppc64el] (cosmic-proposed/main) [0.52.20-4ubuntu3] (core)
[16:00] <superman1> I am also stuck at login loop on the Alt-f1
[16:01] <superman1> I upgraded using do-release-upgrade.
[16:01] <Laney> superman1: This isn't a support channel - try #ubuntu please
[16:01] <Laney> doko: oh ://////////
[16:01] <superman1> Laney: okies. thanks.
[16:02] -queuebot:#ubuntu-release- New binary: newt [armhf] (cosmic-proposed/main) [0.52.20-4ubuntu3] (core)
[16:02] -queuebot:#ubuntu-release- New binary: newt [i386] (cosmic-proposed/main) [0.52.20-4ubuntu3] (core)
[16:02] -queuebot:#ubuntu-release- New: accepted newt [amd64] (cosmic-proposed) [0.52.20-4ubuntu3]
[16:02] -queuebot:#ubuntu-release- New: accepted newt [i386] (cosmic-proposed) [0.52.20-4ubuntu3]
[16:02] -queuebot:#ubuntu-release- New: accepted newt [s390x] (cosmic-proposed) [0.52.20-4ubuntu3]
[16:02] -queuebot:#ubuntu-release- New: accepted newt [armhf] (cosmic-proposed) [0.52.20-4ubuntu3]
[16:02] -queuebot:#ubuntu-release- New binary: newt [arm64] (cosmic-proposed/main) [0.52.20-4ubuntu3] (core)
[16:02] -queuebot:#ubuntu-release- New: accepted newt [ppc64el] (cosmic-proposed) [0.52.20-4ubuntu3]
[16:03] -queuebot:#ubuntu-release- New: accepted newt [arm64] (cosmic-proposed) [0.52.20-4ubuntu3]
[16:04] <Laney> doko: wait, is that because it chose emacs-lucid to satisfy the alternate dep?
[16:49] <superm1> hi can an AA remove and block these from syncing https://launchpad.net/ubuntu/+source/fwupdate-amd64-signed https://launchpad.net/ubuntu/+source/fwupdate-arm64-signed https://launchpad.net/ubuntu/+source/fwupdate-i386-signed ? They're causing problems with https://launchpad.net/ubuntu/+source/fwupdate-signed/1.20
[17:00] <slangasek> superm1: hi!  I had noticed things going on there and wanted to ask why both fwupd and fwupdate are now producing artifacts for EFI signing
[17:01] <slangasek> maybe that's all resolved now and we only need to handle the -signed packages now
[17:01] <superm1> slangasek, i sent some mail to sil2100 to explain it all
[17:01] <superm1> but i guess that didn't float around to everyone that needs to know
[17:01] <slangasek> yes, emailing an individual has that effect :)
[17:02] <superm1> heh. so basically starting with fwupd 1.1.0 the library and EFI binaries were subsumed into the fwupd project
[17:02] <superm1> they are installed dynamically at runtime now
[17:03] <superm1> lots of various reasons for this, but the general expectation is that due to this change less bugs, better control on the process, easier to support problems
[17:03] <superm1> the fwupdate project still exists and can be treated as a simple reference implementation of EFI firmware updates if you don't care about all the other stuff
[17:04] <superm1> in my mind fwupdate and fwupdate-signed should move to universe in cosmic
[17:04] <slangasek> superm1: http://archive.ubuntu.com/ubuntu/dists/cosmic-proposed/main/uefi/fwupdate-amd64/current/fwupx64.efi.signed http://archive.ubuntu.com/ubuntu/dists/cosmic-proposed/main/uefi/fwupd-amd64/1.1.1-1/fwupdx64.efi.signed why are there two of these?
[17:04] <superm1> see above two comments
[17:05] <slangasek> so
[17:05] <superm1> I unseeded fwupdate for this purpose on the next meta upload: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/platform/commit/?id=e44246ad2a65dacc3e816715d0df7bd86cd9a2ac
[17:05] <slangasek> we shouldn't be signing two streams of EFI binaries
[17:05] <slangasek> we shouldn't be signing something that's just a "reference implementation"
[17:05] <cyphermox> moo?
[17:05] <superm1> Moo
[17:05] <slangasek> and it's regrettable if sil2100 accepted these for signing on the basis of your conversation
[17:06] <slangasek> we should instead drop the signing request bits from the package
[17:06] <superm1> Debian is still going to sign both of them
[17:06] <slangasek> I'm not responsible for Debian's EFI keys :)
[17:06] <superm1> and let folks decide if they want to use one or the other
[17:06] <cyphermox> oh my
[17:09] <superm1> Sledge told me that infinity and cjwatson had interest in Debian's EFI signing system as well and are going to look into it.  If Ubuntu adopts something akin to it it will be more difficult to drop the signed bits only from Ubuntu for fwupdate
[17:10] <slangasek> sorry, if Ubuntu adopts something akin to what?
[17:10] <superm1> the signing process for EFI binaries
[17:10] <slangasek> ok
[17:11] <superm1> right now what happens in Debian is that template packages are created and go itno the archive as binary packages
[17:11] <slangasek> so, regardless, my expectation is that the set of objects signed with the EFI key will be gated on archive admin signoff
[17:11] <superm1> a signing service runs and installs these template packages and produces new source packages "with the signed" binary
[17:11] <superm1> and those source packages are uploaded to the archive
[17:11] <superm1> so yes I would expect the gate to be on accepting "those" source packages
[17:12] -queuebot:#ubuntu-release- New binary: docker [amd64] (cosmic-proposed/universe) [1.5-1.1] (no packageset)
[17:12] -queuebot:#ubuntu-release- New binary: duktape [s390x] (cosmic-proposed/universe) [2.3.0-1] (no packageset)
[17:13] -queuebot:#ubuntu-release- New binary: duktape [amd64] (cosmic-proposed/universe) [2.3.0-1] (no packageset)
[17:13] -queuebot:#ubuntu-release- New binary: duktape [ppc64el] (cosmic-proposed/universe) [2.3.0-1] (no packageset)
[17:13] <superm1> slangasek, the other thing i'm worried about with demoting fwupdate to universe and dropping fwupdate-signed is I have no idea what that does to ubuntu core guys
[17:13] <superm1> if they still use it for generating images or what
[17:13] <superm1> it's in the "system-image" seed and I suspect they have an expectation that they get the EFI binary installed as part of "core" and not at runtime
[17:14] -queuebot:#ubuntu-release- New binary: duktape [arm64] (cosmic-proposed/universe) [2.3.0-1] (no packageset)
[17:14] -queuebot:#ubuntu-release- New binary: duktape [i386] (cosmic-proposed/universe) [2.3.0-1] (no packageset)
[17:14] -queuebot:#ubuntu-release- New binary: duktape [armhf] (cosmic-proposed/universe) [2.3.0-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: git-sizer [s390x] (cosmic-proposed/universe) [1.2.0+dfsg-1] (no packageset)
[17:18] <cjwatson> superm1: It's not likely to happen any time soon
[17:18] -queuebot:#ubuntu-release- New binary: eclipse-debian-helper [amd64] (cosmic-proposed/universe) [1.0] (no packageset)
[17:18] -queuebot:#ubuntu-release- New binary: minetest-mod-lucky-block [amd64] (cosmic-proposed/universe) [0.8-1] (no packageset)
[17:18] -queuebot:#ubuntu-release- New binary: git-sizer [ppc64el] (cosmic-proposed/universe) [1.2.0+dfsg-1] (no packageset)
[17:18] <cjwatson> Any such change would be distinctly non-trivial
[17:19] -queuebot:#ubuntu-release- New binary: git-sizer [amd64] (cosmic-proposed/universe) [1.2.0+dfsg-1] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: minetest-mod-unified-inventory [amd64] (cosmic-proposed/universe) [20180704-1] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: minetest-mod-protector [amd64] (cosmic-proposed/universe) [2.6-1] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: drms [amd64] (cosmic-proposed/universe) [0.5.5-1] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: python-numpysane [amd64] (cosmic-proposed/universe) [0.15-1] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: git-sizer [i386] (cosmic-proposed/universe) [1.2.0+dfsg-1] (no packageset)
[17:19] <superm1> cjwatson, OK thanks, I sorta expected that
[17:19] <cjwatson> There are pros and cons; it may be worth it for the sake of being in sync, and I can see the advantages
[17:20] <cjwatson> Particularly reducing the number of round-trips for updates
[17:20] -queuebot:#ubuntu-release- New binary: iraf-mscred [ppc64el] (cosmic-proposed/universe) [5.05+2018.07.09-1] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: iraf-sptable [i386] (cosmic-proposed/universe) [1.0~pre20180612-1] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: iraf-sptable [amd64] (cosmic-proposed/universe) [1.0~pre20180612-1] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: iraf-sptable [ppc64el] (cosmic-proposed/universe) [1.0~pre20180612-1] (no packageset)
[17:20] <cjwatson> But it doesn't make it an easy change to implement :)
[17:20] <superm1> yeah from a package maintainer perspective it's nice to not have to update a separate signed -source package
[17:20] <cjwatson> And it's hard to justify spending time on it when it just streamlines things a bit rather than enabling new functionality
[17:21] -queuebot:#ubuntu-release- New binary: iraf-mscred [amd64] (cosmic-proposed/universe) [5.05+2018.07.09-1] (no packageset)
[17:21] <superm1> I think Debian is still working out kinks with their system anyway, it doesn't run automatically just yet
[17:21] <cjwatson> Indeed
[17:22] -queuebot:#ubuntu-release- New binary: git-sizer [arm64] (cosmic-proposed/universe) [1.2.0+dfsg-1] (no packageset)
[17:22] -queuebot:#ubuntu-release- New binary: iraf-mscred [i386] (cosmic-proposed/universe) [5.05+2018.07.09-1] (no packageset)
[17:22] <cjwatson> In a Launchpad context it would involve dispatching subsidiary builds, I think
[17:22] <cjwatson> Which is ... complex
[17:22] <superm1> I see
[17:22] <cjwatson> I kind of know what sort of general shape I'd like it to be but haven't worked out the data model
[17:23] <cjwatson> What we definitely *can't* do is construct debs somewhere other than on builders
[17:23] <superm1> I think even in their model the debs would be constructed on builders
[17:24] <cjwatson> Yeah, I haven't seen how the dispatch works there ...
[17:24] -queuebot:#ubuntu-release- New binary: git-sizer [armhf] (cosmic-proposed/universe) [1.2.0+dfsg-1] (no packageset)
[17:24] <superm1> their model generates source packages that get uploaded
[17:24] <cjwatson> Right, what I haven't worked out is how those get injected
[17:24] <cjwatson> And whether there's any DB link between those and the unsigned versions
[17:25] <cjwatson> I'd kind of rather construct the source packages on builders too
[17:25] <cjwatson> Like recipes
[17:25] <cjwatson> That means we get to use tools appropriate to the target series to build the source package, rather than having to either do it by hand or have interesting dependencies on the Ubuntu release that Launchpad happens to run on
[17:26] <cjwatson> (ICBW but I suspect that Debian is taking something equivalent to the latter approach)
[17:26] <cjwatson> Recipes have some pretty weird DB modelling though
[17:27] -queuebot:#ubuntu-release- New binary: iraf-sptable [arm64] (cosmic-proposed/universe) [1.0~pre20180612-1] (no packageset)
[17:27] <cjwatson> Anyway, that's as far as I've got
[17:27] <superm1> building the source package outside of a builder is actually quite challenging from the debian side today
[17:27] <superm1> if it fails to build you have no idea why
[17:28] -queuebot:#ubuntu-release- New binary: iraf-mscred [armhf] (cosmic-proposed/universe) [5.05+2018.07.09-1] (no packageset)
[17:28] <superm1> so if you deviated from the "template" used by another signed package a little bit or have a minor typographical error you can't really debug
[17:29] -queuebot:#ubuntu-release- New binary: iraf-mscred [arm64] (cosmic-proposed/universe) [5.05+2018.07.09-1] (no packageset)
[17:29] -queuebot:#ubuntu-release- New binary: iraf-sptable [armhf] (cosmic-proposed/universe) [1.0~pre20180612-1] (no packageset)
[17:30] <superm1> so back on the initial question around fwupdate/fwupdate-signed and what to do with them.  I'll file a bug with this conversation and subscribe ubuntu-archive and whoever is the right person from ubuntu-core that can commment what ripping fwupdate and fwupdate-signed out of system-image does.  slangasek any idea who from core can speak to that?
[17:31] <cjwatson> https://salsa.debian.org/ftp-team/code-signing/blob/master/secure-boot-code-sign.py is the relevant thing in Debian; definitely looks like that's just going to run with (I assume) stable's dpkg-dev
[17:31] <cjwatson> which I guess isn't awful since dpkg-dev is pretty stable, but I'd hope not to have to install it on LP systems
[17:32] <cjwatson> we'd need an isolated signing service in the same way
[17:32] <superm1> the other dimension I didn't mention is that there may be a need for backporting either fwupdate 12 or fwupd 1.1.1 back to bionic due to https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1785165  I guess i'll add that to the bug for discussion too
[17:32] <ubot5> Ubuntu bug 1785165 in fwupdate-signed (Ubuntu) "firmware update on fwupdate version 10-3 not work on some AMI's firmwares" [Undecided,New]
[17:41] <slangasek> superm1: I would have to check what's done with fwupdate in Ubuntu Core, but snaps are not necessarily built from the devel series and core snaps in particular are only built from LTSes.  So any change that's appropriate to make here in terms of preferred EFI implementation for Ubuntu classic should also be tracked by Ubuntu Core in the next major series, and would not affect builds of the
[17:41] <slangasek> current series.
[17:42] <superm1> I guess this is now a bigger problem then for them that snaps probably can't put binaries into the ESP directly
[17:43] <superm1> and they'll have to sort that in snapd by the next LTS?
[17:43] <slangasek> quite possibly
[17:44] <slangasek> do the two executables (fwupx64.efi, fwupdx64.efi) provide the same interface?  Do they get installed to the same well known location on the ESP?
[17:44] <superm1> they purposefully use a different EFI NVRAM variable to communicate information
[17:45] <superm1> and both get installed into respective binary names (fwupx64.efi or fwupdx64.efi)
[17:45] <superm1> to allow both implementations to be installed side by side
[17:45] <slangasek> well, that does make a transition more complicated
[17:46] <superm1> depends on which lens you look at it from.  it allows the contents of the NVRAM interface variable to change in incompatible ways in the future
[17:48] <slangasek> fwiw I can't find anything in snapd source code that installs fwupx64.efi to the ESP, and I know I haven't seen this in the gadget snaps
[17:50] <slangasek> superm1: anyway, when you file that bug, please subscribe me directly as well, and for the ubuntu-core side I think I'd start with ~chipaca
[17:50] <superm1> OK thanks, will do
[17:51] <superm1> OK bug 1787254
[17:51] <ubot5> bug 1787254 in fwupdate-signed (Ubuntu) "Possibly demote fwupdate to universe?" [Undecided,New] https://launchpad.net/bugs/1787254
[17:57] <slangasek> superm1: ah, and wrt your original request to remove+blacklist fwupdate-{amd64,i386,arm64}-signed, please file a bug for this as well so there's an audit trail
[18:00] -queuebot:#ubuntu-release- New: accepted drms [amd64] (cosmic-proposed) [0.5.5-1]
[18:00] -queuebot:#ubuntu-release- New: accepted git-sizer [armhf] (cosmic-proposed) [1.2.0+dfsg-1]
[18:00] -queuebot:#ubuntu-release- New: accepted iraf-mscred [amd64] (cosmic-proposed) [5.05+2018.07.09-1]
[18:00] -queuebot:#ubuntu-release- New: accepted iraf-mscred [armhf] (cosmic-proposed) [5.05+2018.07.09-1]
[18:00] -queuebot:#ubuntu-release- New: accepted iraf-mscred [ppc64el] (cosmic-proposed) [5.05+2018.07.09-1]
[18:00] -queuebot:#ubuntu-release- New: accepted iraf-sptable [arm64] (cosmic-proposed) [1.0~pre20180612-1]
[18:00] -queuebot:#ubuntu-release- New: accepted iraf-sptable [i386] (cosmic-proposed) [1.0~pre20180612-1]
[18:00] -queuebot:#ubuntu-release- New: accepted minetest-mod-protector [amd64] (cosmic-proposed) [2.6-1]
[18:00] -queuebot:#ubuntu-release- New: accepted python-numpysane [amd64] (cosmic-proposed) [0.15-1]
[18:00] -queuebot:#ubuntu-release- New: accepted git-sizer [arm64] (cosmic-proposed) [1.2.0+dfsg-1]
[18:00] -queuebot:#ubuntu-release- New: accepted iraf-mscred [arm64] (cosmic-proposed) [5.05+2018.07.09-1]
[18:00] -queuebot:#ubuntu-release- New: accepted iraf-sptable [amd64] (cosmic-proposed) [1.0~pre20180612-1]
[18:00] -queuebot:#ubuntu-release- New: accepted iraf-sptable [ppc64el] (cosmic-proposed) [1.0~pre20180612-1]
[18:00] -queuebot:#ubuntu-release- New: accepted git-sizer [i386] (cosmic-proposed) [1.2.0+dfsg-1]
[18:00] -queuebot:#ubuntu-release- New: accepted iraf-sptable [armhf] (cosmic-proposed) [1.0~pre20180612-1]
[18:00] -queuebot:#ubuntu-release- New: accepted iraf-mscred [i386] (cosmic-proposed) [5.05+2018.07.09-1]
[18:00] -queuebot:#ubuntu-release- New: accepted minetest-mod-unified-inventory [amd64] (cosmic-proposed) [20180704-1]
[18:00] -queuebot:#ubuntu-release- New: accepted docker [amd64] (cosmic-proposed) [1.5-1.1]
[18:00] -queuebot:#ubuntu-release- New: accepted duktape [arm64] (cosmic-proposed) [2.3.0-1]
[18:00] -queuebot:#ubuntu-release- New: accepted duktape [i386] (cosmic-proposed) [2.3.0-1]
[18:00] -queuebot:#ubuntu-release- New: accepted duktape [s390x] (cosmic-proposed) [2.3.0-1]
[18:00] -queuebot:#ubuntu-release- New: accepted git-sizer [amd64] (cosmic-proposed) [1.2.0+dfsg-1]
[18:00] -queuebot:#ubuntu-release- New: accepted git-sizer [s390x] (cosmic-proposed) [1.2.0+dfsg-1]
[18:00] -queuebot:#ubuntu-release- New: accepted duktape [amd64] (cosmic-proposed) [2.3.0-1]
[18:00] -queuebot:#ubuntu-release- New: accepted duktape [ppc64el] (cosmic-proposed) [2.3.0-1]
[18:00] -queuebot:#ubuntu-release- New: accepted git-sizer [ppc64el] (cosmic-proposed) [1.2.0+dfsg-1]
[18:00] -queuebot:#ubuntu-release- New: accepted duktape [armhf] (cosmic-proposed) [2.3.0-1]
[18:00] -queuebot:#ubuntu-release- New: accepted minetest-mod-lucky-block [amd64] (cosmic-proposed) [0.8-1]
[18:00] -queuebot:#ubuntu-release- New: accepted eclipse-debian-helper [amd64] (cosmic-proposed) [1.0]
[18:06] -queuebot:#ubuntu-release- New binary: rustc [s390x] (cosmic-proposed/universe) [1.28.0+dfsg1+llvm-0ubuntu1] (no packageset)
[18:56] -queuebot:#ubuntu-release- New binary: rustc [ppc64el] (cosmic-proposed/universe) [1.28.0+dfsg1+llvm-0ubuntu1] (no packageset)
[19:52] -queuebot:#ubuntu-release- New binary: equinox-bundles [amd64] (cosmic-proposed/universe) [4.7.3-1] (no packageset)
[21:16] -queuebot:#ubuntu-release- Unapproved: rejected ubuntu-drivers-common [source] (bionic-proposed) [1:0.5.2.1]
=== fossfree- is now known as fossfreedom
[22:16] -queuebot:#ubuntu-release- New binary: rustc [arm64] (cosmic-proposed/universe) [1.28.0+dfsg1+llvm-0ubuntu1] (no packageset)
[22:48] -queuebot:#ubuntu-release- New binary: rustc [armhf] (cosmic-proposed/universe) [1.28.0+dfsg1+llvm-0ubuntu1] (no packageset)
[22:50] -queuebot:#ubuntu-release- New binary: rustc [amd64] (cosmic-proposed/universe) [1.28.0+dfsg1+llvm-0ubuntu1] (no packageset)
[23:12] -queuebot:#ubuntu-release- New binary: iraf-fitsutil [amd64] (cosmic-proposed/universe) [2018.07.06-2] (no packageset)
[23:12] -queuebot:#ubuntu-release- New binary: iraf-fitsutil [ppc64el] (cosmic-proposed/universe) [2018.07.06-2] (no packageset)
[23:12] -queuebot:#ubuntu-release- New binary: iraf-fitsutil [i386] (cosmic-proposed/universe) [2018.07.06-2] (no packageset)
[23:13] -queuebot:#ubuntu-release- New binary: iraf-fitsutil [arm64] (cosmic-proposed/universe) [2018.07.06-2] (no packageset)
[23:13] -queuebot:#ubuntu-release- New binary: iraf-fitsutil [armhf] (cosmic-proposed/universe) [2018.07.06-2] (no packageset)