[08:40] -queuebot:#ubuntu-release- Unapproved: accepted nova [source] (bionic-proposed) [2:17.0.5-0ubuntu2]
[08:41] -queuebot:#ubuntu-release- Unapproved: accepted nova [source] (xenial-proposed) [2:13.1.4-0ubuntu4.3]
[08:44] -queuebot:#ubuntu-release- Unapproved: accepted syslog-ng-incubator [source] (xenial-proposed) [0.3.3-2ubuntu1]
[09:07] <Trevinho> sil2100: hey, could you instead have a look on those SRUs from LP I've mentioned last friday?
[09:08] <Trevinho> from LP => from bileto
[09:52] <apw> Trevinho, if they have a bionic component then it is hard to get things out if they are main because of the point release freez
[10:01] <Trevinho> apw: uff... They were waiting for weeks, and they have to be in .1 or some installs will break...
[10:02] <apw> infinity, ^
[10:02] <Trevinho> I had to ping again maybe, but I asked already few times
[10:04] <apw> and it is helpful if you could point at the silo and/or the packages
[10:09] <Trevinho> Nux and xorg
[10:54] -queuebot:#ubuntu-release- Unapproved: openvswitch (bionic-proposed/main) [2.9.0-0ubuntu1 => 2.9.2-0ubuntu0.18.04.1] (ubuntu-server)
[11:14] -queuebot:#ubuntu-release- New binary: intel-mkl [s390x] (cosmic-proposed/multiverse) [2018.3.222-1] (no packageset)
[11:15] -queuebot:#ubuntu-release- New binary: intel-mkl [ppc64el] (cosmic-proposed/multiverse) [2018.3.222-1] (no packageset)
[11:17] -queuebot:#ubuntu-release- New binary: python-certbot-dns-gehirn [amd64] (cosmic-proposed/universe) [0.26.1-1] (no packageset)
[11:17] -queuebot:#ubuntu-release- New binary: python-certbot-dns-sakuracloud [amd64] (cosmic-proposed/universe) [0.26.1-1] (no packageset)
[11:17] -queuebot:#ubuntu-release- New binary: python-certbot-dns-linode [amd64] (cosmic-proposed/universe) [0.26.0-1] (no packageset)
[11:23] -queuebot:#ubuntu-release- New: accepted python-certbot-dns-gehirn [amd64] (cosmic-proposed) [0.26.1-1]
[11:23] -queuebot:#ubuntu-release- New: accepted python-certbot-dns-sakuracloud [amd64] (cosmic-proposed) [0.26.1-1]
[11:23] -queuebot:#ubuntu-release- New: accepted python-certbot-dns-linode [amd64] (cosmic-proposed) [0.26.0-1]
[11:31] -queuebot:#ubuntu-release- New binary: intel-mkl [i386] (cosmic-proposed/multiverse) [2018.3.222-1] (no packageset)
[11:33] <ginggs> ^^^^ intel-mkl (libmkl-local) on s390x and pcc64el makes no sense, so please don't accept these binaries, if that's an option - the next upload will fix this
[11:35] -queuebot:#ubuntu-release- New binary: intel-mkl [amd64] (cosmic-proposed/multiverse) [2018.3.222-1] (no packageset)
[11:37] -queuebot:#ubuntu-release- New binary: intel-mkl [arm64] (cosmic-proposed/multiverse) [2018.3.222-1] (no packageset)
[11:38] -queuebot:#ubuntu-release- New binary: intel-mkl [armhf] (cosmic-proposed/multiverse) [2018.3.222-1] (no packageset)
[11:41] -queuebot:#ubuntu-release- New: accepted intel-mkl [amd64] (cosmic-proposed) [2018.3.222-1]
[11:41] -queuebot:#ubuntu-release- New: accepted intel-mkl [armhf] (cosmic-proposed) [2018.3.222-1]
[11:41] -queuebot:#ubuntu-release- New: accepted intel-mkl [ppc64el] (cosmic-proposed) [2018.3.222-1]
[11:41] -queuebot:#ubuntu-release- New: accepted intel-mkl [arm64] (cosmic-proposed) [2018.3.222-1]
[11:41] -queuebot:#ubuntu-release- New: accepted intel-mkl [s390x] (cosmic-proposed) [2018.3.222-1]
[11:41] -queuebot:#ubuntu-release- New: accepted intel-mkl [i386] (cosmic-proposed) [2018.3.222-1]
[11:57] <LocutusOfBorg> apw, force-badtest php-horde-http/2.1.7-1
[11:57] <LocutusOfBorg> can you please update it to 2.1.7-3?
[11:57] <LocutusOfBorg> it is under pitti file
[12:01] <apw> LocutusOfBorg, done
[12:10] <ginggs> apw: would you bump the r-cran-curl/3.2-2build1/arm64 in vorlon's hints please?
[12:12] <LocutusOfBorg> thanks!
[12:20] <rbasak> LocutusOfBorg: are you looking at PHP stuff in general?
[12:20] <rbasak> LocutusOfBorg: I intend to give it some attention if needed
[12:21] <LocutusOfBorg> rbasak, I want to make phpunit I boostrapped migrate, and then forget about all this stuff
[12:21] <LocutusOfBorg> :)
[12:23] <LocutusOfBorg> php-mockery php-net-ldap2 needs fixes, otherwise I'll ask to kick them to proposed and then block-proposed with a bug
[12:35] <LocutusOfBorg> rbalint, also php-horde-http needs fixes for testsuite, I made the "obvious" patch, but we are now to the old error https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+sourcepub/9276312/+listing-archive-extra
[12:35] <LocutusOfBorg> and no, I wont' upload a partial testsuite fix, because we have hints
[12:37] <LocutusOfBorg> apw, proposal: kick php-mockery and php-net-ldap2 to proposed, until they are fixed in Debian (they are both RC buggy, no upstream fixes, they do have broken testsuite, leaf packages, out from buster too)
[12:37] <LocutusOfBorg> so we can move forward with phpunit, the whole phpstack, and pcre3
[12:38] <LocutusOfBorg> I don't think we should have a bug with "block-proposed" hint, because they are safe to migrate once fixed automatically
[12:40] <LocutusOfBorg> also imagemagick is blocked by that php
[12:41] -queuebot:#ubuntu-release- Unapproved: linux-meta-hwe (xenial-security/main) [4.15.0.29.51 => 4.15.0.29.51] (kernel) (sync)
[12:42] <apw> LocutusOfBorg, a tollerable plan i suspect, but php-net-ldap2 looks to have rdeps
[12:44] <LocutusOfBorg> simpleid-ldap and php-net-ldap3 are both rc buggy, out of buster
[12:50] <LocutusOfBorg> apw, ^^ does this sound plausible too?
[12:53] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta-hwe [sync] (xenial-security) [4.15.0.29.51]
[13:07] -queuebot:#ubuntu-release- Unapproved: accepted libapache2-mod-perl2 [source] (xenial-proposed) [2.0.9-4ubuntu1.1]
[13:12] <seb128> apw, unsure how the SRUs are being handled but something is buggy, the xorg SRU has been in the queue waiting for a month and is an important fix since the issue is that upgraders that remove unity without purging it are using software rendering
[13:16] <apw> seb128, it is a sync, which is much harder to review, so it doesn't get hit in peoples drive-bys i am sure
[13:18] <rbasak> I tend to assume there's something special going on. Special reviews sometimes take half or a whole day of SRU session, so I don't do them very frequently :-/
[13:19] <seb128> apw, oh come on "much harder", it's 2 clicks away to get to the diff, https://launchpadlibrarian.net/375418303/xorg_1%3A7.7+19ubuntu7_1%3A7.7+19ubuntu7.1.diff.gz
[13:19] <seb128> the queue has a link to the ppa which has the diff
[13:19] <rbasak> seb128: breaks the review tooling
[13:20] <apw> seb128, only if you know that _that_ sync is special from a place that has the extra info
[13:20] <apw> and it is a manual process, and yes it should have been done
[13:20] <seb128> apw, at this end it's just an upload, worth case if you don't know anything it's dget and debdiff
[13:20] <seb128> don't tell me it's that hard
[13:21] <rbasak> I don't think he's saying it's hard so he's not doing it.
[13:21] <apw> as rbasak points out, it is out of process, so it gets shoved 'later'
[13:21] <rbasak> He's saying it looks hard without further investigation and that may explain why it wasn't looked at before.
[13:21] <apw> anyhow, it sounds like something one would want in the point release
[13:22] <seb128> those have been part of our reality for years, it sounds like a lame excuse to let an important LTS issue unreviewed/unfixed for .1 to me
[13:22] <rbasak> AFAIK, the SRU team in general don't make a commitment to process SRUs FIFO or anything like that.
[13:22] <rbasak> Informally we've relied on being poked for important things.
[13:22] <seb128> yeah, that's part of the issue
[13:22] <apw> seb128, right they have, and all the time i have hated on them :)
[13:22] <infinity> The PPA doesn't have the diff.
[13:23] <rbasak> That's not to say that I object to the process being changed or anything.
[13:23] <seb128> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3298/+packages has a "
[13:23] <seb128>     diff from 1:7.7+19ubuntu7 (in Ubuntu) to 1:7.7+19ubuntu7.1 (1.2 KiB)
[13:23] <seb128> " line
[13:23] <infinity> seb128: The PPA has the xorg diff, but not the nux diff, and as soon as someone gets that far, they may decide they have better things to do. :P
[13:23] <rbasak> I'm just explaining the current situation.
[13:23] <infinity> Anyhow, we should get it in today, and it can be released with .1
[13:23] <seb128> infinity, I think the bottom line is that the process is unprofessional
[13:23] <seb128> nobody commits to get important fixes reviewed
[13:23] <infinity> It doesn't need to be on the media, since it's an upgrade issue.
[13:23] <seb128> and people just hand wave that it's not done because the SRU team is "best effort" and "not commiting to anything"
[13:23] <infinity> seb128: Who defines what's "important"?
[13:24] <seb128> well, I guess I'm arguing that from the Canonical side we should have a process to nominate bugs
[13:24] <seb128> and have people commiting to have those fixes reviewed
[13:24] <rbasak> seb128: I agree with that bit.
[13:24] <apw> you do, you come ask for them here
[13:24] <seb128> apw, nagging people is something some consider rude and don't like doing
[13:25] <rbasak> seb128: AIUI, the way it works inside Canonical is that if an SRU isn't getting addressed the managers nominate an SRU team member who is a Canonical employee to sort it out.
[13:25] <seb128> it's also not documented nor fair
[13:25] <apw> which was done yesterday to my knowledge, and we were already in freeze, so it needed the release-team member doing the work to ok it
[13:25] <seb128> we shouldn't end up in that situation in the first place
[13:25] <seb128> if sync are an issue and are not processed it should be documented
[13:25] <rbasak> The trouble is that there are a large number of SRUs that are hell to properly review.
[13:26] <infinity> It's been mentioned many times that syncs are a pain.
[13:26] <rbasak> I prefer to favour traditional bugfixes coming from volunteers since I want to encourage more of those.
[13:26] <infinity> Like, for years.
[13:26] <infinity> Anyway.  Can we maybe refrain from having a two hour debate about it?
[13:26] <infinity> apw: Can you review xorg/nux?
[13:26] <apw> infinity, sure
[13:26] <seb128> if we don't have a debate it's going to come back as an issue again
[13:26] <infinity> apw: Ta.
[13:27] <infinity> seb128: If we do have a debate, it'll also come back as an issue again.
[13:27] <infinity> seb128: If we resolve the debate with useful action, maybe not, but that's less likely to happen in the middle of a release week.
[13:27] <seb128> unless we take steps to address the problem
[13:27] <LocutusOfBorg> apw, do you need any paperwork for the 4 php packages to kick out from release?
[13:27] <seb128> k, fair enough
[13:27] <rbasak> seb128: IMHO, it's something you need to resolve internally with Canonical's Foundations team. Other SRU team members are essentially volunteers.
[13:27] <rbasak> (and you can't force volunteers to do some particular review)
[13:27] <seb128> rbasak, right
[13:28] <seb128> rbasak, but if the team position about sync is "we can't be bothered reviewing them because dget & debdiff is too difficult" that should at least be documented
[13:28] <apw> seb128, i would say, that though there are diffs, they are only advisory, so one has to redo them, which is where the pain comes from
[13:28] <rbasak> You can document what makes SRUs more painful to review, sure.
[13:29] <seb128> apw, it's dget && debdiff, not exactly rocket science either...
[13:29] <rbasak> And that volunteers will tend to do things that seem less painful :)
[13:29] <rbasak> See my recent post to ubuntu-release@ about making diff review easier with git ubuntu :)
[13:29] <apw> seb128, compared to looking at a pregenerated diff in the officially tooling, it is
[13:30] <rbasak> (plug: it works with syncs!)
[13:30] <seb128> k, well I guess I made my point, thx for listening :)
[13:30] <seb128> (and for reviewing)
[13:31] <rbasak> seb128: it's a valid concern, but honestly, I think the right place to raise it is with your manager (to talk to the Canonical Foundations manager, etc)
[13:32] <rbasak> Separately if someone who doesn't have internal access to SRU team members needs to get an urgent SRU through, I think this channel is the right place to request review still.
[13:33] <seb128> rbasak, you are right
[13:34] <seb128> it's a bit annoying how SRUs/point release are being handled nowadays, but that's mostly from a Canonical perspective yes
[13:34] <seb128> like there is no communication on the project list about now being tme for getting fixes in, freeze starting, etc
[13:35] <seb128> rbasak, and yeah, I've no issue asking here or pinging people for reviews but others feel like nagging is rude and don't do it
[13:35] <seb128> it's a cultural thing and not easy to fix :/
[13:36] <rbasak> It's unfortunate, but wearing my Ubuntu hat, if you have volunteers reviewing for other volunteers then review work can't really be enforced at all. The only ways I see around it are polite requests or if a volunteer wants to commit to always reviewing everything.
[13:37] <seb128> yeah
[13:40] -queuebot:#ubuntu-release- Unapproved: accepted crash [source] (xenial-proposed) [7.2.3+real-1~16.04.1]
[13:51] <LocutusOfBorg> rbasak, php-imagick  is a sad thing now :/ blocking imagemagick transition, and I don't want to look at the failure
[14:01] -queuebot:#ubuntu-release- Unapproved: accepted lttng-modules [source] (xenial-proposed) [2.8.0-1ubuntu1~16.04.7]
[14:20] -queuebot:#ubuntu-release- Unapproved: accepted python-wadllib [source] (bionic-proposed) [1.3.2-3ubuntu0.18.04.1]
[14:26] <infinity> seb128: While we're complaining about people's responsibilities WRT SRUs, the nux upload fixing the conffile was accepted to xenial and artful over a month ago and never verified.
[14:26] <infinity> seb128: Which means artful EOLed without the fix being promoted to updates.
[14:27] <infinity> seb128: And xenial still doesn't have the fix.
[14:38] <cjwatson> Just a note about python-wadllib to whoever reviewed it - the xenial diff is all but identical so should be easy to review at the same time
[14:38] <cjwatson> (and thanks)
[14:39] <cjwatson> sil2100: ^- aha, that was you
[14:39] <LocutusOfBorg> doko, https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1340250
[14:40] <LocutusOfBorg> this is what is breaking libunistring and libidn
[14:40] <sil2100> cjwatson: in progress!
[14:40] <sil2100> :)
[14:40] <LocutusOfBorg> why is this an ubuntu only bug?
[14:40] <sil2100> (got distracted)
[14:40] <cjwatson> sil2100: \o/
[14:41] <sil2100> (wanted to have it in xenial for the .5)
[14:42] -queuebot:#ubuntu-release- Unapproved: accepted python-wadllib [source] (xenial-proposed) [1.3.2-3ubuntu0.16.04.1]
[14:43] <doko> LocutusOfBorg: no updates for these packages since 2014?
[14:47] <LocutusOfBorg> but the example code returns correctly 0 in debian, and 2 in ubuntu
[14:47] <LocutusOfBorg> so I presume this is a real bug, and I'm trying to understand what else changed in the meanwhile
[14:48] <LocutusOfBorg> https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+delete-packages I already reverted glibc and glib2.0 uploads
[14:48] <LocutusOfBorg> this is a real bug, a nochange rebuild in bionic fails now
[14:48] <doko> try with -Wl--no-as-needed
[14:48] <LocutusOfBorg> do you have some archive rebuilds of the months before bionic release so we can bisect what changed?
[14:49] <doko> on qa.ubuntuwire.org
[14:49] <LocutusOfBorg> 2018-03-26 libidn was good
[14:51] <LocutusOfBorg> sadly no rebuilds after 20180408
[14:51] <LocutusOfBorg> https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+build/15160733
[14:52] <LocutusOfBorg> interestingly, forcing that weak stuff to disable works
[14:52] <LocutusOfBorg> now checking the as-needed
[14:55] <LocutusOfBorg> doko, do you have build logs for the rebuilds?
[14:57] <LocutusOfBorg> found them nvm
[14:57] <doko> could be a change in binutils 2.31 as well
[15:00] <LocutusOfBorg> let me try with released packages, no updates pocket
[15:03] <LocutusOfBorg> +-  /* Don't generate dynamic GOT relocation against undefined weak
[15:03] <LocutusOfBorg> +-     symbol in executable.  */
[15:03] <LocutusOfBorg> ++  /* Don't generate dynamic GOT relocation against resolved undefined weak
[15:03] <LocutusOfBorg> ++     symbols in an executable.  */
[15:03] <LocutusOfBorg> mmmm
[15:10] <seb128> could somebody skip the udisks2/s390x autopkgtest, it's buggy and it's not new (or better, update the hint's version)?
[15:44] -queuebot:#ubuntu-release- Unapproved: accepted xl2tpd [source] (bionic-proposed) [1.3.10-1ubuntu1]
[15:46] -queuebot:#ubuntu-release- Unapproved: accepted xl2tpd [source] (xenial-proposed) [1.3.6+dfsg-4ubuntu0.16.04.2]
[15:46] <sil2100> Trevinho: hey! I'll try taking a look at those again now
[16:02] <LocutusOfBorg> doko_, wl-asneeded didn't work
[16:04] <LocutusOfBorg> ./vorlon:force-badtest abi-compliance-checker/2.2-2ubuntu1/arm64
[16:04] <LocutusOfBorg> apw, ^^ bump please?
[16:04] <LocutusOfBorg> to avoid bothering, please bump directly to version  2.3-1
[16:04] <LocutusOfBorg> it is in debian deferred queue
[16:13] <slangasek> LocutusOfBorg: done
[16:14] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (bionic-proposed/main) [2.525.2 => 2.525.3] (desktop-core)
[16:14] <infinity> sil2100: ^-- livecd-rootfs review svp.  Try not to vomit.
[16:17] <LocutusOfBorg> thanks!
[16:18] <LocutusOfBorg> wow double hint! so now I don't need anymore the --proposed pocket for the kde retries, nice thanks!
[16:18] <sil2100> infinity: ACK
[16:22] <sil2100> infinity: do we know if having it as the first snap in the list is also a valid fix?
[16:22] <infinity> sil2100: mvo said yes.
[16:22] <sil2100> Ah, we did
[16:23] <sil2100> Ok, I've seen worse hacks around
[16:23] <Trevinho> sil2100: great, thanks
[16:23] <sil2100> ;)
[16:23] <infinity> sil2100: I've written worse hacks, doesn't mean I'm proud of this one existing. :P
[16:24] <infinity> sil2100: And, for the record, as far as SRU rules go, I refuse to "fix" this in cosmic, as I think the glaring bug needs to continue to exist to force people to fix it properly.
[16:24] <infinity> Cause WTF.
[16:24] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (bionic-proposed) [2.525.3]
[16:24] <infinity> "We are designing a new package format that doesn't require dependencies, but also, it has untracked dependencies."
[16:24] <infinity> Well job.
[16:24] <sil2100> infinity: that's fine in this case, cosmic is still rolling on dailies only and it only affects images, so as long as it's fixed before release I think it's ok
[16:28] -queuebot:#ubuntu-release- Unapproved: accepted nux [sync] (bionic-proposed) [4.0.8+18.04.20180622.2-0ubuntu1]
[16:29] -queuebot:#ubuntu-release- Unapproved: accepted xorg [sync] (bionic-proposed) [1:7.7+19ubuntu7.1]
[16:32] <sil2100> Trevinho: so for nux in xenial there's the previous part of the fix still in xenial-proposed
[16:33] <sil2100> Trevinho: since it's the same bug, I'll just approve it
[16:34] -queuebot:#ubuntu-release- Unapproved: accepted nux [sync] (xenial-proposed) [4.0.8+16.04.20180622.2-0ubuntu1]
[16:34] -queuebot:#ubuntu-release- Unapproved: accepted xorg [sync] (xenial-proposed) [1:7.7+13ubuntu3.1]
[16:39] <Trevinho> sil2100: yeah, I will get someone to approve both. Thanks
[17:13] -queuebot:#ubuntu-release- New binary: libhinawa [s390x] (cosmic-proposed/universe) [1.0.0-1] (no packageset)
[17:14] -queuebot:#ubuntu-release- New binary: libhinawa [ppc64el] (cosmic-proposed/universe) [1.0.0-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: libhinawa [amd64] (cosmic-proposed/universe) [1.0.0-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: python-lzo [s390x] (cosmic-proposed/universe) [1.12-2] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: libvirt-dbus [s390x] (cosmic-proposed/universe) [1.2.0-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: libhinawa [i386] (cosmic-proposed/universe) [1.0.0-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: python-lzo [ppc64el] (cosmic-proposed/universe) [1.12-2] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: libvirt-dbus [ppc64el] (cosmic-proposed/universe) [1.2.0-1] (no packageset)
[17:18] -queuebot:#ubuntu-release- New binary: libvirt-dbus [i386] (cosmic-proposed/universe) [1.2.0-1] (no packageset)
[17:18] -queuebot:#ubuntu-release- New binary: python-lzo [amd64] (cosmic-proposed/universe) [1.12-2] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: expeyes [amd64] (cosmic-proposed/universe) [4.4.3+dfsg-2] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: python-lzo [i386] (cosmic-proposed/universe) [1.12-2] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: graphviz-dot-mode [amd64] (cosmic-proposed/universe) [0.4+41+gc456a2b-1] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: ruby-marcel [amd64] (cosmic-proposed/universe) [0.3.2-1] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: libvirt-dbus [amd64] (cosmic-proposed/universe) [1.2.0-1] (no packageset)
[17:24] -queuebot:#ubuntu-release- New binary: libhinawa [arm64] (cosmic-proposed/universe) [1.0.0-1] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: libhinawa [armhf] (cosmic-proposed/universe) [1.0.0-1] (no packageset)
[17:31] -queuebot:#ubuntu-release- New binary: octavia [amd64] (cosmic-proposed/universe) [2.0.1-1] (no packageset)
[17:32] <infinity> bdmurray: Can you verify that vte2.91/bionic SRU ASAP?
[17:32] -queuebot:#ubuntu-release- Unapproved: accepted vte2.91 [source] (bionic-proposed) [0.52.2-1ubuntu1~18.04.2]
[17:33] -queuebot:#ubuntu-release- New binary: python-lzo [arm64] (cosmic-proposed/universe) [1.12-2] (no packageset)
[17:35] -queuebot:#ubuntu-release- New binary: python-lzo [armhf] (cosmic-proposed/universe) [1.12-2] (no packageset)
[17:38] <bdmurray> infinity: Sure, but it only affects upgrades from bionic to cosmic.
[17:39] -queuebot:#ubuntu-release- New binary: libvirt-dbus [arm64] (cosmic-proposed/universe) [1.2.0-1] (no packageset)
[17:40] -queuebot:#ubuntu-release- New binary: libvirt-dbus [armhf] (cosmic-proposed/universe) [1.2.0-1] (no packageset)
[17:48] <infinity> bdmurray: Ahh, okay.  I misread that, then.
[17:48] <infinity> bdmurray: Still nice to verify, but indeed, not point-release-critical.
[18:10] -queuebot:#ubuntu-release- New: accepted expeyes [amd64] (cosmic-proposed) [4.4.3+dfsg-2]
[18:10] -queuebot:#ubuntu-release- New: accepted libhinawa [amd64] (cosmic-proposed) [1.0.0-1]
[18:10] -queuebot:#ubuntu-release- New: accepted libhinawa [armhf] (cosmic-proposed) [1.0.0-1]
[18:10] -queuebot:#ubuntu-release- New: accepted libhinawa [ppc64el] (cosmic-proposed) [1.0.0-1]
[18:10] -queuebot:#ubuntu-release- New: accepted libvirt-dbus [amd64] (cosmic-proposed) [1.2.0-1]
[18:10] -queuebot:#ubuntu-release- New: accepted libvirt-dbus [armhf] (cosmic-proposed) [1.2.0-1]
[18:10] -queuebot:#ubuntu-release- New: accepted libvirt-dbus [ppc64el] (cosmic-proposed) [1.2.0-1]
[18:10] -queuebot:#ubuntu-release- New: accepted octavia [amd64] (cosmic-proposed) [2.0.1-1]
[18:10] -queuebot:#ubuntu-release- New: accepted python-lzo [arm64] (cosmic-proposed) [1.12-2]
[18:10] -queuebot:#ubuntu-release- New: accepted python-lzo [i386] (cosmic-proposed) [1.12-2]
[18:10] -queuebot:#ubuntu-release- New: accepted graphviz-dot-mode [amd64] (cosmic-proposed) [0.4+41+gc456a2b-1]
[18:10] -queuebot:#ubuntu-release- New: accepted libhinawa [i386] (cosmic-proposed) [1.0.0-1]
[18:10] -queuebot:#ubuntu-release- New: accepted libvirt-dbus [arm64] (cosmic-proposed) [1.2.0-1]
[18:10] -queuebot:#ubuntu-release- New: accepted libvirt-dbus [s390x] (cosmic-proposed) [1.2.0-1]
[18:10] -queuebot:#ubuntu-release- New: accepted python-lzo [armhf] (cosmic-proposed) [1.12-2]
[18:10] -queuebot:#ubuntu-release- New: accepted python-lzo [s390x] (cosmic-proposed) [1.12-2]
[18:10] -queuebot:#ubuntu-release- New: accepted libhinawa [arm64] (cosmic-proposed) [1.0.0-1]
[18:10] -queuebot:#ubuntu-release- New: accepted libvirt-dbus [i386] (cosmic-proposed) [1.2.0-1]
[18:10] -queuebot:#ubuntu-release- New: accepted python-lzo [ppc64el] (cosmic-proposed) [1.12-2]
[18:11] -queuebot:#ubuntu-release- New: accepted libhinawa [s390x] (cosmic-proposed) [1.0.0-1]
[18:11] -queuebot:#ubuntu-release- New: accepted ruby-marcel [amd64] (cosmic-proposed) [0.3.2-1]
[18:11] -queuebot:#ubuntu-release- New: accepted python-lzo [amd64] (cosmic-proposed) [1.12-2]
[19:13] -queuebot:#ubuntu-release- Unapproved: aodh (bionic-proposed/main) [6.0.1-0ubuntu1 => 6.0.1-0ubuntu1.1] (openstack, ubuntu-server)
[19:15] <doko_> LocutusOfBorg: I said:  -Wl--no-as-needed
[19:18] <infinity> -Wl,--no-as-needed even.
[19:19] <doko_> ohh, while you are here, do we have an update of the buildd chroots?
[19:20] <infinity> doko_: Colin and I have been working on making them all fancy and automated.  That probably needs another round of review before we get around to using them, though, so I can do one more manual refresh.
[19:21] <doko_> infinity: ok, then maybe wait for gcc-8.2.0 next weekend
[19:21] <infinity> doko_: Next weekend, you can bug me in person instead. :P
[19:35] -queuebot:#ubuntu-release- Unapproved: aodh (xenial-proposed/universe) [2.0.6-0ubuntu1 => 5.1.0-0ubuntu1~cloud1] (openstack)
[19:46] -queuebot:#ubuntu-release- Unapproved: base-files (bionic-proposed/main) [10.1ubuntu2 => 10.1ubuntu2.1] (core)
[19:49] -queuebot:#ubuntu-release- Unapproved: accepted base-files [source] (bionic-proposed) [10.1ubuntu2.1]
[19:52] -queuebot:#ubuntu-release- Unapproved: rejected aodh [source] (xenial-proposed) [5.1.0-0ubuntu1~cloud1]
[20:05] <LocutusOfBorg> doko_, I said, -Wl,--no-as-needed nothing changes...
[20:13] <LocutusOfBorg> doko_, of course I did bad copy-pasting... -no-as-needed worked...
[20:13] <LocutusOfBorg> is this a real fix?
[20:16] <LocutusOfBorg> oh... I forgot to mention you in changelog, bad me :(
[22:11] <infinity> LocutusOfBorg: FWIW, when no-as-needed "fixes" a binary at runtime, that generally means the build system is broken and the binary is being underlinked.
[22:11] <infinity> LocutusOfBorg: And it's just random luck that the underlinking is papered over by some other random linkage accidentally fixing it in passing. :P