[10:06] <xnox> apw, sforshee:  i think i have sponsored them all, a while ago. But we were in point release freeze. Let me see what's going on with them all again.
[12:21] <sforshee> xnox: these are new since the ones you sponsored, these are from just a few days ago
[13:17] <xnox> sforshee:  oh, ok.
[13:19] <xnox> sforshee:  will check and do them.
[13:19] <xnox> must be extra careful with community package sponsoring =)))))))
[13:21] <sforshee> :-P
[13:29] <xnox> sforshee:  so no xenial and trusty backports. I guess i should check if we should be doing them or not.
[15:21] <sforshee> xnox: I think so. It doesn't seem like anything happened with the ones I did last time, so I didn't bother this time. But I'm happy to do updates if they will actually be used
[15:23] <xnox> sforshee:  well, i thought i did submit them to esm proposed, but not sure if they got released. let me track down as to what happened with the last lot of them.
[17:20] <sem2peie> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939937
[17:20] <sem2peie> i am supposed to test some kernel, can someone also tell me which one is meant exactly?
[17:26] <sem2peie> focal-proposed offers me as update 5.11.0.34.36 , is this also the kernel that is meant or 5.13.0-oem ?
[17:34] <jawn-smith> Is any core dev available to restart a package build? https://launchpad.net/ubuntu/+archive/test-rebuild-20210805-impish/+build/21865510
[17:37] <bdmurray> jawn-smith: looking
[17:38] <jawn-smith> thanks bdmurray. It's one of the packages that failed with Go 1.17
[17:38] <bdmurray> jawn-smith: that's actually not something any core-dev can do
[17:38] <jawn-smith> oh I see, is that an AA thing?
[17:39] <bdmurray> no, I think its a very small set of people - doko for sure and maybe vorlon
[17:39] <bdmurray> what are you trying to accomplish though?
[17:40] <jawn-smith> the package failed when built against Go 1.17. I think it was a fluke, but wanted to see if it still failed on a second try because that would point to differences between the LP builders and my sbuild environment
[17:41] <jawn-smith> If that is not appropriate I'm happy to just wait for the next test-rebuild
[17:41] <bdmurray> jawn-smith: could you accomplish what you want using a PPA?
[17:41] <jawn-smith> yes, I was just thinking that
[19:51] <bryceh> bdmurray, vorlon do you know if foundations or another team has backported openjdk-11 to bionic in a PPA?
[19:54] <bryceh> ah looks like maybe https://launchpad.net/~openjdk-r/+archive/ubuntu/ppa/+packages ?
[19:54] <bryceh> sorry I meant openjdk-17
[20:01] <bdmurray> that looks right to me but I'm not certian
[20:01] <bdmurray> certain
[20:03] <bryceh> bdmurray, hopefully it's fine, this should save me a huge amount of time :-)
[20:15] <jawn-smith> Can any core dev restart
[20:15] <jawn-smith> https://autopkgtest.ubuntu.com/request.cgi?release=impish&arch=armhf&package=openssh&trigger=openssh/1%3A8.4p1-6ubuntu1&trigger=chiark-tcl/1.3.4ubuntu3&trigger=cmake-extras/1.5-7&trigger=dateparser/1.0.0-1&trigger=gem2deb/1.4&trigger=glib2.0/2.68.4-1&trigger=glibc/2.34-0ubuntu1&trigger=gnome-desktop3/40.2-1ubuntu1&trigger=grep/3.6-1&trigger=gtk4/4.4.0%2Bds1-3&trigger=ipolish/20210105-1&trigge
[20:15] <jawn-smith> r=link-grammar/5.8.1-1&trigger=natsort/7.1.0-1&trigger=openconnect/8.10-2build1&trigger=orafce/3.14.0-1&trigger=osinfo-db/0.20210809-1&trigger=pandas/1.1.5%2Bdfsg-2&trigger=pango1.0/1.48.9%2Bds1-1&trigger=pgpool2/4.1.4-3&trigger=php-shellcommand/1.6.3-1&trigger=php-twig/3.3.2-1ubuntu3&trigger=postgresql-13/13.4-1&trigger=postgresql-common/226&trigger=postgresql-multicorn/1.4.0-3&trigger=repro
[20:15] <jawn-smith> test/0.7.16&trigger=rows/0.4.1-3&trigger=snapd/2.51.1%2B21.10&trigger=symfony/5.2.6%2Bdfsg-1ubuntu7&trigger=systemd/248.3-1ubuntu5&trigger=tracker/3.1.1-2&trigger=vis/0.7-2
[20:15] <bryceh> jawn-smith, sure on it
[20:15] <jawn-smith> please and thank you. Oof that separated into 3 messages
[20:16] <jawn-smith> bryceh thanks! the armhf tests did fail but it doesn't seem to be related to dep8
[20:16] <bryceh> You submitted an invalid request: gtk4/4.4.0+ds1-3 is not published in impish
[20:17] <jawn-smith> and I've re-ran them locally numerous times.
[20:17] <jawn-smith> That's probably an issue with IRC splitting the link. It's the most recent failure on https://autopkgtest.ubuntu.com/packages/o/openssh/impish/armhf
[20:18] <jawn-smith> Oh actually looks like it's now ds1-3build1
[20:18] <jawn-smith> for gtk4
[20:18] <bryceh> gotcha, but nope the link on the page fails too.  More likely it's a newer gtk4 in -proposed
[20:19] <jawn-smith> Yeah that's it
[20:19] <bryceh> also systemd 248.3-1ubuntu6
[20:20] <bryceh> okie that went in
[20:20] <jawn-smith> great, thanks so much!
[20:23] <bryceh> jawn-smith, btw in case its of any interest I have a script https://code.launchpad.net/~bryce/+git/excuses-kicker that generates the retriggers for a package recalculated with what's in -proposed, using a download of the autopkgtest.db
[20:23] <bryceh> (if you run into this situation very often.  I find it handy when doing +1 maintenance.)
[20:24] <jawn-smith> That's great, thanks! I've got a +1 shift coming up here in a couple weeks
[20:25] <bdmurray> I wonder if you really needed to include all those triggers
[20:26] <bryceh> bdmurray, maybe not, but it doesn't hurt in practice since the buildd will just satisfy from -release instead of -proposed afaict
[20:26] <jawn-smith> I was thinking about that, and while I thought I likely didn't need them all I had just run the test 3 times against all of proposed
[20:26] <jawn-smith> locally that is
[20:27] <jawn-smith> I suppose "against all of proposed" is poor phrasing. What I meant is: with --apt-pocket=proposed
[20:27] <bryceh> fwiw, excuses-kicker will omit the ones already satisfied in the links it generates, but in my experience overspecifying things doesn't seem to cause extra build times or anything.