[00:35] <rbasak> ^ done, thanks
[00:35] -queuebot:#ubuntu-release- Unapproved: rejected openbox [source] (bionic-proposed) [3.6.1-7ubuntu0.2]
=== pieq_ is now known as pieq
[05:58] <cpaelzer> LocutusOfBorg: yes I'll look after freecad
[05:58] <cpaelzer> it worked with the fix on a cannistack based build and in Debian, I wondere what it is now, loooking ...
[05:59] <cpaelzer> I see that you already did a rebuld which worked (on build)
[05:59] <cpaelzer> thanks
[06:00] <cpaelzer> And the original problem resolved as well with the autopkgtest on 0.19.1+dfsg1-2~build1 being good now
[06:00] <cpaelzer> at least on s390x, checking other arches now ...
[06:52] <RAOF> ddstreet: I'm actually off this week (and next), but it's because I've got childcare duties so I'll see if I can fit it in.
[07:00] <RAOF> ddstreet: bug #1853613 and bug #1864822 are missing the necessary SRU information; bdmurray asked for that on the 10th, and there doesn't appear to have been any activity since then?
[07:00] <ubot5> bug 1853613 in neutron (Ubuntu) "VMs don't get ip from dhcp after compute restart" [Undecided,Incomplete] https://launchpad.net/bugs/1853613
[07:00] <ubot5> bug 1864822 in neutron (Ubuntu) "Openvswitch Agent - Connexion openvswitch DB Broken" [Undecided,Incomplete] https://launchpad.net/bugs/1864822
[08:37] <LocutusOfBorg> yes cpaelzer :D
[08:37] <LocutusOfBorg> thanks for looking at the armhf too
[08:37] <LocutusOfBorg> what about ignoring the failure since it has been there since the begin, and its a problem in Debian too?
[08:51] <apw> xnox, i suspect as that doesn't get bound up with nvidia we can just let it die on the vine and replace it with the upcoming 5.11. ^ sforshee
[09:14] <Laney> The initial seeding of autopkgtest-cloud's database which is running in the new environment currently ...
[09:14] <Laney> it's been happening for 2 days now
[09:15] <Laney> means redeploys will be painful things, hmm
[09:16] <Laney> maybe we should look into backing that up and being able to seed a deployment with a pre-existing copy of the db
[09:21] <cpaelzer> LocutusOfBorg: this is my +1 time, which means looking after cases that usually are ignored :-)
[09:21] <cpaelzer> I'm looking for an ubuntu-archive member to consider https://bugs.launchpad.net/ubuntu/+source/iperf/+bug/1919432 please - anyone around?
[09:21] <ubot5> Ubuntu bug 1919432 in iperf (Ubuntu) "[REMOVE] please remove iperf 2.0.14a+dfsg1 fom hirsute-proposed" [Undecided,New]
[09:26] <LocutusOfBorg> cpaelzer, I can do it then :D
[09:36] <tintou> Hi there, I get frequent crashes with the bamf daemon and would appreciate this to be available in focal 🙂 https://bileto.ubuntu.com/#/ticket/4442
[09:44] <seb128> LocutusOfBorg, you are archive admin now?
[09:44] <LocutusOfBorg> lol seb128
[09:44] <seb128> ?
[09:44] <seb128> sorry I don't understand the joke if that's one
[09:44] <seb128> should I handle that request or are you dealing with it?
[09:45] <LocutusOfBorg> no cpaelzer was answering me something related to netgen/armhf build failure
[09:45] <LocutusOfBorg> but the context has been probably lost in messages sent days ago :)
[09:45] <LocutusOfBorg> this is why it looks funny now with the other messages written after
[09:45] <LocutusOfBorg> I'm not archive admin sorry!
[09:46] <LocutusOfBorg> we were discussing about freecad (fixed now) and netgen on armhf that is the last blocker for migration
[09:46]  * LocutusOfBorg thinks that irc should gain a feature to answer to a specific message, otherwise different conversations are entangled and misunderstanding becomes common... discord has it
[09:49] <cpaelzer> seb128: TL;DR yes please look after the iperf removal if you have the time for it atm
[10:03] <LocutusOfBorg> opencascade should go in in ~10h cpaelzer :)
[10:03] <seb128> cpaelzer, removed
[10:03] <cpaelzer> thanks seb128
[10:03] <seb128> np!
[10:05] <cpaelzer> LocutusOfBorg: how so, did you manage to further track down the sigbus on netgen?
[10:16] <LocutusOfBorg> cpaelzer, I uploaded a patch to dh_auto_test || true on armhf
[10:16] <cpaelzer> ok, thanks
[10:16] <LocutusOfBorg> since the archive won't regress (the sigbus has been there since lots of time)
[10:16] <cpaelzer> yes that also was my summary
[10:16] <LocutusOfBorg> yes so the hammer looks ok wrt "archive sanity"
[10:17] <LocutusOfBorg> (btw armhf is built now!)
[10:20] <LocutusOfBorg> cpaelzer, btw the debian issue is really the same, but unfortunately the link I provided changes when stuff is rebuilt, so it doesn't point anymore to the right failure
[10:20] <LocutusOfBorg> (wrt what you wrote on upstream issue)
[10:20] <cpaelzer> I expected that when not seeing an issue
[10:20] <cpaelzer> but I didn't know for sure that this was the case
[10:21] <LocutusOfBorg> yeah bad me
[10:21] <cpaelzer> np
[10:21] <LocutusOfBorg> I opened that bug after checking if debian was affected too
[10:21] <LocutusOfBorg> btw, do you know that back in the days, we used to fix some armhf unaligned access by using -O0 there?
[10:21] <LocutusOfBorg> let me try on ppa
[10:26] <cpaelzer> I happened to see a few -O0 and froce-gcc-9 fixes, but not for armhf unaligned access
[10:31] <ginggs> there's also a -mno-unaligned-access flag
[10:41] <LocutusOfBorg> testing it now...
[11:12] <LocutusOfBorg> didn't fix :/
[11:12] <LocutusOfBorg> https://launchpadlibrarian.net/528368416/buildlog_ubuntu-hirsute-armhf.netgen_6.2.2006+really6.2.1905+dfsg-2ubuntu3_BUILDING.txt.gz
[11:23] <ddstreet> RAOF ah sorry about that, i was requesting for a teammate and didn't notice they were missing sru data - i'll get them to fix that asap. thanks any enjoy your time off!
[11:24] <cpaelzer> the log does not show the  || true
[11:24] <cpaelzer> so it seems it didn't enter that path at all
[11:29] -queuebot:#ubuntu-release- New binary: linux-signed-azure-4.15 [amd64] (bionic-proposed/main) [4.15.0-1110.122] (no packageset)
[11:30] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (xenial-proposed/main) [4.4.0-206.238] (core, kernel)
[11:32] -queuebot:#ubuntu-release- New binary: linux-signed-gcp-4.15 [amd64] (bionic-proposed/main) [4.15.0-1095.108] (no packageset)
[11:32] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (bionic-proposed/main) [4.15.0-139.143] (core, kernel)
[11:45] <ddstreet> rbasak on your sru shift today, if you have a chance can you review the neutron upload in the bionic queue
[11:49] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (bionic-proposed/main) [4.15.0-139.143] (core, kernel)
[12:04] <tjaalton> src:xwayland is stuck on the new queue for hirsute
[12:08] <sforshee> xnox, apw: I don't care much either way whether that linux-riscv migrates, we will be doing a 5.11 upload this week
[12:08] <apw> sforshee, but you do want to make sure that that upload doesn't have the pointeless udeb which is causing issues
[12:10] <sforshee> apw: of course. Our 5.11 tree has the noudeb profile support so I don't think it should, but we'll confirm before uploading
[12:12] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (xenial-proposed) [4.4.0-206.238]
[12:12] -queuebot:#ubuntu-release- New: accepted linux-signed-azure-4.15 [amd64] (bionic-proposed) [4.15.0-1110.122]
[12:12] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (bionic-proposed) [4.15.0-139.143]
[12:12] -queuebot:#ubuntu-release- New: accepted linux-signed-gcp-4.15 [amd64] (bionic-proposed) [4.15.0-1095.108]
[12:12] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (bionic-proposed) [4.15.0-139.143]
[12:46] <xnox> sforshee:  apw: horay =) doing 360s now. New riscv kernel would be nice, cause then we would be able to cron daily unmatched images.
=== mfo_ is now known as mfo
=== didrocks999 is now known as didrocks
[14:48] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (xenial-proposed/main) [4.15.0-1110.122~16.04.1] (kernel)
[14:50] -queuebot:#ubuntu-release- New binary: linux-signed-gcp [amd64] (xenial-proposed/main) [4.15.0-1095.108~16.04.1] (kernel)
[15:10] <doko> tjaalton: is this entirely new code, or split out from something?
=== alan_g_ is now known as alan_g
[15:17] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (xenial-proposed) [4.15.0-1110.122~16.04.1]
[15:17] -queuebot:#ubuntu-release- New: accepted linux-signed-gcp [amd64] (xenial-proposed) [4.15.0-1095.108~16.04.1]
[15:27] <vorlon> doko: hmm for some reason there are a number of udeb binaries left behind on s390x and riscv64 only https://people.canonical.com/~ubuntu-archive/proposed-migration/hirsute_outdate.txt I'm working on cleaning them up
[15:29] <doko> vorlon: could be the left-over that was built with the dpkg introducing noudeb removed from proposed and not yet avail in release
[15:30] <vorlon> they're all out-of-date udebs
[15:30] <doko> ahh, and we still need to remove the source packages that *only* build udebs, and block-list them
[15:30] <doko> like hw-detect
[15:30] <vorlon> so the newer source did build on these archs, dropping the udebs, but the binaries were left behind on s390x and riscv64
[15:30] <vorlon> and I spot-checked and the binaries seem to have been manually removed by you on the other archs
[15:33] <doko> vorlon: will you remove these, or should I?
[15:33] <doko> tjaalton: so xwayland is a copy of xorg-xserver ... accepting that
[15:34] <vorlon> doko: I'm taking care of them
[15:34] <vorlon> just wanted to let you know something seemed to have gone wrong
[15:34] -queuebot:#ubuntu-release- New: accepted xwayland [source] (hirsute-proposed) [2:21.0.99.902-0ubuntu1]
[16:34] <LocutusOfBorg> jamespage, hello, is python-ceilometerclient syncable?
[17:16] <dosaboy_> bdmurray: hi sorry i missed your msg, i caught it in https://bugs.launchpad.net/neutron/+bug/1853613
[17:16] <ubot5> Ubuntu bug 1853613 in neutron (Ubuntu) "VMs don't get ip from dhcp after compute restart" [Undecided,Incomplete]
=== dosaboy_ is now known as dosaboy
[17:17] <dosaboy> bdmurray: so basically that SRU contains 7 patches that all form part of the same fix for which the test is the same
[17:17] <dosaboy> so i tried to simplify it by putting the template in one bug and referencing it from the others
[17:18] <dosaboy> since the verification need only happen once i.e. in one LP
[17:18] <dosaboy> bdmurray: if there is anything else i can do to make that make more sense please let me know
[17:23] <dosaboy> rbasak: sorry i think i meant to ping you since brian is out
[17:52] <tjaalton> doko: yes, it's a stripped version that only builds xwayland deb.. thanks!
[18:19] <xnox> vorlon: i think it was just timing & the fact that we did process all the amd64 ones and then wanted to wait for them to rattle out. Then i uploaded drops for all other arches, but didn't think of out of date binaries, nor did i ping anybody about them.
[18:20] <xnox> so i don't think there was active effort to spot them & remove them. I thought everything was fine.
[18:34] <LocutusOfBorg> cpaelzer, opencascade should go in on next round
[18:36] <cpaelzer> \o/
[18:48] -queuebot:#ubuntu-release- Unapproved: runc (groovy-proposed/main) [1.0.0~rc10-0ubuntu2 => 1.0.0~rc93-0ubuntu1~20.10.1] (ubuntu-server)
[18:52] -queuebot:#ubuntu-release- Unapproved: runc (focal-proposed/main) [1.0.0~rc10-0ubuntu1 => 1.0.0~rc93-0ubuntu1~20.04.1] (no packageset)
[18:57] -queuebot:#ubuntu-release- Unapproved: runc (bionic-proposed/universe) [1.0.0~rc10-0ubuntu1~18.04.2 => 1.0.0~rc93-0ubuntu1~18.04.1] (no packageset)
[19:02] -queuebot:#ubuntu-release- Unapproved: containerd (groovy-proposed/main) [1.3.7-0ubuntu3.3 => 1.4.4-0ubuntu1~20.10.1] (ubuntu-server)
[19:06] -queuebot:#ubuntu-release- Unapproved: containerd (focal-proposed/main) [1.3.3-0ubuntu2.3 => 1.4.4-0ubuntu1~20.04.1] (no packageset)
[19:10] -queuebot:#ubuntu-release- Unapproved: containerd (bionic-proposed/universe) [1.3.3-0ubuntu1~18.04.4 => 1.4.4-0ubuntu1~18.04.1] (no packageset)
[19:16] -queuebot:#ubuntu-release- Unapproved: docker.io (groovy-proposed/universe) [19.03.13-0ubuntu3.1 => 20.10.2-0ubuntu1~20.10.1] (no packageset)
[19:20] -queuebot:#ubuntu-release- Unapproved: docker.io (focal-proposed/universe) [19.03.8-0ubuntu1.20.04.2 => 20.10.2-0ubuntu1~20.04.1] (no packageset)
[19:24] -queuebot:#ubuntu-release- Unapproved: docker.io (bionic-proposed/universe) [19.03.6-0ubuntu1~18.04.3 => 20.10.2-0ubuntu1~18.04.1] (no packageset)
[19:43] -queuebot:#ubuntu-release- Unapproved: nfs-utils (focal-proposed/main) [1:1.3.4-2.5ubuntu3.3 => 1:1.3.4-2.5ubuntu3.4] (core)
[19:46] -queuebot:#ubuntu-release- Unapproved: nfs-utils (groovy-proposed/main) [1:1.3.4-2.5ubuntu6 => 1:1.3.4-2.5ubuntu6.1] (core)
[19:47] -queuebot:#ubuntu-release- Unapproved: nfs-utils (bionic-proposed/main) [1:1.3.4-2.1ubuntu5.3 => 1:1.3.4-2.1ubuntu5.4] (core)
[21:35] -queuebot:#ubuntu-release- Unapproved: systemd (groovy-proposed/main) [246.6-1ubuntu1.2 => 246.6-1ubuntu1.3] (core, i386-whitelist)
[21:38] -queuebot:#ubuntu-release- Unapproved: systemd (focal-proposed/main) [245.4-4ubuntu3.5 => 245.4-4ubuntu3.6] (core, i386-whitelist)
[21:40] -queuebot:#ubuntu-release- Unapproved: systemd (bionic-proposed/main) [237-3ubuntu10.45 => 237-3ubuntu10.46] (core)
[21:43] -queuebot:#ubuntu-release- Unapproved: systemd (xenial-proposed/main) [229-4ubuntu21.29 => 229-4ubuntu21.30] (core)