[00:47] -queuebot:#ubuntu-release- Unapproved: breezy (cosmic-proposed/universe) [3.0.0~bzr7111-1 => 3.0.0~bzr7119-1] (no packageset) (sync)
[00:48] -queuebot:#ubuntu-release- Unapproved: twinkle (cosmic-proposed/universe) [1:1.10.1+dfsg-3 => 1:1.10.1+dfsg-3.1] (no packageset) (sync)
[00:48] -queuebot:#ubuntu-release- Unapproved: accepted breezy [sync] (cosmic-proposed) [3.0.0~bzr7119-1]
[00:48] -queuebot:#ubuntu-release- Unapproved: accepted twinkle [sync] (cosmic-proposed) [1:1.10.1+dfsg-3.1]
[03:10] -queuebot:#ubuntu-release- Unapproved: patsy (cosmic-proposed/universe) [0.4.1+git34-ga5b54c2-1 => 0.4.1+git34-ga5b54c2-1ubuntu1] (no packageset)
[03:10] -queuebot:#ubuntu-release- Unapproved: accepted patsy [source] (cosmic-proposed) [0.4.1+git34-ga5b54c2-1ubuntu1]
[08:00] -queuebot:#ubuntu-release- Unapproved: compiz (cosmic-proposed/universe) [1:0.9.13.1+18.10.20180905-0ubuntu1 => 1:0.9.13.1+18.10.20180930-0ubuntu1] (ubuntu-mate) (sync)
[08:46] -queuebot:#ubuntu-release- Unapproved: accepted mutter [sync] (cosmic-proposed) [3.30.0-3]
[08:47] -queuebot:#ubuntu-release- Unapproved: accepted mutter [sync] (cosmic-proposed) [3.30.0-4]
[08:52] -queuebot:#ubuntu-release- Unapproved: accepted libzstd [source] (cosmic-proposed) [1.3.5+dfsg-1ubuntu1]
[08:56] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (cosmic-proposed/main) [4.18.0-1002.2] (kernel)
[08:58] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (cosmic-proposed) [4.18.0-1002.2]
[09:09] -queuebot:#ubuntu-release- Unapproved: nvidia-prime (cosmic-proposed/main) [0.8.9 => 0.8.10] (ubuntu-desktop)
[09:10] -queuebot:#ubuntu-release- Unapproved: shared-mime-info (cosmic-proposed/main) [1.9-2 => 1.10-1] (core) (sync)
[09:12] -queuebot:#ubuntu-release- Unapproved: ubuntu-drivers-common (cosmic-proposed/main) [1:0.5.4 => 1:0.5.5] (desktop-core, ubuntu-server)
[09:37] <handsome_feng> Hi, Would someone help to upload the theme and wallpapers packages? LP: #1791416 LP: #179709 Thanks in advance!
[09:38] <handsome_feng> Sorry... LP: #1794709
[09:45] <seb128> hey there, is there anything blocking that ffe to get reviewed, bug #1792356? it has been sitting there for 10 days waiting
[11:05] -queuebot:#ubuntu-release- Unapproved: cryptsetup (cosmic-proposed/main) [2:2.0.4-2ubuntu2 => 2:2.0.4-2ubuntu3] (core)
[11:07] -queuebot:#ubuntu-release- Unapproved: makedumpfile (cosmic-proposed/main) [1:1.6.4-2 => 1:1.6.4-2ubuntu1] (core)
[11:14] <xnox> cascardo, ^^^ i believe the two above together should fix huge initrds for kdumps
[11:15] <xnox> cascardo, first one, makes cryptsetup set FRAMEBUFFER conditionally, as to not override an existing value.
[11:15] <xnox> cascardo, the second one, sets FRAMEBUFFER in the settings file. everything seems to work fine for me now.
[11:15] <ahasenack> hello, good morning. Could someone look at https://code.launchpad.net/~paelzer/britney/hints-ubuntu-ocfs2-cosmic-bump/+merge/355482 for an update to ocfs2-tools hints? It doesn't work on s390x, known bug filed upstream
[11:18] -queuebot:#ubuntu-release- Unapproved: r-cran-etm (cosmic-proposed/universe) [1.0.4-2 => 1.0.4-2ubuntu1] (no packageset)
[11:19] -queuebot:#ubuntu-release- Unapproved: accepted r-cran-etm [source] (cosmic-proposed) [1.0.4-2ubuntu1]
[11:37] -queuebot:#ubuntu-release- Unapproved: network-manager-applet (cosmic-proposed/main) [1.8.18-1ubuntu1 => 1.8.18-2ubuntu1] (ubuntu-desktop)
[11:38] <GunnarHj> Hello, anybody in the release team who can look at the FFe request at bug #1791367?
[11:56] -queuebot:#ubuntu-release- Unapproved: libsdl2 (cosmic-proposed/universe) [2.0.8+dfsg1-2ubuntu1 => 2.0.8+dfsg1-4ubuntu1] (kubuntu)
[11:57] <LocutusOfBorg> can we please have libsdl2 accepted? we added a testsuite to the package ^^
[12:06] -queuebot:#ubuntu-release- Unapproved: xfce4-sensors-plugin (cosmic-proposed/universe) [1.3.0-1 => 1.3.0-2] (xubuntu) (sync)
[12:07] -queuebot:#ubuntu-release- Unapproved: shellcheck (cosmic-proposed/universe) [0.4.7-1 => 0.5.0-1] (no packageset) (sync)
[12:08] -queuebot:#ubuntu-release- Unapproved: accepted shellcheck [sync] (cosmic-proposed) [0.5.0-1]
[12:08] <LocutusOfBorg> libsdl2 will prevent breaking mir changes to migrate before libsdl being fixed
[12:08] <LocutusOfBorg> also vulkan build regressions and other things
[12:13] <ginggs> would someone please 'force-badtest pandas/0.23.3-1fakesync1ubuntu1' ? - i believe it has regressed in release http://autopkgtest.ubuntu.com/packages/p/pandas/cosmic/amd64
[12:14] -queuebot:#ubuntu-release- Unapproved: yaru-theme (cosmic-proposed/main) [18.10.4 => 18.10.5] (ubuntu-desktop)
[12:20] -queuebot:#ubuntu-release- Unapproved: peruse (cosmic-proposed/universe) [1.2+dfsg+20180923-1 => 1.2+dfsg+20181001-1] (kubuntu) (sync)
[12:23] -queuebot:#ubuntu-release- Unapproved: gocryptfs (cosmic-proposed/universe) [1.4.3-6 => 1.4.3-7] (no packageset) (sync)
[12:24] -queuebot:#ubuntu-release- Unapproved: accepted gocryptfs [sync] (cosmic-proposed) [1.4.3-7]
[12:33] -queuebot:#ubuntu-release- Unapproved: kannel (cosmic-proposed/universe) [1.4.5-0ubuntu1 => 1.4.5-0ubuntu2] (no packageset)
[12:34] -queuebot:#ubuntu-release- Unapproved: accepted kannel [source] (cosmic-proposed) [1.4.5-0ubuntu2]
[12:36] -queuebot:#ubuntu-release- Unapproved: intel-vaapi-driver-shaders (cosmic-proposed/multiverse) [2.2.0-1 => 2.2.0-2] (no packageset) (sync)
[12:36] -queuebot:#ubuntu-release- Unapproved: accepted intel-vaapi-driver-shaders [sync] (cosmic-proposed) [2.2.0-2]
[12:44] -queuebot:#ubuntu-release- Unapproved: enigmail (cosmic-proposed/universe) [2:2.0.8-1 => 2:2.0.8-2] (mozilla) (sync)
[12:46] -queuebot:#ubuntu-release- Unapproved: update-manager (cosmic-proposed/main) [1:18.10.8 => 1:18.10.9] (core)
[12:49] <cascardo> xnox: hum... I was sure I had another makedumpfile on the queue, so you replaced that one?
[12:49] -queuebot:#ubuntu-release- Unapproved: spamassassin (cosmic-proposed/main) [3.4.1-8build1 => 3.4.2-1] (ubuntu-server) (sync)
[12:49] <cascardo> ah... I was waiting for someone to sponsor it, but it wasn't sponsored
[12:52] <xnox> cascardo, probably did not....
[12:52] <xnox> cascardo, which one were you waiting on? bug #?
[12:52] <rbalint_> infinity, i now referenced the remaining bugs in update-manager's .changes
[12:58] <cascardo> xnox: LP: #1790788 and LP: #1655280
[12:58] <cascardo> but no debdiffs there, as my usual sponsors prefer some other method
[12:59] <xnox> cascardo, but where is the code? do you have a repository somwhere or something?
[13:00] <xnox> cascardo, also are any changes needed in s390-tools then as well? cause i thought we did set crashkernel paramemter default somewhere.
[13:00] <xnox> also it was expected for crashkernel= to be on the kernel cmdline, as far as i understand there is no crashkernel key in zipl.conf
[13:01] <xnox> so something is broken.
[13:04] -queuebot:#ubuntu-release- Unapproved: boxbackup (cosmic-proposed/universe) [0.13~~git20180313.g16a11e86-1 => 0.13~~git20180313.g16a11e86-1ubuntu1] (no packageset)
[13:04] -queuebot:#ubuntu-release- Unapproved: accepted boxbackup [source] (cosmic-proposed) [0.13~~git20180313.g16a11e86-1ubuntu1]
[13:04] <cascardo> the sed rule is broken
[13:04] <cascardo> let me upload the debdiff to the bug
[13:05] -queuebot:#ubuntu-release- Unapproved: kannel-sqlbox (cosmic-proposed/universe) [0.7.2-4build3 => 0.7.2-4build4] (no packageset)
[13:05] -queuebot:#ubuntu-release- Unapproved: accepted kannel-sqlbox [source] (cosmic-proposed) [0.7.2-4build4]
[13:06] <cascardo> I will test your fix before rebasing on top of it
[13:08] -queuebot:#ubuntu-release- Unapproved: gnome-shell (cosmic-proposed/main) [3.30.0-1ubuntu2 => 3.30.0-3ubuntu1] (desktop-extra, mozilla, ubuntu-desktop)
[14:04] -queuebot:#ubuntu-release- Unapproved: kdenetwork-filesharing (cosmic-proposed/universe) [4:18.04.3-0ubuntu1 => 4:18.04.3-0ubuntu2] (kubuntu)
[14:25] <ahasenack> hi, this is about the squid3 src removal (replaced by just "squid", which is at v4.x): https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1793654
[14:25] <ahasenack> seeds were updated already
[14:28] -queuebot:#ubuntu-release- Unapproved: accepted gnome-boxes [sync] (cosmic-proposed) [3.30.1-1]
[14:28] -queuebot:#ubuntu-release- Unapproved: accepted mysql-5.7 [source] (cosmic-proposed) [5.7.23-2ubuntu1]
[14:28] -queuebot:#ubuntu-release- Unapproved: accepted graphicsmagick [sync] (cosmic-proposed) [1.3.30+hg15796-1]
[14:28] -queuebot:#ubuntu-release- Unapproved: accepted colord [sync] (cosmic-release) [1.4.3-3]
[14:40] -queuebot:#ubuntu-release- Unapproved: rejected ukui-indicators [source] (cosmic-proposed) [1.1.2-0ubuntu1]
[14:41] -queuebot:#ubuntu-release- Unapproved: accepted ukui-control-center [source] (cosmic-proposed) [1.1.6-0ubuntu1]
[14:48] -queuebot:#ubuntu-release- Unapproved: ubuntu-report (cosmic-proposed/main) [1.3.0 => 1.4.0] (ubuntu-desktop)
[14:49] <Laney> rbalint_: regarding the update-manager in the queue - I think E502 is telling you that to remove the backslashes, not the brackets
[14:49] <Laney> Not sure that ignoring that one is the right thing to do
[14:51] -queuebot:#ubuntu-release- Unapproved: accepted networkd-dispatcher [source] (cosmic-proposed) [1.7-0ubuntu7]
[14:51] -queuebot:#ubuntu-release- Unapproved: accepted networkd-dispatcher [source] (cosmic-proposed) [1.7-0ubuntu8]
[14:56] <rbalint_> Laney, yes, but if i remove the backslash it complains about line break before binary operator
[14:57] -queuebot:#ubuntu-release- Unapproved: rejected protobuf [source] (cosmic-proposed) [3.0.0-9.2ubuntu1]
[14:57] <seb128> is there any release team member active recently?
[14:58] <didrocks> seb128: sil2100 acked my ubuntu-report FFe a couple of hours ago, so it sounds like yes
[14:58] <seb128> Laney, oh, thanks for picking up colord :) (just saw the bug comment, I wrote this morning on IRC but the channel doesn't seem much active)
[14:59] <seb128> I still wonder why it took 10 days+, if the triaged status contributed to have it mentaly filtered by some in a different category than if it has been New
[14:59] <seb128> didrocks, good :)
[15:01] <Laney> it's not mental filtering, it's actual filtering: I tend to look at "New" bugs most and the others a bit less often
[15:01] <Laney> rbalint_: right, there's probably another way to indent those lines
[15:01] -queuebot:#ubuntu-release- Unapproved: debian-installer (cosmic-proposed/main) [20101020ubuntu552 => 20101020ubuntu553] (core)
[15:01] <Laney> and np on the review
[15:02]  * Laney interleaves talking to different people without making it clear which line is for which person
[15:02] <Laney> keeping you on your toes
[15:02] <seb128> Laney, k, that makes sense, I note down to change back the status to "New" next time :)
[15:05] <sil2100> Not sure what's this about but yeah, for instance I only look at FFe's that are 'New' or 'Confirmed', 'Triaged' in the FFe world means 'this has been handled'
[15:07] <seb128> it was about https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1792356 which was sitting there waiting for review for 10 days
[15:07] <seb128> but was set as Triaged
[15:07] -queuebot:#ubuntu-release- Unapproved: python-apt (bionic-proposed/main) [1.6.2 => 1.6.3] (core)
[15:07] <seb128> https://wiki.ubuntu.com/FreezeExceptionProcess mentions that it needs to be "New" though, so I need to remember that for next time :)
[15:12] <Laney> rbalint_: It'd be OK to ignore W503 though I think, if that would help you (pycodestyle does that by default if I'm reading correctly)
[15:17] -queuebot:#ubuntu-release- Unapproved: accepted qemu [source] (cosmic-proposed) [1:2.12+dfsg-3ubuntu7]
[15:19] -queuebot:#ubuntu-release- Unapproved: accepted libsecret [sync] (cosmic-proposed) [0.18.6-3]
[15:21] <rbalint_> Laney, ok, let me give it a try
[15:22] <Laney> great
[15:23] -queuebot:#ubuntu-release- Unapproved: accepted ibus-pinyin [sync] (cosmic-proposed) [1.5.0-5]
[15:23] -queuebot:#ubuntu-release- Unapproved: accepted pycodestyle [sync] (cosmic-proposed) [2.4.0-2]
[15:23] -queuebot:#ubuntu-release- Unapproved: accepted pycodestyle [sync] (cosmic-proposed) [2.4.0-1]
[15:23] -queuebot:#ubuntu-release- Unapproved: ubuntu-settings (cosmic-proposed/main) [18.10.3 => 18.10.5] (ubuntu-desktop)
[15:26] -queuebot:#ubuntu-release- Unapproved: ubuntu-settings (cosmic-proposed/main) [18.10.3 => 18.10.6] (ubuntu-desktop)
[15:31] -queuebot:#ubuntu-release- Unapproved: python-apt (xenial-proposed/main) [1.1.0~beta1ubuntu0.16.04.2 => 1.1.0~beta1ubuntu0.16.04.3] (core)
[15:33] <cascardo> xnox: so, I would reject that makedumpfile change. when used on an encrypted desktop, there is no idea what's going on
[15:34] <xnox> cascardo, sorry, i'm struggling to understand you. could you please rephrase?
[15:34] <xnox> "there is no idea what's going on" -> ?!
[15:34] <cascardo> there is no display output
[15:35] <cascardo> the user has no idea what's going on, no passphrase prompt is ever gonna show up
[15:35] <xnox> that's unexpected.
[15:35] <xnox> cascardo, and that's for normal boot right? rather than the kdump boot?
[15:35] <cascardo> not really... without any framebuffer drivers on the initrd, there is no modesetting reset
[15:36] <cascardo> no, that's the kdump boot
[15:36] <cascardo> the one I care about  :-D
[15:36] <xnox> cascardo, the one you complained about.... that cryptsetup sets FRAMEBUFFER=y and thus initrd is too large.
[15:36] <xnox> cascardo, i did this change for you, as i thought that's what you want lol.
[15:36] <cascardo> no, I am complaining about you changing makedumpfile to set FRAMEBUFFER=n
[15:37] <cascardo> I don't want cryptsetup to set FRAMEBUFFER=y when the system is not encrypted
[15:37] <cascardo> which I assume is the case on ADT systems
[15:38] <xnox> sure, but then you still end up with a huge initrd
[15:38] <cascardo> on encrypted systems, yes. the correct fix would be only to include the needed gpu drivers
[15:39] <xnox> ah cause gpu drivers do not do sensible thing w.r.t. MODULES=most vs MODULES=dep ?
[15:39] <cascardo> yep... all of them are included even with MODULES=dep
[15:39] <xnox> cascardo, problem is that FRAMEBUFFER= is an option for a lot of things.... not just gpu drivers but also to include plymouth and a whole bunch of stuff.
[15:40] <cascardo> well, just reducing the number of drivers would save a lot of space
[15:40] <xnox> cascardo, so basically FRAMEBUFFER=y means "let's explode initrd size by many MBs for no reason"
[15:40] <cascardo> they take most of it, from what I could analyze
[15:41] <xnox> so plymouth framebuffer brltty console_setup keymap are all sensitive to FRAMEBUFFER=y option
[15:41] <cascardo> also because of firmware
[15:41] <xnox> plymouth is quite large, and i see no way to say "cryptsetup=y framebuffer=y plymouth=n"
[15:41] <xnox> cause i don't think people care about fancy UI for kdumps.... maybe they do
[15:41] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [amd64] (bionic-proposed) [2.02-2ubuntu8.6]
[15:41] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [arm64] (bionic-proposed) [2.02-2ubuntu8.6]
[15:44] <xnox> horum
[16:07] -queuebot:#ubuntu-release- Unapproved: shim-signed (bionic-proposed/main) [1.37~18.04.1 => 1.37~18.04.2] (core)
[16:08] -queuebot:#ubuntu-release- Unapproved: rejected shim-signed [source] (bionic-proposed) [1.37~18.04.2]
[16:28] <bluesabre> xnox, can you please accept/approve the elementary-xfce cosmic sync?
[16:28] <bluesabre> :)
[16:33] -queuebot:#ubuntu-release- Unapproved: accepted shim-signed [source] (bionic-proposed) [1.37~18.04.2]
[16:34] <infinity> bluesabre: xnox isn't in the release team.
[16:34] <bluesabre> ah
[16:35] <bluesabre> infinity: can you do it? (currently at work but wanted to get it moving while folks were still around)
[16:35] <xnox> infinity, don't worry i typically silently ignore requests like that to me... just to keep people angry at the release team ;-)
[16:35] <bluesabre> :D
[16:35] <xnox> it would be nice if one could ping !sru !archive !release teams....
[16:36] <infinity> xnox: I don't think it would help. :P
[16:36] <infinity> xnox: (I also don't want to log on to 30 previously-actioned pings)
[16:36] -queuebot:#ubuntu-release- Unapproved: accepted elementary-xfce [sync] (cosmic-proposed) [0.13.1-1]
[16:36] <xnox> infinity, of course it won't, but at least the new excuse will be "but you didn't use the right bot ping command"
[16:36] <bluesabre> infinity: much appreciated!
[16:37] <xnox> infinity, but many people have no idea who are archive/release/sru team members....
[16:37] <xnox> or the difference between the three....
[16:37] <bluesabre> xnox: sorry for the noise, but thanks for being a good highlight :)
[16:38] <xnox> bluesabre, mostly because infinity highlights on xnox just to monitor the batshit crazy things i do ;-)
[16:38] <bluesabre> (thank goodness)
[16:38] <infinity> Hahaha.  I don't, but that sounds like a solid plan going forward.
[16:38] -queuebot:#ubuntu-release- Unapproved: accepted debian-installer [source] (cosmic-proposed) [20101020ubuntu553]
[16:38] <infinity> Have to keep the Russian trolls in check.
[16:39] -queuebot:#ubuntu-release- Unapproved: rejected update-manager [source] (cosmic-proposed) [1:18.10.9]
[16:39] <xnox> infinity, i highlight on "s390x" and it's interesting when like "juju" "maas" "openstack" "snapd" "snapcraft" channel lit up. Also i bet with all these words, i'll trigger a few people right now too =)))) muahahhahaha
[16:39] <infinity> xnox: Several of those words trigger me, yes. :P
[16:40] <xnox> infinity, can you reject cryptsetup and makedumpfile from cosmic unappoved queue for now?
[16:40] -queuebot:#ubuntu-release- Unapproved: update-manager (cosmic-proposed/main) [1:18.10.8 => 1:18.10.9] (core)
[16:40] <xnox> infinity, i think there is no consensus yet, if that's what in fact we want to do.
[16:41] <xnox> so better have it rejected, for now, and resurrect later if the bikeshed goes that way.
[16:48] -queuebot:#ubuntu-release- Unapproved: accepted apturl [source] (bionic-proposed) [0.5.2ubuntu14.2]
[16:50] -queuebot:#ubuntu-release- Unapproved: rejected cryptsetup [source] (cosmic-proposed) [2:2.0.4-2ubuntu3]
[16:50] -queuebot:#ubuntu-release- Unapproved: rejected makedumpfile [source] (cosmic-proposed) [1:1.6.4-2ubuntu1]
[16:50] -queuebot:#ubuntu-release- Unapproved: heat (bionic-proposed/main) [1:10.0.1-0ubuntu2 => 1:10.0.2-0ubuntu1] (openstack, ubuntu-server)
[16:51] <xnox> tah
[16:55] -queuebot:#ubuntu-release- Unapproved: accepted gnome-shell [source] (cosmic-proposed) [3.30.0-3ubuntu1]
[16:55] -queuebot:#ubuntu-release- Unapproved: accepted network-manager-applet [source] (cosmic-proposed) [1.8.18-2ubuntu1]
[16:55] -queuebot:#ubuntu-release- Unapproved: accepted kdenetwork-filesharing [source] (cosmic-proposed) [4:18.04.3-0ubuntu2]
[16:55] -queuebot:#ubuntu-release- Unapproved: accepted yaru-theme [source] (cosmic-proposed) [18.10.5]
[16:57] <infinity> jdstrand: Why did your evince apparmor profile overhaul delete the Author lines?
[16:57] <infinity> jdstrand: You consider it enough of a rewrite that Kees's bits are gone?
[16:58] <jdstrand> infinity: more that the profile has had many authors and kees and I shouldn't get direct bug reports
[16:58] <infinity> Well, kees wouldn't, cause that email is dead. ;)
[16:59] <jdstrand> I mean, I can add them back, but we've gotten away from that typically, so I just removed them
[16:59] <infinity> jdstrand: I don't like seeing attribution removed, generally.  But if kees is party to this and also doesn't care, then yay.
[17:00] <infinity> (not like any future employer will be judging him based on his portfolio of evince apparmor profiles)
[17:03] <infinity> xnox: Why are all these openssl rebuilds necessary?  Feature detection at build time?
[17:03] <infinity> xnox: And, if so, did you investigate which packages actually need that, or is this just a napalm rebuild of all rdeps "just in case"?
[17:03] <jdstrand> well, I didn't consult with kees. I guess I can real quick
[17:04] <jdstrand> kees: do you mind that I dropped our names from the evince profile? if so, I can add it back
[17:04] <infinity> jdstrand: That'd be the polite thing to do (I mean, unless there's an AUTHORS file elsewhere that consolidates, and you're just removing redundant headers, but I imagine that's not the case here)
[17:04] <jdstrand> it isn't
[17:06] -queuebot:#ubuntu-release- Unapproved: accepted gnome-pkg-tools [source] (cosmic-proposed) [0.20.2ubuntu3]
[17:09] <kees> jdstrand, infinity: I'm totally fine with that removal. :)
[17:09] <infinity> kees: Shiny.
[17:09] <infinity> Now if only I knew someone who was competent enough to review this diff.
[17:09]  * infinity stares at kees.
[17:09] -queuebot:#ubuntu-release- Unapproved: rejected nvidia-prime [source] (cosmic-proposed) [0.8.10]
[17:11] <kees> infinity: where can I find it?
[17:12] <infinity> kees: http://launchpadlibrarian.net/390908576/evince_3.30.0-3_3.30.0-3ubuntu1.diff.gz
[17:12] -queuebot:#ubuntu-release- Unapproved: accepted apt [source] (bionic-proposed) [1.6.5]
[17:13] <xnox> infinity, based on grep for libssl1.1 (>= 1.1.1) from ppa:xnox/ubuntu/openssl -> rebuilding these makes them dep on 1.1.1 rather than 1.1.0
[17:13] <xnox> infinity, so they use something from 1.1.1 symbols....
[17:14] <infinity> xnox: That alone isn't a reason to rebuild.
[17:14] <infinity> xnox: By that logic, we'd rebuild ~50% of libc's rdeps every cycle.
[17:14] <cjwatson> When I don't want somebody to get support email but want to keep their attribution, I generally compromise by keeping their name but removing their email address.
[17:14] <xnox> infinity, and eg. curl without rebuild cannot do --tlsv1.3 the flag is there but it claims that "openssl is built without tls 1.3 support"
[17:15] <xnox> infinity, with rebuild it starts to be able to do tlsv1.3 downloads
[17:15] <xnox> and --tlsv1.3 flag becomes operational.
[17:15] <jdstrand> kees: thanks!
[17:15] <infinity> xnox: Right, so that's a solid argument for cURL.  My question was how you arrived at the conclusion that everything needed that. :)
[17:15] <kees> infinity: looks good to me. much more restrictive. nice! :)
[17:16] <infinity> Having a hard time picturing you saying that in anything but leather.
[17:17] <xnox> infinity, the rest is based on the symbols dep. meaning they use symbols needed to e.g. renew keys in tls 1.3 and the like.
[17:17] <infinity> jdstrand: Is there any prior art for dynamically creating some of these nastier profile bits?  My only concern is stuff like the "supported archivers" section, where if upstream adds another, the profile will be busted.
[17:18] <xnox> infinity, this is consisent with how 1.2 was enabled. and e.g. apache2 was shipped for a long time non-rebuilt, and thus didn't do tls1.2......
[17:18] <infinity> jdstrand: Ditto on supported file formats.
[17:18] <jdstrand> infinity: no. note that what I added there came from the existing evince abstractions
[17:18] <jdstrand> abstraction*
[17:18] <xnox> (note apache2 is not rebuilt, cause mod_ssl only does tls1.3 in trunk; and not in the archive)
[17:18] <jdstrand> which was too lenient
[17:19] <jdstrand> I mean, I could've blacklisted or I could take what I wanted from there
[17:19] <jdstrand> I went with the latter since the former was a bit of what got us in trouble
[17:20] <infinity> jdstrand: Yeah, I'm not implying any of this is wrong, just that it would be nice to be able to tie into the build system (even with some nasty rgreppry and seddery) to try to determine at build time *what* archivers and formats we should whitelist.
[17:20] <jdstrand> and for the file rules, I only really modified the thumbnailer. evince and previewer are still using the evince abstraction
[17:20] <infinity> jdstrand: But also not saying that should block this upload.  Just suggesting it might bite you next year.
[17:20] <jdstrand> infinity: that would indeed be nice
[17:21] <jdstrand> there was in ancient days work to statically analyze binaries to suggest profiles
[17:21] <jdstrand> but that hasn't really been a thing for a long time
[17:22] <xnox> infinity, my primary concern was for post-release SRU or Security uploads to these packages to not cause a radically new behavior due to them starting to utilize tlsv1.3 / openssl 1.1.1 apis.
[17:24] <infinity> xnox: Mmkay.  I'm 75% convinced.
[17:25] <infinity> xnox: My take would be "if it's a new version of an existing symbol, meh, but if it's a new symbol entirely, rebuilding probably picked up new functionality", but given the mess that is OpenSSL, I'm not sure I'd count on being able to make that call reliably.,
[17:26] <infinity> So, churn on, I guess.
[17:27] -queuebot:#ubuntu-release- Unapproved: accepted evince [source] (cosmic-proposed) [3.30.0-3ubuntu1]
[17:28] -queuebot:#ubuntu-release- Unapproved: accepted ldns [source] (cosmic-proposed) [1.7.0-3ubuntu7]
[17:28] -queuebot:#ubuntu-release- Unapproved: accepted python-cryptography [source] (cosmic-proposed) [2.3-1build1]
[17:28] -queuebot:#ubuntu-release- Unapproved: accepted nghttp2 [source] (cosmic-proposed) [1.32.1-1build1]
[17:28] -queuebot:#ubuntu-release- Unapproved: accepted unbound [source] (cosmic-proposed) [1.7.3-1build1]
[17:28] -queuebot:#ubuntu-release- Unapproved: accepted curl [source] (cosmic-proposed) [7.61.0-1ubuntu2]
[17:28] -queuebot:#ubuntu-release- Unapproved: accepted erlang [source] (cosmic-proposed) [1:20.3.8.5+dfsg-1build1]
[17:28] -queuebot:#ubuntu-release- Unapproved: accepted dovecot [source] (cosmic-proposed) [1:2.3.2.1-1ubuntu3]
[17:28] -queuebot:#ubuntu-release- Unapproved: accepted haproxy [source] (cosmic-proposed) [1.8.13-2build1]
[17:29] -queuebot:#ubuntu-release- Unapproved: accepted bind9 [source] (cosmic-proposed) [1:9.11.4+dfsg-3ubuntu5]
[17:29] -queuebot:#ubuntu-release- Unapproved: accepted libnet-dns-sec-perl [source] (cosmic-proposed) [1.09-1build1]
[17:30] <xnox> infinity, it's a shame w.r.t. libssl and libcrypto shipped together. most of libcrypto new symbols are that "new editions of the same thing" at least to me; and the libssl ones are all "new functionality looking" -> ie. calls and stuff to do things with the new tls v1.3 handshake / session. =/
[17:30] -queuebot:#ubuntu-release- Unapproved: accepted vlc [source] (cosmic-proposed) [3.0.4-2build1]
[17:30] <xnox> cause one cannot do old v1.2 callbacks and things for v1.3 session key updates and the like. Hence nodejs appears to struggle to support tls v1.3 -> all of their tests fail.
[17:31] <xnox> most likely nodejs 11 will ship with using 1.1.x abi, and set upper limit to v1.2.
[17:31] <xnox> until they rewrite all of their code to be v1.3 compatible isntead of relying on debug/tracing apis.
[17:31] -queuebot:#ubuntu-release- Unapproved: rejected calibre [sync] (cosmic-proposed) [3.32.0+dfsg-1]
[17:31] -queuebot:#ubuntu-release- Unapproved: rejected krita [sync] (cosmic-proposed) [1:4.1.3+dfsg-1]
[17:32] <infinity> xnox: nodejs is a tire fire, that's not news.
[17:32] -queuebot:#ubuntu-release- Unapproved: rejected update-manager [source] (cosmic-proposed) [1:18.10.9]
[17:36] -queuebot:#ubuntu-release- Unapproved: accepted vala-panel-appmenu [sync] (cosmic-proposed) [0.7.1+dfsg1-1]
[17:36] -queuebot:#ubuntu-release- Unapproved: accepted vala-panel [sync] (cosmic-proposed) [0.4.63+dfsg1-1]
[17:37] -queuebot:#ubuntu-release- Unapproved: accepted gnome-maps [sync] (cosmic-proposed) [3.30.1-1]
[17:37] -queuebot:#ubuntu-release- Unapproved: accepted krita [sync] (cosmic-proposed) [1:4.1.3+dfsg-1]
[17:38] -queuebot:#ubuntu-release- Unapproved: accepted catfish [sync] (cosmic-proposed) [1.4.6-1]
[17:38] -queuebot:#ubuntu-release- Unapproved: accepted entangle [sync] (cosmic-proposed) [1.0-1]
[17:41] -queuebot:#ubuntu-release- Unapproved: accepted cloud-initramfs-tools [source] (bionic-proposed) [0.40ubuntu1.1]
[17:42] -queuebot:#ubuntu-release- Unapproved: accepted cloud-initramfs-tools [source] (xenial-proposed) [0.27ubuntu1.6]
[17:48] -queuebot:#ubuntu-release- Unapproved: plymouth (cosmic-proposed/main) [0.9.3-1ubuntu8 => 0.9.3-1ubuntu9] (core)
[17:52] -queuebot:#ubuntu-release- Unapproved: accepted python-apt [source] (bionic-proposed) [1.6.3]
[18:11] -queuebot:#ubuntu-release- Unapproved: keystone (bionic-proposed/main) [2:13.0.0-0ubuntu1 => 2:13.0.1-0ubuntu1] (openstack, ubuntu-server)
[18:13] -queuebot:#ubuntu-release- Unapproved: strongswan (cosmic-proposed/main) [5.6.3-1ubuntu2 => 5.6.3-1ubuntu3] (ubuntu-server)
[18:22] <cyphermox> could someone please badtest ubuntu-image autopkgtests for grub2; the issue comes from the new pycodestyle check for escape sequences, not a bug in grub or ubuntu-image.
[18:22] <cyphermox> qa runtests: commands[0] | python -m flake8 ubuntu_image
[18:22] <cyphermox> ubuntu_image/helpers.py:68:7: W605 invalid escape sequence '\d'
[18:23] <cyphermox> (it would unblock grub2)
[18:29] <tjaalton> and please check the new queue and review spirv-tools & vulkan-*
[18:30] <infinity> cyphermox: Done.
[18:30] <infinity> sil2100: Please fix ubuntu-image's W605 errors (see ubiquity trunk for prior art)
[18:33] <vorlon> cyphermox: why/when did pycodestyle sneak in?  indirect test dep?
[18:33] <teward> cyphermox: this'll sound like a stupid question, but why not alter the autopkgtests to set up Flake8 to *not* trigger on W605?
[18:34] <infinity> teward: Err, you mean the autopkgtest infra, or the ubuntu-image tests?
[18:34] <infinity> The former certainly isn't going to happen.
[18:34] <infinity> The latter could be done, sure.
[18:35] <infinity> But if one's fixing ubuntu-image to not fail, they could fix the bug too. :P
[18:35] <teward> infinity: the ubuntu-image tests
[18:35] <teward> i was imprecise, my apologies
[18:35] -queuebot:#ubuntu-release- Unapproved: accepted apt [source] (xenial-proposed) [1.2.28]
[18:35] <teward> infinity: It might mean the autopkgtests have to generate a tox.ini unless one ships with ubuntu-image but you would be able to block the W605 triggers, or other stylistic warnings you don't want to trigger on
[18:35] <teward> not the *nicest* if you want to be fully PEP8 compliant but
[18:36] <teward> (and you're right, they could fix the bug too if they're fixing it to not fail)
[18:36] <infinity> teward: Yeah, I'm not sure the point of this bikeshed.
[18:36] <infinity> teward: I imagine everyone who uses pycodestyle knows how to ask it to ignore things.  But ignoring things isn't always the best option.
[18:36] <infinity> (In this case, it's not, IMO)
[18:39] <infinity> vorlon: You can blame mwhudson for the new pycodestyle.  As for the "sneaking in", that might be britney's fault for not recursing.  Most tests probably depend on pep8 still.
[18:40] <teward> infinity: i... may have a fix that's a single-character change for Cosmic, let me do some tests...
[18:40] <infinity> (The lack of recursion was a heated point of contention between pitti and I, his argument being that recursion would cripple the infra without getting us much more useful testing, while I argued that things like the above happen)
[18:40] <infinity> teward: Yes, it's a single-char fix. :P
[18:40] <infinity> teward: I was asking sil2100 to fix it because he's upstream, not because I couldn't.
[18:41] <teward> ack
[18:41] <teward> :)
[18:42] <sil2100> infinity: o/
[18:43] -queuebot:#ubuntu-release- Unapproved: accepted python-apt [source] (xenial-proposed) [1.1.0~beta1ubuntu0.16.04.3]
[18:43] <sil2100> bleh
[18:43] <sil2100> (on it)
[18:43] -queuebot:#ubuntu-release- Unapproved: gnome-shell-extension-workspaces-to-dock (cosmic-proposed/universe) [48-2 => 49-1] (no packageset) (sync)
[18:44] -queuebot:#ubuntu-release- Unapproved: accepted gnome-shell-extension-workspaces-to-dock [sync] (cosmic-proposed) [49-1]
[18:44] -queuebot:#ubuntu-release- Unapproved: uwsgi (cosmic-proposed/universe) [2.0.17.1-6 => 2.0.17.1-7] (no packageset) (sync)
[18:45] -queuebot:#ubuntu-release- Unapproved: accepted uwsgi [sync] (cosmic-proposed) [2.0.17.1-7]
[18:45] <infinity> vorlon: Ultimately, I think pitti's probably right about the recursion issue (if britney recursed fully to determine test rdeps, glibc would trigger literally every test in the archive, and perl would be close), but OTOH, I have no good answer for problems like the above, where a commonly-depended-on package becomes a transitional and suddenly a useless test trigger.
[18:46] -queuebot:#ubuntu-release- Unapproved: firejail (cosmic-proposed/universe) [0.9.54-1 => 0.9.56-1] (no packageset) (sync)
[18:47] -queuebot:#ubuntu-release- Unapproved: accepted firejail [sync] (cosmic-proposed) [0.9.56-1]
[18:47] <cyphermox> vorlon: IIRC it was uploaded as https://launchpad.net/ubuntu/+source/pycodestyle/2.4.0-0ubuntu1 around 09/20
[18:48] <cyphermox> vorlon: infinity and I investigated that coming up first when we last uploaded ubiquity
[18:48] <vorlon> cyphermox: ok
[18:49] <cyphermox> in this case it's definitely a one-char fix :)
[19:01] -queuebot:#ubuntu-release- Unapproved: linux-kvm (cosmic-proposed/main) [4.18.0-1001.1 => 4.18.0-1002.2] (kernel) (sync)
[19:01] -queuebot:#ubuntu-release- Unapproved: linux-meta-kvm (cosmic-proposed/main) [4.18.0.1001.1 => 4.18.0.1002.2] (kernel) (sync)
[19:14] -queuebot:#ubuntu-release- Unapproved: ubuntu-image (cosmic-proposed/main) [1.4+18.10ubuntu2 => 1.4+18.10ubuntu3] (desktop-core)
[19:16] -queuebot:#ubuntu-release- Unapproved: accepted linux-kvm [sync] (cosmic-proposed) [4.18.0-1002.2]
[19:16] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta-kvm [sync] (cosmic-proposed) [4.18.0.1002.2]
[19:17] -queuebot:#ubuntu-release- Unapproved: accepted plymouth [source] (cosmic-proposed) [0.9.3-1ubuntu9]
[19:17] -queuebot:#ubuntu-release- Unapproved: accepted strongswan [source] (cosmic-proposed) [5.6.3-1ubuntu3]
[19:18] -queuebot:#ubuntu-release- Unapproved: accepted nautilus [source] (cosmic-proposed) [1:3.26.4-0ubuntu5]
[19:20] -queuebot:#ubuntu-release- Unapproved: accepted libsdl2 [source] (cosmic-proposed) [2.0.8+dfsg1-4ubuntu1]
[19:22] <sil2100> ubuntu-image in the queue ^
[19:22] <sil2100> Anyway, I go EOD now
[19:27] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-image [source] (cosmic-proposed) [1.4+18.10ubuntu3]
[19:33] -queuebot:#ubuntu-release- Unapproved: rejected ubuntu-settings [source] (cosmic-proposed) [18.10.5]
[19:36] -queuebot:#ubuntu-release- Unapproved: accepted mate-tweak [source] (cosmic-proposed) [18.10.1-0ubuntu1]
[21:24] -queuebot:#ubuntu-release- Unapproved: breeze (cosmic-proposed/universe) [4:5.13.5-0ubuntu1 => 4:5.13.5-0ubuntu2] (kubuntu)
[21:34] -queuebot:#ubuntu-release- Unapproved: firefox (cosmic-proposed/main) [62.0+build2-0ubuntu1 => 62.0.3+build1-0ubuntu1] (kubuntu, mozilla, ubuntu-desktop)
[22:19] <jbicha> we don't do anything with autopkgtest "Restrictions: flaky" yet, right?
[22:23] <vorlon> jbicha: correct
[23:53] -queuebot:#ubuntu-release- New sync: appmenu-registrar (cosmic-proposed/primary) [0.7.1-1]