[05:03] <cpaelzer> Hi, I wanted to ask about autopkgtest as I've realized that one of the tests I've run there seems to hang indefinitely
[05:03] <cpaelzer> I haven't done anything special, but seeing it hang for 64h 57m 17s by now makes me assume that whatever timeouts we have in place missed it
[05:04] <cpaelzer> and since I don't want to block the resources I wanted to ask if/how we could cancel that
[05:04] <cpaelzer> The test is chrony @ impish  @ armhf for a PPA build in 'chrony/4.1~pre1-1ubuntu1~impishppa1'
[05:05] <cpaelzer> The other architectures completed, but this armhf one seems to hang at the initial juju/autopkgtest call (if the output on https://autopkgtest.ubuntu.com/running#pkg-chrony is up to date)
[05:06] <cpaelzer> I see that I'm not alone 9x > 63h - and I guess all of them are MIA in some way
[06:03] -queuebot:#ubuntu-release- Unapproved: libvirt-dbus (hirsute-proposed/universe) [1.4.0-2 => 1.4.0-2ubuntu0.1] (no packageset)
[07:18] -queuebot:#ubuntu-release- Unapproved: rejected linux-base [source] (focal-proposed) [4.5ubuntu3.3]
[07:22] -queuebot:#ubuntu-release- Unapproved: rejected linux-base [source] (hirsute-proposed) [4.5ubuntu6]
[08:36] <Laney> cpaelzer: I killed some, I think they got in a weird state due to the network outages that were happening last week :(
[08:36] <Laney> autopkgtest is supposed to timeout but seems like there's situations where that doesn't work
[08:39] <Laney> yikes
[08:39] <Laney> I missed groovy from the list of release for autopkgtest /o\ /o\ /o\ /o\ /o\
[08:39] <Laney> sorry groovy requesters
[08:40] <Laney> I was like "why aren't these requests being executed?" thinking rabbitmq was broken
[08:43] -queuebot:#ubuntu-release- Unapproved: gnome-calculator (hirsute-proposed/main) [1:40.0-2ubuntu1 => 1:40.1-0ubuntu1] (ubuntu-desktop)
[08:57] -queuebot:#ubuntu-release- Unapproved: gnome-disk-utility (hirsute-proposed/main) [40.0-1ubuntu1 => 40.1-0ubuntu1] (ubuntu-desktop)
[09:10] <cpaelzer> thank you Laney
[09:11] <cpaelzer> that was the cleanup I was looking for
[09:15] <Laney> np
[09:15] <Laney> ok groovy results are flowing now
[09:18] <RikMills> 'arch: linux-any' packages are now not building for riscv64, so showing as build missing on excuses
[09:20] <Laney> good spot
[09:20] <Laney> where is that evaluated though?
[09:20]  * Laney doesn't know
[09:21] <RikMills> neither do I :/
[09:23]  * Laney decides who to ping
[09:23] <Laney> wgrant: ^- can you guide us in the right direction?
[09:23] <Laney> https://launchpad.net/ubuntu/+source/fuse3/3.10.3-1 is an example
[09:40] <doko> ohh, that's a fun one
[09:44] <cpaelzer> Laney: not sure why but exactly the chrony job that made me find this situation isstill considered running
[09:44] <cpaelzer> https://autopkgtest.ubuntu.com/running#pkg-chrony
[09:44] <cpaelzer> 69h
[09:46] <cpaelzer> Do I need to do something since it is a ppa based job?
[09:57] <Laney> cpaelzer: it just finished afaics
[09:59] <Laney> https://autopkgtest.ubuntu.com/results/autopkgtest-impish-ci-train-ppa-service-4541/impish/armhf/c/chrony/20210503_094957_951e1@/log.gz
[10:11]  * ginggs welcomes our new ubuntu/kfreebsd/riscv64 overlords
[10:47] <Laney> asking in #launchpad about it
[10:47] <RikMills> cheers
[10:58] <rbalint> Laney, rbasak please remove glibc 2.31-0ubuntu9.3 from focal-proposed, i've saved it to https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4547
[10:59] <rbalint> Laney, rbasak it causes crashes and some people test it from -proposed
[11:00] <Laney> okey dokey
[11:00] <Laney> rbalint: do you have a bug reference for the removal message?
[11:01] <rbalint> LP: #1926355
[11:01] <ubot3> Launchpad bug 1926355 in snap-core20 "Snap applications segfault with new core20 (rev: 1015+)" [Critical, New] https://launchpad.net/bugs/1926355
[11:01] <Laney> merci
[11:01] <rbalint> merci beaucoup :-)
[11:02] <Laney> it is done
[11:03] -queuebot:#ubuntu-release- Unapproved: epiphany-browser (hirsute-proposed/universe) [40.0-2 => 40.1-0ubuntu1] (desktop-extra)
[11:04] <doko> Laney: if you want to save some time, you could remove all glibc triggered autopkg tests on arm64, we will need a new upload anyway
[11:04] <Laney> O RLY
[11:04] <Laney> I do want to save some time!
[11:04] <Laney> poor old arm64
[11:05] <doko> ta
[11:08] <Laney> doko: shall we remove it from proposed too?
[11:08] <Laney> if you get a gcc-10/armhf build ever then it'll trigger all the tests there
[11:09] <doko> no, please keept it there. the build itself is good
[11:48] <kanashiro> ubuntu-archive: could any AA process resource-agents in the impish NEW queue?
[11:53] <vorlon> kanashiro: hi, I had sent some questions about it on Friday; I'm looking to understand why resource-agents doesn't depend or recommend resource-agents-supported so that upgrades don't drop the one supported agent
[12:00] <mdeslaur> looks like we lost our security PPA autopkgtests? https://people.canonical.com/~platform/security-britney/current/
[12:04] <kanashiro> vorlon, hi o/ sorry, I missed those messages. That's a good point, I think a recommends would be more appropriate
[12:05] <vorlon> kanashiro: ok. do you want to fix before I accept into the archive?
[12:05] <kanashiro> vorlon, yes, doing it now
[12:09] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (hirsute-proposed) [3.192.40.2]
[12:09] <paride> kanashiro, I think the same Recommends should be added to fence-agents?
[12:09] <kanashiro> paride, yes, I'll do the same in fence-agents
[12:11] <jamespage> o/
[12:11] <jamespage> the ceph updates in focal and groovy proposed failed verification for https://launchpad.net/bugs/1914584
[12:11] <ubot3> Launchpad bug 1914584 in ceph (Ubuntu Bionic) "[SRU] radosgw-admin user create error message confusing if user with email already exists" [Low, Triaged]
[12:12] <jamespage> I've uploaded revised versions which drop that patch - if they could be accepted that would be helpful so we can resume the verification process for the point release and arm64 related fixes (which include a security update)
[12:19] <vorlon> Laney: arm64 queue dropped substantially - did someone sort out what was going wrong w/ the runners, or is this drop something else?
[12:19] <Laney> vorlon: see doko's request just above
[12:20] <vorlon> ah ok
[12:20] <vorlon> so arm64 runners still borked? :/
[12:20] <Laney> well
[12:20] <Laney> I wouldn't say borked, they're working, but could be better
[12:20] <Laney> 1) those new servers aren't available in bos01 still, so that's all the old slow hardware
[12:20] <Laney> 2) many reboots we initiate are failing to actually reboot and spewing some IRQ error instead
[12:21] <Laney> 3) that port quota thing I raised / prioritised is still unfixed
[12:21] <Laney> so yeah
[12:21] <vorlon> available in bos01> do we not have bos02 runners in the new deployment?
[12:21] <Laney> yes
[12:21] <Laney> but it's not as fast as it could be, half the fast machines aren't online
[12:21] <vorlon> ah ok
[12:22] <Laney> but despite all this, tests are still getting finished ¬_¬
[12:23] <RikMills> the libreoffice ones seems to be staring over again and again
[12:23] <RikMills> *starting
[12:24] <Laney> they'll get there
[12:24] <Laney> see (2)
[12:24] <RikMills> well, they keep requeue ate the top of the queue, so I guess o
[12:24] <RikMills> *so
[12:25] <RikMills> thanks
[12:27] <RikMills> think I need more coffee before trying to type again ;)
[12:40] -queuebot:#ubuntu-release- Unapproved: apache2 (precise-security/main) [2.2.22-1ubuntu1.11 => 2.2.22-1ubuntu1.15] (core) (sync)
[12:40] -queuebot:#ubuntu-release- Unapproved: aptdaemon (precise-security/main) [0.43+bzr805-0ubuntu10 => 0.43+bzr805-0ubuntu10.1] (core, unr) (sync)
[12:40] -queuebot:#ubuntu-release- Unapproved: apport (precise-security/main) [2.0.1-0ubuntu17.15 => 2.0.1-0ubuntu17.16] (core) (sync)
[12:40] -queuebot:#ubuntu-release- Unapproved: aspell (precise-security/main) [0.60.7~20110707-1 => 0.60.7~20110707-1ubuntu0.1] (core) (sync)
[12:41] -queuebot:#ubuntu-release- Unapproved: avahi (precise-security/main) [0.6.30-5ubuntu2.2 => 0.6.30-5ubuntu2.3] (core) (sync)
[12:41] -queuebot:#ubuntu-release- Unapproved: bind9 (precise-security/main) [1:9.8.1.dfsg.P1-4ubuntu0.22 => 1:9.8.1.dfsg.P1-4ubuntu0.32] (core) (sync)
[12:41] -queuebot:#ubuntu-release- Unapproved: bzr (precise-security/main) [2.5.1-0ubuntu2 => 2.5.1-0ubuntu2.1] (bzr, core) (sync)
[12:41] -queuebot:#ubuntu-release- Unapproved: clamav (precise-security/main) [0.99.2+addedllvm-0ubuntu0.12.04.1 => 0.102.4+dfsg-0ubuntu0.12.04.1] (ubuntu-desktop, ubuntu-server) (sync)
[12:41] -queuebot:#ubuntu-release- Unapproved: curl (precise-security/main) [7.22.0-3ubuntu4.17 => 7.22.0-3ubuntu4.29] (core) (sync)
[12:41] -queuebot:#ubuntu-release- Unapproved: bash (precise-security/main) [4.2-2ubuntu2.6 => 4.2-2ubuntu2.9] (core) (sync)
[12:41] -queuebot:#ubuntu-release- Unapproved: ca-certificates (precise-security/main) [20160104ubuntu0.12.04.1 => 20190110~12.04.1] (core) (sync)
[12:41] -queuebot:#ubuntu-release- Unapproved: bzip2 (precise-security/main) [1.0.6-1 => 1.0.6-1ubuntu0.2] (core) (sync)
[12:41] -queuebot:#ubuntu-release- Unapproved: cpio (precise-security/main) [2.11-7ubuntu3.2 => 2.11-7ubuntu3.3] (core) (sync)
[12:42] -queuebot:#ubuntu-release- Unapproved: cyrus-sasl2 (precise-security/main) [2.1.25.dfsg1-3ubuntu0.1 => 2.1.25.dfsg1-3ubuntu0.2] (core) (sync)
[12:42] -queuebot:#ubuntu-release- Unapproved: db4.8 (precise-security/main) [4.8.30-11ubuntu1 => 4.8.30-11ubuntu1.1] (core) (sync)
[12:42] -queuebot:#ubuntu-release- Unapproved: dbus (precise-security/main) [1.4.18-1ubuntu1.8 => 1.4.18-1ubuntu1.10] (core) (sync)
[12:42] -queuebot:#ubuntu-release- Unapproved: distro-info (precise-security/main) [0.8.2 => 0.8.2ubuntu1] (ubuntu-server) (sync)
[12:42] -queuebot:#ubuntu-release- Unapproved: dovecot (precise-security/main) [1:2.0.19-0ubuntu2.2 => 1:2.0.19-0ubuntu2.8] (kubuntu, netbook, ubuntu-desktop, ubuntu-server) (sync)
[12:42] -queuebot:#ubuntu-release- Unapproved: e2fsprogs (precise-security/main) [1.42-1ubuntu2.3 => 1.42-1ubuntu2.5] (core) (sync)
[12:42] -queuebot:#ubuntu-release- Unapproved: davfs2 (precise-security/universe) [1.4.6-1ubuntu3 => 1.4.6-1ubuntu3.1] (no packageset) (sync)
[12:42] -queuebot:#ubuntu-release- Unapproved: distro-info-data (precise-security/main) [0.8ubuntu0.12 => 0.8ubuntu0.21] (ubuntu-server) (sync)
[12:42] -queuebot:#ubuntu-release- Unapproved: dpkg (precise-security/main) [1.16.1.2ubuntu7.8 => 1.16.1.2ubuntu7.9] (core) (sync)
[12:42] -queuebot:#ubuntu-release- Unapproved: db (precise-security/main) [5.1.25-11build1 => 5.1.25-11ubuntu0.1] (core) (sync)
[12:42] -queuebot:#ubuntu-release- Unapproved: eglibc (precise-security/main) [2.15-0ubuntu10.18 => 2.15-0ubuntu10.23] (core) (sync)
[12:42] -queuebot:#ubuntu-release- Unapproved: dnsmasq (precise-security/main) [2.59-4ubuntu0.2 => 2.59-4ubuntu0.4] (core, unr) (sync)
[12:42] <kanashiro> vorlon, uploaded a new version of resource-agents
[12:43] -queuebot:#ubuntu-release- Unapproved: expat (precise-security/main) [2.0.1-7.2ubuntu1.4 => 2.0.1-7.2ubuntu1.7] (core) (sync)
[12:43] -queuebot:#ubuntu-release- Unapproved: freetype (precise-security/main) [2.4.8-1ubuntu2.6 => 2.4.8-1ubuntu2.7] (core) (sync)
[12:43] -queuebot:#ubuntu-release- Unapproved: glib2.0 (precise-security/main) [2.32.4-0ubuntu1 => 2.32.4-0ubuntu1.4] (core) (sync)
[12:43] -queuebot:#ubuntu-release- Unapproved: file (precise-security/main) [5.09-2ubuntu0.6 => 5.09-2ubuntu0.8] (core) (sync)
[12:43] -queuebot:#ubuntu-release- Unapproved: gettext (precise-security/main) [0.18.1.1-5ubuntu3 => 0.18.1.1-5ubuntu3.1] (core) (sync)
[12:45] -queuebot:#ubuntu-release- Unapproved: gnupg (precise-security/main) [1.4.11-3ubuntu2.10 => 1.4.11-3ubuntu2.12] (core) (sync)
[12:45] -queuebot:#ubuntu-release- New binary: resource-agents [s390x] (impish-proposed/main) [1:4.7.0-1ubuntu3] (ubuntu-server)
[12:46] -queuebot:#ubuntu-release- Unapproved: accepted apache2 [sync] (precise-security) [2.2.22-1ubuntu1.15]
[12:46] -queuebot:#ubuntu-release- Unapproved: accepted aptdaemon [sync] (precise-security) [0.43+bzr805-0ubuntu10.1]
[12:46] -queuebot:#ubuntu-release- Unapproved: accepted avahi [sync] (precise-security) [0.6.30-5ubuntu2.3]
[12:46] -queuebot:#ubuntu-release- Unapproved: accepted bind9 [sync] (precise-security) [1:9.8.1.dfsg.P1-4ubuntu0.32]
[12:46] -queuebot:#ubuntu-release- Unapproved: accepted bzr [sync] (precise-security) [2.5.1-0ubuntu2.1]
[12:46] -queuebot:#ubuntu-release- Unapproved: accepted clamav [sync] (precise-security) [0.102.4+dfsg-0ubuntu0.12.04.1]
[12:46] -queuebot:#ubuntu-release- Unapproved: accepted curl [sync] (precise-security) [7.22.0-3ubuntu4.29]
[12:46] -queuebot:#ubuntu-release- Unapproved: accepted davfs2 [sync] (precise-security) [1.4.6-1ubuntu3.1]
[12:46] -queuebot:#ubuntu-release- Unapproved: accepted db [sync] (precise-security) [5.1.25-11ubuntu0.1]
[12:46] -queuebot:#ubuntu-release- Unapproved: accepted distro-info [sync] (precise-security) [0.8.2ubuntu1]
[12:46] -queuebot:#ubuntu-release- Unapproved: accepted apport [sync] (precise-security) [2.0.1-0ubuntu17.16]
[12:46] -queuebot:#ubuntu-release- Unapproved: accepted bash [sync] (precise-security) [4.2-2ubuntu2.9]
[12:46] -queuebot:#ubuntu-release- Unapproved: accepted ca-certificates [sync] (precise-security) [20190110~12.04.1]
[12:47] -queuebot:#ubuntu-release- Unapproved: accepted cyrus-sasl2 [sync] (precise-security) [2.1.25.dfsg1-3ubuntu0.2]
[12:47] -queuebot:#ubuntu-release- Unapproved: accepted dbus [sync] (precise-security) [1.4.18-1ubuntu1.10]
[12:47] -queuebot:#ubuntu-release- Unapproved: accepted aspell [sync] (precise-security) [0.60.7~20110707-1ubuntu0.1]
[12:47] -queuebot:#ubuntu-release- Unapproved: accepted cpio [sync] (precise-security) [2.11-7ubuntu3.3]
[12:47] -queuebot:#ubuntu-release- Unapproved: accepted bzip2 [sync] (precise-security) [1.0.6-1ubuntu0.2]
[12:47] -queuebot:#ubuntu-release- Unapproved: accepted db4.8 [sync] (precise-security) [4.8.30-11ubuntu1.1]
[12:47] -queuebot:#ubuntu-release- New binary: resource-agents [amd64] (impish-proposed/main) [1:4.7.0-1ubuntu3] (ubuntu-server)
[12:47] -queuebot:#ubuntu-release- Unapproved: accepted distro-info-data [sync] (precise-security) [0.8ubuntu0.21]
[12:47] -queuebot:#ubuntu-release- Unapproved: accepted dovecot [sync] (precise-security) [1:2.0.19-0ubuntu2.8]
[12:47] -queuebot:#ubuntu-release- Unapproved: accepted e2fsprogs [sync] (precise-security) [1.42-1ubuntu2.5]
[12:47] -queuebot:#ubuntu-release- Unapproved: accepted expat [sync] (precise-security) [2.0.1-7.2ubuntu1.7]
[12:47] -queuebot:#ubuntu-release- Unapproved: accepted freetype [sync] (precise-security) [2.4.8-1ubuntu2.7]
[12:47] -queuebot:#ubuntu-release- Unapproved: accepted glib2.0 [sync] (precise-security) [2.32.4-0ubuntu1.4]
[12:47] -queuebot:#ubuntu-release- Unapproved: accepted dnsmasq [sync] (precise-security) [2.59-4ubuntu0.4]
[12:47] -queuebot:#ubuntu-release- Unapproved: accepted eglibc [sync] (precise-security) [2.15-0ubuntu10.23]
[12:47] -queuebot:#ubuntu-release- Unapproved: accepted gettext [sync] (precise-security) [0.18.1.1-5ubuntu3.1]
[12:47] -queuebot:#ubuntu-release- Unapproved: accepted dpkg [sync] (precise-security) [1.16.1.2ubuntu7.9]
[12:47] -queuebot:#ubuntu-release- Unapproved: rejected gnupg [sync] (precise-security) [1.4.11-3ubuntu2.12]
[12:47] -queuebot:#ubuntu-release- Unapproved: accepted file [sync] (precise-security) [5.09-2ubuntu0.8]
[12:48] -queuebot:#ubuntu-release- New binary: resource-agents [arm64] (impish-proposed/main) [1:4.7.0-1ubuntu3] (ubuntu-server)
[12:48] -queuebot:#ubuntu-release- New binary: resource-agents [ppc64el] (impish-proposed/main) [1:4.7.0-1ubuntu3] (ubuntu-server)
[12:48] -queuebot:#ubuntu-release- New binary: resource-agents [armhf] (impish-proposed/main) [1:4.7.0-1ubuntu3] (ubuntu-server)
[12:59] <Laney> welp, Boston just went down again
[13:07] <vorlon> FYI with precise having reached the end of life of the ESM product, the security updates from ESM are being merged into the Ubuntu archive (precise-security) and the lot will be archived off to old-releases.  If anyone is surprised to see updates to precise happening, that's what's up
[13:18] -queuebot:#ubuntu-release- New binary: resource-agents [riscv64] (impish-proposed/main) [1:4.7.0-1ubuntu3] (ubuntu-server)
[13:32] -queuebot:#ubuntu-release- New: accepted resource-agents [amd64] (impish-proposed) [1:4.7.0-1ubuntu2]
[13:32] -queuebot:#ubuntu-release- New: accepted resource-agents [armhf] (impish-proposed) [1:4.7.0-1ubuntu2]
[13:33] -queuebot:#ubuntu-release- New: accepted resource-agents [riscv64] (impish-proposed) [1:4.7.0-1ubuntu2]
[13:33] -queuebot:#ubuntu-release- New: accepted resource-agents [amd64] (impish-proposed) [1:4.7.0-1ubuntu3]
[13:33] -queuebot:#ubuntu-release- New: accepted resource-agents [armhf] (impish-proposed) [1:4.7.0-1ubuntu3]
[13:33] -queuebot:#ubuntu-release- New: accepted resource-agents [riscv64] (impish-proposed) [1:4.7.0-1ubuntu3]
[13:33] -queuebot:#ubuntu-release- New: accepted resource-agents [arm64] (impish-proposed) [1:4.7.0-1ubuntu2]
[13:33] -queuebot:#ubuntu-release- New: accepted resource-agents [s390x] (impish-proposed) [1:4.7.0-1ubuntu2]
[13:33] -queuebot:#ubuntu-release- New: accepted resource-agents [ppc64el] (impish-proposed) [1:4.7.0-1ubuntu3]
[13:33] -queuebot:#ubuntu-release- New: accepted resource-agents [ppc64el] (impish-proposed) [1:4.7.0-1ubuntu2]
[13:33] -queuebot:#ubuntu-release- New: accepted resource-agents [s390x] (impish-proposed) [1:4.7.0-1ubuntu3]
[13:33] -queuebot:#ubuntu-release- New: accepted resource-agents [arm64] (impish-proposed) [1:4.7.0-1ubuntu3]
=== _hc[m] is now known as _hc
[14:27] -queuebot:#ubuntu-release- Unapproved: shim (hirsute-proposed/main) [15.4-0ubuntu1 => 15.4-0ubuntu2] (core) (sync)
[14:48] <doko> vorlon: fyi, https://bugs.launchpad.net/bugs/1926964
[14:48] <ubot3> Launchpad bug 1926964 in python-apt (Ubuntu) "missing libapt-pkg4.12 dependency" [Undecided, New]
[15:54] <Laney> I filed a bug about the reboot thing btw https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926955
[15:54] <ubot3> Launchpad bug 1926955 in linux (Ubuntu) "arm64 eMAG system often failng to reboot with 'IRQ Exception at 0x000000009BC11F38'" [Undecided, Confirmed]
[15:54] <Laney> cpaelzer: might interest you ^^^^^^^
[15:56] <Laney> I was blaming the hw but it just occurred to me that the host OS version might be different, have asked IS to check
[15:56] <cpaelzer> interesting
[15:58] <Laney> interesting to you because edk2 is being blamed ;-)
[15:59] <sforshee> note that I'm not necessarily blaming edk2, just that this is where the message seems to be coming from
[16:01] <Laney> heh yeah, sorry, it's mainly that it made me feel like cpaelzer should be looped in now
[16:02] <sforshee> no worries, just wanted to be clear :-)
[16:02] <Laney> could be like "oh, yeah, that's a bug I know about, you need commit foobarbaz"
[16:04] <sforshee> it looks like EDK2 doesn't expect irq exceptions but gets one anyway, so could be something that the kernel doesn't clean up properly on reboot or something like that
[16:10] <vorlon> doko: fixed
[16:10] <vorlon> doko: thanks for flagging
[16:37] <ddstreet> doko so is -Werror basically no longer usable with gcc in h and later? due to it suddenly starting to warn for possible uninitialized vars and/or null dereferences or other things that a human review of the code shows aren't possible?
[16:51] -queuebot:#ubuntu-release- Unapproved: shim-signed (hirsute-proposed/main) [1.46 => 1.46.1] (core)
[17:33] <doko> ddstreet: please can you point to such code?
[17:34] <ddstreet> e.g. https://code.launchpad.net/~ubuntu-support-team/+recipe/systemd and https://code.launchpad.net/~ubuntu-support-team/+recipe/elfutils
[17:35] <ddstreet> e.g. https://launchpadlibrarian.net/536740411/buildlog_ubuntu-hirsute-ppc64el.systemd_248.666.gd4d7127d94+21.04.20210503043716_BUILDING.txt.gz
[17:35] <ddstreet> e.g. https://launchpadlibrarian.net/536683989/buildlog_ubuntu-hirsute-amd64.elfutils_0.183.43.g92980edc+21.04.20210502190301_BUILDING.txt.gz
[18:02] <doko> ddstreet: did you update the packaging for elfutils from the elfutils package?
[18:04] <ddstreet> doko i'm aware that debian elfutils disables -Werror since ~2018, but yeah i don't include any debian/ubuntu patches, it's straight building of the upstream code
[18:07] <doko> well, if you build with -Werror which includes a -W having *maybe* in it's name ...
[18:07] <ddstreet> point is, the exact same upstream code builds fine for all archs in g and earler
[18:07] <ddstreet> with the exact same packaging
[18:08] <doko> yes, -flto exposes for more warnings
[18:08] <doko> and I assume it's the same for systemd
[18:10] <ddstreet> so then it's yes, -Werror isn't really useful anymore in h and later (without specific additional flags to silence incorrect warnings)
[18:10] <doko> is it just this warning, or other warnings as well?
[18:11] <ddstreet> it's different warnings for the systemd and elfutils examples
[18:11] <ddstreet> i suspect there will be more
[18:11] <ddstreet> the systemd code that generates the warning, for example, is years old
[18:12] <doko> s/maybe/potential/
[18:12] <doko> I can bring that up upstream
[18:14] <doko> but if you want to test straight upstream code, you should disable hardening flags as well ;p
[18:17] <ddstreet> yeah, i try to change as little as possible in the debian/ packaging but maybe i should strip it down
[18:19] <doko> I would add a patch to add -Wno-error= to the places where -Werror is set, or send a fix upstream, or complain that gcc shouldn't emit the warning. or disable lto in your recipe
[19:28] <kanashiro> hey o/ is there a way to know the reason of a package demotion? I want to understand why fence-agents was demoted in Trusty. I tried to find a bug report but there is none AFAICS
[19:33] <sarnold> I think the usual reason is when packages 'fall out' of main due to either no longer being a dependency of a seeded main package
[19:33] <vorlon> kanashiro: best to look at seeds or reverse-dependencies; generally things get demoted when the seeds no longer pull them in, not much process required
[20:25] <doko> Laney, vorlon: https://people.canonical.com/~ubuntu-archive/proposed-migration/focal/update_excuses.html#openjdk-16  are the armhf tests still running? I don't think so.
[22:04] <vorlon> doko: well, https://autopkgtest.ubuntu.com/running shows that they are not.  I'll requeue all that have gone missing