[07:27] <icey> hey bdmurray - on the topic of +1, would you recommend I start with looking at packages in update_excuses to see if I can propose something to resolve the issues?
[07:31] <icey> bdmurray: ah - I suspect you'll be online in several hours :-P
[07:38] <seb128> xnox, thank you for unblocking gtk! :)
[07:39] <seb128> icey, hey, are you on +1 rotation and is that your first time? if so maybe start reading https://wiki.ubuntu.com/PlusOneMaintenanceTeam
[07:39] <icey> seb128: indeed - doing today and tomorrow,  and then again week after next :-)
[07:42] <seb128> icey, ah, enjoy! to reply to your question usually https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html is the main place where to find +1 work indeed
[07:42] <seb128> icey, check for things that fail to build or test failures there, ideally for components that are not owned by a team (https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html tell you that)
[07:43] <seb128> icey, you might also want to read the recent +1 reports on https://lists.ubuntu.com/archives/ubuntu-devel/2021-June/date.html , it gives some indication of the work being done by other, which would help to get a sense of what +1 maintainers usually do and also avoid redoing investigation work already done by others
[07:44] <icey> seb128: indeed - my first step was looking through my recent emails on the list :)
[07:48] <seb128> icey, random one you could work on from the recent items, https://launchpad.net/ubuntu/+source/pylint/2.7.2-3
[07:48] <seb128> seems it builds fine in Debian and is autosync so probably needs debugging for Ubuntu
[07:49] <Unit193> (Added him as a patch pilot)
[07:50] <seb128> Unit193, +1 != patch pilot though?
[07:51] <Unit193> Aha!
[07:54] <seb128> icey, another one that might be suited for you :p https://autopkgtest.ubuntu.com/packages/s/senlin/impish/amd64
[07:55] <seb128> icey, seems like the recent upload is failing tests
[07:55] <Unit193> (I kind of thought that was a replaced name for a while now....)
[07:55] <seb128> icey, and some other tests failure on https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#dulwich , randomly picked
[07:56] <seb128> Unit193, https://wiki.ubuntu.com/PlusOneMaintenanceTeam
[07:56] <seb128> Unit193, +1 is mostly working on archive issues
[08:03] <icey> seb128: I'll take those three for now then :)
[08:03] <seb128> great :)
[08:03] <icey> seb128: would you be open to helpping me with sponsoring things?
[08:03] <seb128> icey, sure
[08:04] <icey> thanks!
[08:06] <seb128> np!
[08:27] <icey> ah the joy of Python moving forward, I can reproduce that pylint build / test failure on the version accepted into impish too :-D
[13:31] <icey> the recent dulwich autopkgtest failure seems to be the result of a breezy ftbfs (#1932313), and I noticed that there's a somewhat old RM bug for breezy: #1801945
[13:32] <icey> and links, since no bot? https://pad.lv/1932313 and https://pad.lv/1801945 respectively
[13:32] <icey> or just a better format :-P
[14:55] <bdmurray> icey: fwiw I'm about now.
[14:55] <icey> bdmurray: morning!
[20:34] <jawn-smith> Is any core dev available to restart a failed package build for golang-1.16 on riscv64?
[20:34] <jawn-smith> https://launchpad.net/ubuntu/+source/golang-1.16/1.16.5-1ubuntu1/+build/21698044
[20:35] <ogra> jawn-smith, done
[20:35] <jawn-smith> thanks ogra!
[21:21] <jawn-smith> Can any core dev restart this autopkgtest as well? https://autopkgtest.ubuntu.com/request.cgi?release=impish&arch=arm64&package=opensaml&trigger=glibc/2.33-0ubuntu8
[21:21] <jawn-smith> it has two failures in different places, and is running fine on my local arm64 machine
[21:21] <jawn-smith> so I think it's just a flakey test
[21:25] <bryceh> jawn-smith, done
[21:26] <jawn-smith> thanks!
[21:40] <jawn-smith> well, that might be an actual failure. Thanks for the restart, back to the drawing board
[22:21] <bdmurray> jawn-smith: how much memory does your local arm64 machine have?
[22:21] <jawn-smith> more than 1
[22:21] <jawn-smith> 8GB
[22:21] <sarnold> two, two memory, ah ah ah
[22:22] <jawn-smith> which I thought might likely be the problem so I'm running in a memory limited container now