[00:07] <amurray> vorlon: ok, thanks - how do I find out who is the SRU team member for today?
[00:43] <RAOF> amurray: https://wiki.ubuntu.com/StableReleaseUpdates#Publishing
[01:00] -queuebot:#ubuntu-release- New binary: libplacebo [s390x] (groovy-proposed/universe) [1.29.1+dfsg1-2] (i386-whitelist, kubuntu)
[01:05] <amurray> RAOF: thanks - somehow I missed that - would you be able to review the libseccomp updates currently in the security-proposed PPA https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+packages in light of LP #1876055
[01:05] <ubot5> Launchpad bug 1876055 in libseccomp (Ubuntu Focal) "SRU: Backport 2.4.3-1ubuntu2 from groovy to focal/eoan/bionic/xenial for newer syscalls for core20 base" [Medium,Confirmed] https://launchpad.net/bugs/1876055
[01:12] <RAOF> Will do.
[03:22] <RAOF> amurray: The focal upload appears to be missing a reference to LP #1876055?
[03:22] <ubot5> Launchpad bug 1876055 in libseccomp (Ubuntu Focal) "SRU: Backport 2.4.3-1ubuntu2 from groovy to focal/eoan/bionic/xenial for newer syscalls for core20 base" [Medium,Confirmed] https://launchpad.net/bugs/1876055
[03:24] <RAOF> Hm. I guess that 1876055 doesn't actually apply to the focal package, as focal already has 2.4.3.
[03:29] <RAOF> LP #1877633 should have the SRU paperwork filled out. Or, alternatively, you could mark it as a duplicate of 1876055 as a duplicate, as that's got the paperwork filled out already.
[03:29] <ubot5> Launchpad bug 1877633 in libseccomp (Ubuntu Focal) "libseccomp 2.4.3 (and 2.4.2) is not correctly resolving (at least) the getrlimit syscall on arm64" [High,In progress] https://launchpad.net/bugs/1877633
[03:36] <RAOF> Hm. You're dropped db-properly-reset-attribute-state.patch in the eoan package, and added fix-python-module-install-path.patch without mentioning either in the changelog? Is the python module fix not required in focal? (I can see that the db- patch is included in the new upstream)
[03:39] <RAOF> Hm, not added, but added-to.
[04:04] <amurray> RAOF: ah good point re the 2 bug numbers - I can either copy the paperwork over to 1877633 since that is in the changelog or dupe it against 1876055 - do you have a preference?
[04:05] <RAOF> Well, all the packages before focal have both bugs in their chaneglogs :)
[04:06] <amurray> RAOF: the python module fix was due to the differences in the debian packaging between eoan/focal IIRC (I prepared these a couple weeks ago so am having to refresh my memory on the details) - but if I forgot to mention it in the changelog that's no good so I'll update it to add that
[04:07] <RAOF> I maybe have a slight preference for copying the content of 1876055 into 1877633, and then having details specific to how to test the backports in 1876055 (because focal only gets the new syscall, whereas previous series also get a backport)
[04:08] <amurray> RAOF: gah ok looks like I should go over the changelog's with a fine-toothed comb ;) - thanks for taking a look over them - I'll redo the changelogs and do the bug shuffling and updates as you suggest - cheers
[04:10] <RAOF> Ta. I've not noticed any other problems with them so far :)
[07:49] <sil2100> hm, wonder what's going on with the arm64 autopkgtest instances
[07:52] <cpaelzer> hi sil2100, in regard to +1 I've spotted a FTFBS on arm64/armhf in -proposed
[07:52] <cpaelzer> that started as an item I had anyway (one of my uploads) but I'd hope to track down the root cause - chances are that might break more things than just my upload
[07:52] <cpaelzer> and then I'd want to hold it back in proposed if possible
[07:53] <cpaelzer> I'll let you know once I found something
[07:53] <cpaelzer> sil2100: what do you mean in regard t arm64 autopkgtest ?
[07:53] <cpaelzer> the not uncommon network issues connecting to the archive, or something new?
[07:54] <sil2100> cpaelzer: which package FTBFS you have in mind?
[07:55] <sil2100> cpaelzer: as for the arm64 ADT runs, maybe I'm just imagining things but the arm64 queue is huge
[07:59] <cpaelzer> sil2100: my upload was src:spice, it was building fine end of last week
[07:59] <cpaelzer> so I have some hop ethat whatever broke it might still be in -proposed
[08:00] <cpaelzer> sil2100: the queue is even bigger on s390x which is more uncommon
[08:00] <cpaelzer> sometimes the builders get stuck and we ping cjwatson or wgrant to unstcuk them - let me check if it looks like that again ...
[08:00] <cpaelzer> oh wait
[08:00]  * cpaelzer needs to wakr up
[08:00] <cpaelzer> builders, but you are talking autopkgtest
[08:01] <wgrant> Scalingstack bos02 s390x was a bit sad 12h ago
[08:01] <wgrant> (but it's been fixed, and I've fixed the LP builders)
[08:01] <cpaelzer> ok, thanks for the info wgrant
[08:11] <cpaelzer> well active test numbers seem reasonable https://paste.ubuntu.com/p/vVb9bZh9dc/ so for now we can wait until it churns through its backlog
[08:18] <Laney> Yep, that's the deal :(
[08:18] <Laney> Bet you s390x finishes its queue before arm64
[08:19] <Laney> this would all be more pleasing if we weren't down one cloud region
[08:31] -queuebot:#ubuntu-release- New: accepted linux-signed-oem-osp1 [amd64] (bionic-proposed) [5.0.0-1054.59]
[08:31] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (bionic-proposed) [4.15.0-103.104]
[08:31] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [ppc64el] (xenial-proposed) [4.15.0-103.104~16.04.1]
[08:31] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (bionic-proposed) [4.15.0-103.104]
[08:31] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (xenial-proposed) [4.15.0-103.104~16.04.1]
[09:01] <cpaelzer> sil2100: my arm FTFBS debugging is a sad story (always works when trying to recreate)
[09:01] <sil2100> Ouch ;)
[09:01] <cpaelzer> sil2100: but I have found something else haunting grovy proposed migration that I want to resolve - but ping you to avoid doing it twice at the same time
[09:01] <sil2100> I'm looking into nfs-ganesha FTBFS, since it's needed for a mirco-transaction to complete
[09:02] <cpaelzer> azure-cli was synced the last week but some bits were missing (synced late), due to that the tests were broken and thereby failed for many other packages
[09:02] <cpaelzer> sil2100:  I have spotted 9 packages blocked by that
[09:02] <cpaelzer> Logan: has triggered that for knacc - but there are many more
[09:02] <cpaelzer> those I'll trigger now, they are not yet listed as retries in the test queue
[09:02] <sil2100> cpaelzer: ACK o/
[09:03] <sil2100> oh, and earlier I also easy-hinted yara, since the autohinter missed a package, so hopefully that will also migrate
[09:03] <Laney> not listed as retries> why?
[09:04] <cpaelzer> Laney: I just checked the autopkgtest queue and haven't seen them listed there
[09:04] <Laney> cpaelzer: oh, you mean nobody retried those already, I see
[09:04] <cpaelzer> yes
[09:04] <mwhudson> i assume there's no equivalent of rescoring for autopkgtest queues?
[09:04] <cpaelzer> I'd not want to put more onto the queue than needed
[09:04] <Laney> I thought you meant not lited as failure in excuses
[09:04] <cpaelzer> oh ok, no Laney I was not meaning that
[09:04] <Laney> mwhudson: nope, only the huge and not-huge queues (retries go into the latter)
[09:05] <Laney> I think rabbitmq does have some kind of concept of priority though
[09:05] <Laney> so if someone wanted to look into how to achieve that, we could
[09:05] <mwhudson> i guess i'll have to go to bed at a reasonable hour and see if the queue has drained by morning :)
[09:07] <Laney> bloomin perl uploads eh
[09:08] <cpaelzer> hmm, this might be better off runngin with all-proposed than listing 10 packages
[09:08] <cpaelzer> does one of you know if it will make all the packages that "were used" due to all-propsoed migrate - or would it only recognize those if listed as trigger
[09:08] <Laney> the triggers are not considered outside of the test run itself
[09:09] <Laney> i.e. all-proposed (or extra triggers) can make inconsistent things migrate
[09:09] <cpaelzer> I know that part, let me add more detail to my question ...
[09:10] <cpaelzer> I can essentially either do a) trigger=1,trigger=2,trigger=3,... or b) trigger=1,all-proposed=1; but I'm wondering if (b) will unblock 2 and 3 ...?
[09:10] <Laney> ok, I see, you need to add the triggers to have the test recorded against that item, yes
[09:10] <cpaelzer> ok, thanks for confirming
[09:10] <Laney> maybe use retry-autopkgtest-regressions
[09:11] <cpaelzer> can that combine multiple?
[09:11] <Laney> that usually tries to batch up things if it can
[09:11] <cpaelzer> I do as well, but I want to run the tests for the 8 stalled pkg's as one
[09:11] <Laney> yes, it does that
[09:11] <cpaelzer> oh, /me relooks for that again ...
[09:11] <Laney> well, run it, it just prints the URLs, so no harm if it's not what you want
[09:17] <cpaelzer> ok submitted, that should eventually help six/python-jmespath/javaproperties/python-tz
[09:17] <cpaelzer> I'll keep a tab open and recheck the results tomorow
[09:20] <cpaelzer> sil2100: the rebuild of my arm64/armhf builds on src:spice worked in the archive as well now
[09:20] <cpaelzer> which is fine for the PKG to migrate, but odd as nothing was changed
[09:21] <cpaelzer> unless we really have a three-phase issue of "working on thursday" - "broken on the weekend" - "good now"
[09:21] <cpaelzer> keep an eye out for odd arm64 fails and let me know, maybe we can detect a parrtern
[09:21] <cpaelzer> lol, "pattern" obviously
[10:06] -queuebot:#ubuntu-release- New binary: nfs-ganesha [s390x] (groovy-proposed/main) [3.2-2] (no packageset)
[10:07] -queuebot:#ubuntu-release- New binary: nfs-ganesha [amd64] (groovy-proposed/main) [3.2-2] (no packageset)
[10:07] -queuebot:#ubuntu-release- New binary: nfs-ganesha [ppc64el] (groovy-proposed/main) [3.2-2] (no packageset)
[10:12] -queuebot:#ubuntu-release- New binary: nfs-ganesha [arm64] (groovy-proposed/main) [3.2-2] (no packageset)
[10:13] -queuebot:#ubuntu-release- New binary: nfs-ganesha [armhf] (groovy-proposed/main) [3.2-2] (no packageset)
[10:24] <sil2100> cpaelzer: hah ;)
[10:42] <cpaelzer> cjwatson: for groovy https://code.launchpad.net/~paelzer/ubuntu/+source/openssh/+git/openssh/+merge/384814  is tested and ready to fix https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1876320 - my question to you - do you want to upload that to Debian and sync? Or shall I upload to Groovy as Ubuntu Delta for now?
[10:42] <ubot5> Ubuntu bug 1876320 in openssh (Ubuntu Focal) "Port parameter sshd_config is 22 AND whatever you specify" [Low,In progress]
[10:44] <cjwatson> cpaelzer: I'm in the middle of merging 8.3, so can't conveniently upload it just now.  Do what you like
[10:44] <cpaelzer> cjwatson: well, merging 8.3 will fix it as well - IIRC the fix is in there
[10:44] <cpaelzer> let me check to be sure
[10:44] <cjwatson> cpaelzer: No, it's not
[10:44] <cjwatson> I checked
[10:44] <cpaelzer> oh, ok
[10:44] <cjwatson> cpaelzer: Please can you file a Debian bug as a reminder for me to cherry-pick that?
[10:44] <cpaelzer> I'll upload as ubuntu Delta to groovy now
[10:45] <cpaelzer> cjwatson: I'll file you a Debian bug to pick it up at or after the 8.3 merge
[10:45] <cjwatson> (No need to attach a patch, just point to the upstream commit)
[10:45] <cjwatson> Thanks
[10:50] <RikMills> could someone no change rebuild libclass-xsaccessor-perl?
[10:50] <RikMills> anothee perl mini transition has made pkg-kde-tools uninstallable again
[10:53] <cpaelzer> cjwatson: filed as 962035 and linked from the LP bug so it can be found from both bug trackers
[10:56] <cpaelzer> RikMills: I can issue that no change rebuild if you want
[10:56] <cpaelzer> RikMills: nay other context I need to be aware of - dependencies, common test issues ... ?
[10:56] <RikMills> cpaelzer: would be appreciated :)
[10:57] <RikMills> cpaelzer: I don't think so. the last rebuild just on the main perl tests which are running now
[10:57] <RikMills> *just waited
[10:57] <cpaelzer> ok, for 5.30.3 then as I see
[10:57] <RikMills> cpaelzer: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962012
[10:57] <cpaelzer> I'll be queuing and tracking its build/migration
[10:57] <ubot5> Debian bug 962012 in release.debian.org "binnmus for perl mini-transition 5.30.3" [Normal,Open]
[10:58] <RikMills> there is that bug for the other bin nmu needed
[10:58] <RikMills> we can't sync those, so someone will have to rebuild those here soon as well
[11:24] -queuebot:#ubuntu-release- Unapproved: openblas (focal-proposed/universe) [0.3.8+ds-1 => 0.3.8+ds-1ubuntu0.20.04.1] (kubuntu)
[11:25] <cpaelzer> RikMills: perl 5.30.3 still isn't build on riscv
[11:25] <cpaelzer> RikMills: I think my rebase has to wait a bit
[11:25] <cpaelzer> sorry, "rebuild" not "rebase"
[11:30] <RikMills> cpaelzer: thanks for noticing!
[11:31] <cpaelzer> I have this and the other packages ready for no change rebuilds
[11:31] <RikMills> ty
[11:31] <cpaelzer> they seem not to be interlocked with each other and seem not to wait on anything else but perl
[11:31] <cpaelzer> I have the tab on the perl build open and will issue them once ready
[11:38] <cpaelzer> sil2100: all but the extra long queue architectures worked on azure-cli
[11:38] <cpaelzer> so that will unblock over night
[11:38] <cpaelzer> I'm shivering that I ask, but there is a lot of haskell in update-excuses - is anyone looking at that or has an understanding what we wait for?
[11:38] <cpaelzer> from far away it seems like a few FTFBS and a lot of dependency waits due to that
[12:28] <sil2100> Wimpress: hey! So I see ubuntu-mate has folder-color in its supported seed
[12:28] <sil2100> Wimpress: so I'm currently feeling trigger happy to remove that package, with the rationale of it no longer working as python-nautilus has been removed (with only the python3 bindings remaining)
[12:29] <cpaelzer> can I make reverse-depends / apt-cache rdepends / apt-rdepends (or any other tool) to only list me those packges depending on an (outdated) version. Like reverse-depends --release=groovy 'foo<1.2' ?
[12:29] <sil2100> Wimpress: I didn't see any development on this package since at least bionic
[12:29] <cpaelzer> all of these tools give me some unknown package error if I try it like that
[12:30] <cpaelzer> I use these tools often looking forward, butnow I need to look backwards to see what still needs to be touched depending on an old package of a trasnition
[12:30] <cpaelzer> I'm sure this exists, yet how exactly is still hiding from me
[12:30] <sil2100> cpaelzer: hm, I must say nothing comes into my mind so far, usually when I need to check for these things it's when binary packages bump their soversion, so I usually have a good overview doing reverse-depends libfoo3 (when the new one is libfoo4)
[12:31] <sil2100> Wimpress: any objections for removing it for now? I guess it can be reuploaded once it has python3 support?
[12:32] <cpaelzer> sil2100: yeah I know that with versioned source names
[12:32] <Wimpress> sil2100: I am planning to update it this cycle.
[12:32] <cpaelzer> sil2100: but here it is just a hard dep <<version
[12:32] <cpaelzer> and the new pacakhe now is >=version, so I see a lot of dependency issues
[12:32] <cpaelzer> rebuilds will fix it and I "manuall" detected a few, but there must be a programatic way to find all candidates I need to touch ...
[12:34] <sil2100> Wimpress: I suppose somewhere later in the cycle, right?
[12:37] <sil2100> hm, actually, maybe I'll instead just try it with python3
[12:55] <sil2100> Wimpress: ok, nevermind! I've got this
[13:52] <cpaelzer> sil2100: I have rechecked the perl dependenceis for 5.30.3 - there are a bunch which have alternate deps that make them succeed and the four already identified packages
[13:52] <cpaelzer> sil2100: it now completed build on riscv64 and was published, I'll upload the no change rebuilds
[13:53] <cpaelzer> as mentioned before once they all have passed we need to re-trigger most tests of perl with them
[13:53] <cpaelzer> I'll take a look at that either later today or tomorrow then
[13:53] <cpaelzer> sil2100: and for the version-reverse-dep I now have a three line command piping things together
[13:54] <cpaelzer> everyone that knows the right way will shiver (and hopefully let me know about a better way), but this works https://paste.ubuntu.com/p/mPQKPkxxPc/
[13:55] <cpaelzer> RikMills: ^^ FYI since you asked for these perl bits
[13:56] <RikMills> cpaelzer: aha. thanks!
[13:58] <cpaelzer> and while uploading LocutusOfBorg and NikoTyni already beat me pushing that :-)
[13:58] <cpaelzer> anyway it is in progress
[13:59] <sil2100> cpaelzer: ooh!
[14:00] <sil2100> In the meantime I hopefully unblocked nautilus-python, but I guess we'll only start seeing results once the arm64 and s390x tests complete
[14:03] <RikMills> cpaelzer: right. it was going to be picked up soonish anyway, and without the rebuilds lintian and perhaps more cannot be installed in proposed
[14:04] <RikMills> thankyou to LocutusOfBorg and NikiTyni :)
[14:05] <RikMills> I was just trying to make some progress merging 80+ KDE things from debian earlier, and was sad to seed they could not build
[14:05] <RikMills> *to see
[14:29] <Laney> what have security done to the autopkgtest queues 😱😱😱
[14:33] <RikMills> omfg
[14:35] <RikMills> maybe I will come back to see how migrations are going in say, a week!
[14:37] -queuebot:#ubuntu-release- New binary: nfs-ganesha [riscv64] (groovy-proposed/main) [3.2-2] (no packageset)
[14:45] <mdeslaur> huh? what'd I do?
[14:55] <Laney> oh just perl updates to all the things
[14:55] <apw> mdeslaur, did you patch perl ?
[14:55] <mdeslaur> oh, hah, yeah
[14:55] <mdeslaur> do we need more hamsters?
[14:56] <mdeslaur> oh wow, that's a lot of tests
[14:56] <apw> ouch ... if this is right there are 79k jobs on the queues
[14:56] <mdeslaur> you can call me 'killer' from now on
[14:57] <mdeslaur> can you cancel them? though, I'd like for the xenial ones to run, but the others can be cancelled
[14:58] <Laney> if you're not interested, sure
[14:58] <mdeslaur> I'm only interested in xenial
[14:59] <Laney> okey
[14:59] <Laney> will do after meetings
[15:02] <mdeslaur> thanks Laney
[15:17] -queuebot:#ubuntu-release- Unapproved: nautilus (focal-proposed/main) [1:3.36.2-0ubuntu1 => 1:3.36.3-0ubuntu1] (ubuntu-desktop)
[15:19] -queuebot:#ubuntu-release- Unapproved: rejected nautilus [source] (focal-proposed) [1:3.36.3-0ubuntu1]
[15:19] -queuebot:#ubuntu-release- Unapproved: nautilus (focal-proposed/main) [1:3.36.2-0ubuntu1 => 1:3.36.3-0ubuntu1] (ubuntu-desktop)
[15:48] -queuebot:#ubuntu-release- Unapproved: accepted gummi [source] (focal-proposed) [0.8.1-1ubuntu0.20.04.1]
[15:57]  * Laney terminates
[16:50] <LocutusOfBorg> cpaelzer, but I didn't touch any perl bit today, did you upload something on my behalf? thanks :D
[17:24] <ginggs> would someone please accept slepc and petsc4py from groovy new queue?
[19:24] -queuebot:#ubuntu-release- Unapproved: cloud-init (focal-proposed/main) [20.1-10-g71af48df-0ubuntu5 => 20.2-45-g5f7825e2-0ubuntu1~20.04.1] (core, edubuntu, ubuntu-cloud)
[19:41] <cpaelzer> LocutusOfBorg: hmm, maybe the no change rebuild inserted te last uploader instead of me - that would be odd
[19:42] <cpaelzer> LocutusOfBorg: but if you didn't touch it it is the noly explanation I can come up with
[19:42] <cpaelzer> indeed, the changes file have taken over the last uploader, dear dch what did you do
[19:43] <cpaelzer> sorry then LocutusOfBorg, but since I'll track and push it anyway you are good
[19:43] <cpaelzer> ignore it if you get and further pings on it
[19:49] <LocutusOfBorg> no problem cpaelzer :) I just have been thanked for doing it over telegram on your behalf :D this is why I went on the web page and saw your name on signoff :)
[19:52] -queuebot:#ubuntu-release- Unapproved: fwupd (groovy-proposed/main) [1.3.9-4ubuntu1 => 1.3.9-4ubuntu1] (core)
[19:57] -queuebot:#ubuntu-release- Unapproved: fwupd (groovy-proposed/main) [1.3.9-4ubuntu1 => 1.3.9-4ubuntu1] (core)
[19:57] -queuebot:#ubuntu-release- Unapproved: fwupd (groovy-proposed/main) [1.3.9-4ubuntu1 => 1.3.9-4ubuntu1] (core)
[21:03] <vorlon> xnox: arch being tested for> DEB_HOST_ARCH for the cross-arch case?
[21:03] <xnox> Yeah, something like that
[21:04] -queuebot:#ubuntu-release- New: accepted nfs-ganesha [armhf] (groovy-proposed) [3.2-2]
[21:04] -queuebot:#ubuntu-release- New: accepted nfs-ganesha [riscv64] (groovy-proposed) [3.2-2]
[21:04] -queuebot:#ubuntu-release- New: accepted libplacebo [arm64] (groovy-proposed) [1.29.1+dfsg1-2]
[21:04] -queuebot:#ubuntu-release- New: accepted libplacebo [i386] (groovy-proposed) [1.29.1+dfsg1-2]
[21:04] -queuebot:#ubuntu-release- New: accepted libplacebo [riscv64] (groovy-proposed) [1.29.1+dfsg1-2]
[21:04] -queuebot:#ubuntu-release- New: accepted nfs-ganesha [amd64] (groovy-proposed) [3.2-2]
[21:04] -queuebot:#ubuntu-release- New: accepted nfs-ganesha [ppc64el] (groovy-proposed) [3.2-2]
[21:05] -queuebot:#ubuntu-release- New: accepted libplacebo [armhf] (groovy-proposed) [1.29.1+dfsg1-2]
[21:05] -queuebot:#ubuntu-release- New: accepted libplacebo [s390x] (groovy-proposed) [1.29.1+dfsg1-2]
[21:05] -queuebot:#ubuntu-release- New: accepted nfs-ganesha [s390x] (groovy-proposed) [3.2-2]
[21:05] -queuebot:#ubuntu-release- New: accepted libplacebo [ppc64el] (groovy-proposed) [1.29.1+dfsg1-2]
[21:05] -queuebot:#ubuntu-release- New: accepted nfs-ganesha [arm64] (groovy-proposed) [3.2-2]
[21:05] -queuebot:#ubuntu-release- New: accepted libplacebo [amd64] (groovy-proposed) [1.29.1+dfsg1-2]
[21:05] -queuebot:#ubuntu-release- New: accepted openbabel [arm64] (groovy-proposed) [3.1.1+dfsg-2]
[21:05] -queuebot:#ubuntu-release- New: accepted openbabel [ppc64el] (groovy-proposed) [3.1.1+dfsg-2]
[21:05] -queuebot:#ubuntu-release- New: accepted openbabel [s390x] (groovy-proposed) [3.1.1+dfsg-2]
[21:05] -queuebot:#ubuntu-release- New: accepted ordered-map [s390x] (groovy-proposed) [0.8.1-2]
[21:05] -queuebot:#ubuntu-release- New: accepted openbabel [amd64] (groovy-proposed) [3.1.1+dfsg-2]
[21:05] -queuebot:#ubuntu-release- New: accepted openbabel [riscv64] (groovy-proposed) [3.1.1+dfsg-2]
[21:05] -queuebot:#ubuntu-release- New: accepted openbabel [armhf] (groovy-proposed) [3.1.1+dfsg-2]
[21:05] -queuebot:#ubuntu-release- New: accepted ordered-map [riscv64] (groovy-proposed) [0.8.1-2]
[21:05] -queuebot:#ubuntu-release- New: accepted ordered-map [amd64] (groovy-proposed) [0.8.1-2]
[21:05] -queuebot:#ubuntu-release- New: accepted ordered-map [armhf] (groovy-proposed) [0.8.1-2]
[21:05] -queuebot:#ubuntu-release- New: accepted petsc4py [riscv64] (groovy-proposed) [3.13.0-2]
[21:05] -queuebot:#ubuntu-release- New: accepted slepc [armhf] (groovy-proposed) [3.13.2+dfsg1-1]
[21:05] -queuebot:#ubuntu-release- New: accepted slepc [s390x] (groovy-proposed) [3.13.2+dfsg1-1]
[21:06] -queuebot:#ubuntu-release- New: accepted ordered-map [arm64] (groovy-proposed) [0.8.1-2]
[21:06] -queuebot:#ubuntu-release- New: accepted slepc [arm64] (groovy-proposed) [3.13.2+dfsg1-1]
[21:06] -queuebot:#ubuntu-release- New: accepted ordered-map [ppc64el] (groovy-proposed) [0.8.1-2]
[21:06] -queuebot:#ubuntu-release- New: accepted slepc [riscv64] (groovy-proposed) [3.13.2+dfsg1-1]
[21:06] -queuebot:#ubuntu-release- New: accepted paraglob [armhf] (groovy-proposed) [0.4.1-1]
[21:06] -queuebot:#ubuntu-release- New: accepted paraglob [s390x] (groovy-proposed) [0.4.1-1]
[21:06] -queuebot:#ubuntu-release- New: accepted petsc4py [armhf] (groovy-proposed) [3.13.0-2]
[21:06] -queuebot:#ubuntu-release- New: accepted petsc4py [s390x] (groovy-proposed) [3.13.0-2]
[21:06] -queuebot:#ubuntu-release- New: accepted slepc [ppc64el] (groovy-proposed) [3.13.2+dfsg1-1]
[21:06] -queuebot:#ubuntu-release- New: accepted paraglob [riscv64] (groovy-proposed) [0.4.1-1]
[21:06] -queuebot:#ubuntu-release- New: accepted petsc4py [ppc64el] (groovy-proposed) [3.13.0-2]
[21:06] -queuebot:#ubuntu-release- New: accepted petsc4py [arm64] (groovy-proposed) [3.13.0-2]
[21:06] -queuebot:#ubuntu-release- New: accepted slepc [amd64] (groovy-proposed) [3.13.2+dfsg1-1]
[21:06] -queuebot:#ubuntu-release- New: accepted paraglob [amd64] (groovy-proposed) [0.4.1-1]
[21:07] -queuebot:#ubuntu-release- New: accepted paraglob [ppc64el] (groovy-proposed) [0.4.1-1]
[21:07] -queuebot:#ubuntu-release- New: accepted paraglob [arm64] (groovy-proposed) [0.4.1-1]
[21:07] -queuebot:#ubuntu-release- New: accepted petsc4py [amd64] (groovy-proposed) [3.13.0-2]
[21:17] <vorlon> xnox: well, specifically that.  For cross-arch autopkgtests, DEB_HOST_ARCH is set.
[21:21] <xnox> Oh
[21:21] <xnox> Ok
[21:42] -queuebot:#ubuntu-release- Unapproved: gtk+3.0 (focal-proposed/main) [3.24.18-1ubuntu1 => 3.24.20-0ubuntu1] (i386-whitelist, ubuntu-desktop)
[21:48] <Eickmeyer> Hi release team. I just did a syncpackage for ardour, but it looks like it's going to get held-up in proposed for FTBFS on ppc64el. Speaking to the devs, PPC support is WIP and might actually be dropped.
[21:49] <Eickmeyer> I informed the Debian Multimedia Team about the issue, but in the meantime can we get a hint on ppc64el for Ardour? I'd appreciate it. :)
[21:49] <tumbleweed> the solution to that isn't a hint, but a binary removal of the old ppc64el build
[21:50] <Eickmeyer> Or that. ^
[21:50] <tumbleweed> ubuntu-archive: ^^
[21:51] <Eickmeyer> tumbleweed: Thanks. :)
[21:52] <Eickmeyer> In fact, the next major release *will* drop ppc, just confirmed.
[22:09] <mwhudson> strange to see a big autopkgtest queue on s390x, infrastructure issues?
[22:10] <xnox> mwhudson:  yes
[22:10] <xnox> and catching up
[22:10] <xnox> plus perl security update on all series
[22:10] <mwhudson> ah yes that would be why there are 1000s of tests waiting on xenial?
[22:11] <xnox> Yeah
[22:11] <xnox> I think we were wat 50,000+ tests this morning.
[22:13] -queuebot:#ubuntu-release- Unapproved: rejected cloud-init [source] (focal-proposed) [20.2-38-g8377897b-0ubuntu1~20.04.1]
[22:13] <blackboxsw> thx, eoan bionic and xenial still in progress :/
[22:13] <blackboxsw> will probably wrap those up and ping sru vanguard tomorrow
[22:18] <xnox> mwhudson:  publishing
[22:19] <xnox> bah wrong channel
[22:19] -queuebot:#ubuntu-release- Unapproved: accepted curtin [source] (focal-proposed) [20.1-2-g42a9667f-0ubuntu1~20.04.1]
[22:26] -queuebot:#ubuntu-release- Unapproved: accepted curtin [source] (bionic-proposed) [20.1-2-g42a9667f-0ubuntu1~18.04.1]
[22:28] -queuebot:#ubuntu-release- Unapproved: accepted curtin [source] (xenial-proposed) [20.1-2-g42a9667f-0ubuntu1~16.04.1]
[22:33] -queuebot:#ubuntu-release- Unapproved: accepted libvirt [source] (focal-proposed) [6.0.0-0ubuntu8.1]
[22:45] -queuebot:#ubuntu-release- Unapproved: accepted qemu [source] (focal-proposed) [1:4.2-3ubuntu6.2]
[22:49] -queuebot:#ubuntu-release- Unapproved: accepted qemu [source] (eoan-proposed) [1:4.0+dfsg-0ubuntu9.7]
[22:54] -queuebot:#ubuntu-release- Unapproved: accepted qemu [source] (bionic-proposed) [1:2.11+dfsg-1ubuntu7.27]
[23:03] -queuebot:#ubuntu-release- New binary: slepc4py [amd64] (groovy-proposed/universe) [3.13.0-2] (no packageset)
[23:03] -queuebot:#ubuntu-release- New binary: slepc4py [s390x] (groovy-proposed/universe) [3.13.0-2] (no packageset)
[23:05] -queuebot:#ubuntu-release- New binary: slepc4py [ppc64el] (groovy-proposed/universe) [3.13.0-2] (no packageset)
[23:06] -queuebot:#ubuntu-release- New binary: slepc4py [armhf] (groovy-proposed/universe) [3.13.0-2] (no packageset)
[23:11] -queuebot:#ubuntu-release- New binary: slepc4py [arm64] (groovy-proposed/universe) [3.13.0-2] (no packageset)
[23:32] <vorlon> Eickmeyer: ardour removed from ppc64el and riscv64; upstream's code clearly has a bug here and I'm further skeptical of the entire per-architecture thing they're implementing here, but it's a desktop app and ppc64el isn't a desktop arch, so
[23:47] -queuebot:#ubuntu-release- New binary: slepc4py [riscv64] (groovy-proposed/universe) [3.13.0-2] (no packageset)
[23:59] <Eickmeyer> vorlon: Thanks!