[07:39] <apw> ^ /me will look at those once we have the launchpad support in place
[08:18] <cjwatson> apw: which is already, right?
[08:18] <cjwatson> apw: I deployed your SIPL code yesterday
[08:18] <apw> cjwatson, i was under the impression the key was not yet in place; perhaps i missed that
[08:20] <cjwatson> apw: I installed that the day before yesterday :)
[08:21] <apw> cjwatson, ahh i stand corrected, will look at it next :)
[08:58] -queuebot:#ubuntu-release- Unapproved: accepted curtin [source] (disco-proposed) [19.1-7-g37a7a0f4-0ubuntu1~19.04.1]
[09:08] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (disco-proposed) [1:20190611.1-0ubuntu0.19.04.1]
[09:08] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (bionic-proposed) [1:20190611.1-0ubuntu0.18.04.1]
[09:08] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (cosmic-proposed) [1:20190611.1-0ubuntu0.18.10.1]
[09:09] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (xenial-proposed) [1:20190611.1-0ubuntu0.16.04.1]
[09:37] -queuebot:#ubuntu-release- Unapproved: accepted s390-tools [s390x] (eoan-proposed) [2.9.0-0ubuntu2]
[10:13] -queuebot:#ubuntu-release- New: rejected s390-tools-signed [source] (eoan-proposed) [2.9.0-0ubuntu2]
[10:25] -queuebot:#ubuntu-release- New source: s390-tools-signed (eoan-proposed/primary) [2.9.0-0ubuntu2]
[10:38] -queuebot:#ubuntu-release- New: rejected s390-tools-signed [source] (eoan-proposed) [2.9.0-0ubuntu2]
[10:40] -queuebot:#ubuntu-release- New source: s390-tools-signed (eoan-proposed/primary) [2.9.0-0ubuntu2]
[10:45] -queuebot:#ubuntu-release- New: accepted s390-tools-signed [source] (eoan-proposed) [2.9.0-0ubuntu2]
[10:46] -queuebot:#ubuntu-release- New binary: s390-tools-signed [s390x] (eoan-proposed/none) [2.9.0-0ubuntu2] (no packageset)
[10:50] -queuebot:#ubuntu-release- New: accepted s390-tools-signed [s390x] (eoan-proposed) [2.9.0-0ubuntu2]
[12:26] -queuebot:#ubuntu-release- Unapproved: openssl (disco-proposed/main) [1.1.1b-1ubuntu2.2 => 1.1.1b-1ubuntu2.3] (core)
[12:49] -queuebot:#ubuntu-release- Unapproved: openssl (cosmic-proposed/main) [1.1.1-1ubuntu2.3 => 1.1.1-1ubuntu2.4] (core)
[12:52] -queuebot:#ubuntu-release- Unapproved: openssl (bionic-proposed/main) [1.1.1-1ubuntu2.1~18.04.2 => 1.1.1-1ubuntu2.1~18.04.3] (core)
[12:53] <xnox> apw:  can you please reject all three of openssl above ^ ? they shouldn't be direct uploads, but should be built in -security only silo, and copied in.
[13:32] -queuebot:#ubuntu-release- Unapproved: rejected openssl [source] (disco-proposed) [1.1.1b-1ubuntu2.3]
[13:32] -queuebot:#ubuntu-release- Unapproved: rejected openssl [source] (cosmic-proposed) [1.1.1-1ubuntu2.4]
[13:33] -queuebot:#ubuntu-release- Unapproved: rejected openssl [source] (bionic-proposed) [1.1.1-1ubuntu2.1~18.04.3]
[13:33] <xnox> tah
[14:54] -queuebot:#ubuntu-release- Unapproved: openssl (bionic-proposed/main) [1.1.1-1ubuntu2.1~18.04.2 => 1.1.1-1ubuntu2.1~18.04.3] (core) (sync)
[14:54] -queuebot:#ubuntu-release- Unapproved: openssl (cosmic-proposed/main) [1.1.1-1ubuntu2.3 => 1.1.1-1ubuntu2.4] (core) (sync)
[14:54] -queuebot:#ubuntu-release- Unapproved: openssl (disco-proposed/main) [1.1.1b-1ubuntu2.2 => 1.1.1b-1ubuntu2.3] (core) (sync)
[14:58] <tjaalton> bdmurray: i'll discuss the KEY_RFKILL bug with seb next week,when he's back
[16:38] <xnox> vorlon:  fresh set of openssl sru syncs for you to review =) please =)
[17:07] <vorlon> xnox: for disco it seems only the fixes for the restart handling are included, not the other fixes; are those still in progress?
[17:07] <xnox> vorlon:  what other fixes?
[17:08] <vorlon> xnox: the other openssl 1.1.1-induced regressions that were being discussed yesterday and whose bug numbers I would have to hunt down
[17:09] <xnox> regression in 1.1.1 and 1.1.1a; fixed upstream in 1.1.1b and up
[17:09] <vorlon> ok
[17:09] <xnox> bug #1832659
[17:09] <vorlon> and LP: #1832370 is still incomplete
[17:09] <vorlon> (w/ follow-up from submitter suggesting it should be closed invalid)
[17:09] <xnox> vorlon:  re-inability to cap to tlsv1.2 and/or reorder ciphersuites is incomplete/invalid. I managed to tweak my openssl.cnf to both cap, or reorder ciphersuites.
[17:10] <vorlon> ack
[17:10] <xnox> ah
[17:10] <xnox> vorlon:  closed as invalid
[17:11] <vorlon> xnox: why does the disco SRU bump the minimum version for restarting to 1.1.1-1ubuntu2.1~18.04.2, which is ultimately an arbitrary point in the bionic SRU history?
[17:11] <vorlon> is it because that's the first version that triggers the service restart correctly on bionic?
[17:11] <xnox> vorlon:  we need to restart anybody who is coming from 1.1.0 or the 1.1.1 version that didn't restart people.
[17:12] <xnox> vorlon:  yes.
[17:12]  * xnox needs to not forget to bump that, when going to v3.0.0 somehow
[17:12] <vorlon> 1.1.1-1ubuntu2.1 in cosmic is a higher version number.  did that have the restart correct?
[17:12] <xnox> no, bu cosmic shipped with 1.1.1 to begin with in release pocket.
[17:13] <xnox> this is for upgrades from bionic-release => any of these releases really.
[17:13] <xnox> and/or lts -> lts
[17:13] <vorlon> ok
[17:13] <xnox> i.e. for people who installed cosmic/bionic/eoan this is a no-op, and will not fire.
[17:13] <xnox> cosmetic.
[17:14] <xnox> but also all postinsts are the same now =)
[17:14] <vorlon> hmm, alright
[17:14] <vorlon> I'll accept the consistency argument
[17:14] <vorlon> otherwise I would've been inclined to say that the minimum version should've been set at 1.1.1 instead of 1.1.1-1ubuntu2.1~18.04.2,
[17:15] <xnox> debian didn't bump it, cause they are going from libssl1.0.2 => libssl1.1 where 1.1 is 1.1.1
[17:15] <xnox> but probably should report it there too....
[17:16] <vorlon> because "I installed bionic and upgraded to an old 1.1.1 and my services were broken but I never restarted them and I didn't apply any later updates but I dist-upgraded to disco" <-- uh ok
[17:17]  * xnox would find it weird how come version check is different on bionic vs other releases, and how to calculate it right.... and for all practical reasons 1.1.1-1ubuntu2.1~18.04.2 is equivalent to 1.1.1, on post-bionic releases.
[17:20] <vorlon> well, I find having that particular version string in the postinst confusing to read / reason about, see also the preceding discussion, and a 1.1.1 would I think be clearer to people later
[17:20] <vorlon> but as I said, I'm ok with the consistency argument
[17:21] <xnox> ack
[17:22] <vorlon> xnox: LP: #1832421> this observation is not for SRU, but I think given systemd we should be doing much better than this in the future as it is now possible to not only get a complete list of processes on the system that have an out-of-date library loaded in memory, but also to map them to systemd units and figure out which require what kind of notification to the user
[17:24] <xnox> interesting
[17:25] <xnox> vorlon:  but e.g. Xorg is just a usersession process in the user scope, not a unit by itself.
[17:25] <xnox> checking libary loaded mappings and mapping it to unit names will be fun.
[17:25] <vorlon> xnox: yes, but my point is that before we set any flags at all saying "reboot required", we should actually inspect what units have the old library loaded, which currently we do not
[17:26] <vorlon> currently we unconditionally set that flag on servers on upgrade
[17:27] <xnox> we need a card for this
[17:30] -queuebot:#ubuntu-release- Unapproved: accepted openssl [sync] (disco-proposed) [1.1.1b-1ubuntu2.3]
[17:34] -queuebot:#ubuntu-release- Unapproved: accepted openssl [sync] (cosmic-proposed) [1.1.1-1ubuntu2.4]
[17:40] <vorlon> xnox: hmm openssl 1.1.1-1ubuntu2.1~18.04.3 wrongly lists LP: #1832522 a second time
[17:41] <vorlon> xnox: can you fix that quickly, please?  I don't want wrong user-visible changelogs in an SRU, or for this bug to be entangled in the SRU tracking
[17:43] <xnox> looking
[17:44] <xnox> yeah that's buggy
[17:45] <xnox> vorlon:  reject it please
[17:46] -queuebot:#ubuntu-release- Unapproved: rejected openssl [sync] (bionic-proposed) [1.1.1-1ubuntu2.1~18.04.3]
[17:49] <vorlon> eoan/armhf autopkgtest queue cut by a third by --all-proposed'ing the kde autopkgtests
[17:52] <xnox> ah, maybe we should always do that, when all of that goo lands
[17:56] <vorlon> xnox: automation welcome
[17:59] <vorlon> currently it looks like for queue in debci-huge-eoan-armhf debci-eoan-armhf; do ./autopkgtest-cloud/tools/filter-amqp $amqp_url $queue
[17:59] <vorlon> '\b(ktextwidgets|kio|kxmlgui|kcompletion|kconfigwidgets|kiconthemes|kcrash|kservice|kwidgetsaddons|ki18n|kwindowsystem|kcoreaddons|kirigami2|kpeople|kwallet-kf5|kbookmarks|knotifyconfig|kinit|knewstuff|baloo-kf5|kdeclarative|kparts|kactivities-kf5|kross|kded|kdewebkit|kcmutils|khtml|frameworkintegration|kmediaplayer|ktexteditor|kactivities-stats|kdelibs4support|plasma-framework|krunner)\b'; done;
[17:59] <vorlon> retry-autopkgtest-regressions --state RUNNING --all-proposed | grep -E '[...]'
[18:01] <vorlon> anyway, total queue size down now by closer to 50%, and the reshuffle actually means the kde tests are at the back of the queue again, so we ought to see chings making progress
[18:03] <xnox> vorlon:  re deleted maps.... we really ought to do that at the end of every upgrade really.
[18:04] <xnox> at least least things, offer to restart them, and/or raise reboot flags. Or at least like login/logout notifications.
[18:04] <xnox> i think i need to reboot my laptop now, so many deleted maps.....
[18:15] <vorlon> xnox: there's a spectrum here.  Some libs we know break after major upgrades because of plugin libraries and warrant prompting about affected services (libc, pam, openssl); security updates should be in your face (and that should probably be handled by debian/rules glue to notice CVEs in changelogs and bail about maintainer scripts not being updated, or by actually auto-generating the min versions
[18:15] <vorlon> based on changelog); some updates are just inconvenient overhead on the fs if you don't restart
[18:39] -queuebot:#ubuntu-release- Unapproved: openssl (bionic-proposed/main) [1.1.1-1ubuntu2.1~18.04.2 => 1.1.1-1ubuntu2.1~18.04.3] (core) (sync)
[18:39] <xnox> vorlon:  updated ^
[19:22] <vorlon> xnox: accepted, thanks
[19:22] <xnox> yeah
[19:22] -queuebot:#ubuntu-release- Unapproved: accepted openssl [sync] (bionic-proposed) [1.1.1-1ubuntu2.1~18.04.3]
[19:50] <vorlon> who's triggering langpack updates these days?  language-pack-gnome-fi-base seems to have gotten missed for upload
[19:52] <vorlon> coreycb: hi, have you seen the regressed autopkgtests on python-oslo.*?
[19:56] <coreycb> vorlon: I'm off today but that might be fixed with the latest upload
[20:12] <vorlon> coreycb: hmm latest upload of what?
[21:07] <vorlon> librust-curl+force-system-lib-on-osx-dev | 0.4.22-1      | new        | amd64
[21:07] <vorlon> sure, that's a perfectly reasonable justification for having a rust-cargo uploaded with its build-dependencies unsatisfiable in the Debian archive
[22:00] -queuebot:#ubuntu-release- Unapproved: rejected gnupg [source] (xenial-proposed) [1.4.20-1ubuntu3.4]
[22:10] -queuebot:#ubuntu-release- Unapproved: accepted gnome-control-center [source] (xenial-proposed) [1:3.18.2-1ubuntu6.1]
[22:23] -queuebot:#ubuntu-release- Unapproved: accepted gnome-control-center [source] (bionic-proposed) [1:3.28.2-0ubuntu0.18.04.5]