[00:44] <xnox> cjwatson:  i like the 5.8 kernel!
[00:45] <xnox> however seeing odd things already
[00:45] <xnox> i.e. dh_clean: error: unlink clean-7.4-stamp failed: Invalid argument
[00:45] <xnox> i beg your pardon dh_clean?! =) but laters
[00:47] <xnox> https://launchpadlibrarian.net/523389726/buildlog_ubuntu-hirsute-riscv64.xz-utils_5.2.5-1.0build1_BUILDING.txt.gz
[00:47] <xnox> hm
[00:47] <xnox> find: cannot delete ‘./src/liblzma/api/Makefile.in’: Invalid argument
[00:50] <xnox> oh
[00:50] <xnox> it might be me!
[03:29] <slingamn> i just got a change merged into apport that removes its dependency on python3-requests: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1903605
[03:30] <slingamn> i think that removes the hirsute base system's dependency on python3-requests, but i'm not sure how to check
[06:53] <oSoMoN> good morning
[06:53] <oSoMoN> https://people.canonical.com/~ubuntu-archive/proposed-migration/focal/update_excuses.html hasn't been re-generated in a week, is there something broken there?
[06:58] <RAOF> oSoMoN: I think I saw L aney and x nox lalking about that earlier today?
[06:59] <RAOF> oSoMoNS: Ah, yes. This morning, in #ubuntu-devel.
[07:00]  * oSoMoN checks the logs
[07:01] <seb128> oSoMoN, https://irclogs.ubuntu.com/2021/02/16/%23ubuntu-release.html#t18:50 but no reply afaik
[07:03] <RAOF> Huh.
[07:03] <RAOF> Why is wlcs stuck in hirsute-proposed? It doesn't show up on update_excuses?
[07:04] <seb128> RAOF, https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#wlcs ?
[07:04] <seb128> autopkgtest for mir/1.7.1-0ubuntu7: arm64: Regression ♻ , armhf: Regression ♻ , i386: Ignored failure, ppc64el: Regression ♻ , s390x: No test results
[07:04] <seb128> autopkgtest for mir/2.2.0-0ubuntu2: amd64: Regression ♻
[07:05] <RAOF> Hah. Did I not finish waiting for the page to fully load before searching for “wlcs” 🤔
[07:05] <oSoMoN> seb128, ack thanks, let's ping la_ney again when he gets online
[07:06] <seb128> RAOF, right, that page has enough content that loading takes a bit :-)
[07:12] <RAOF> Aaaaaaah. The new Mir release I'm preparing to upload should let it through!
[08:50] <cjwatson> xnox: I'm on leave today.  wgrant may be around, but if it turns out not to be a problem on our side then all the better :)
[09:08] <juliank> andrewsh: I actually read the Debian bug on wpa and session-ticket now, and actually upstream disabled session tickets itself too, in a different place, so I'll just sync it
[09:09] <juliank> One delta less
[09:09] <andrewsh> juliank: cool, thanks!
[09:12] <oSoMoN> Laney, https://people.canonical.com/~ubuntu-archive/proposed-migration/focal/update_excuses.html hasn't been re-generated in a week, is there something broken there?
[09:13] <Laney> oSoMoN: sounds likely, you can see the logs under https://people.canonical.com/~ubuntu-archive/proposed-migration/log/focal/
[09:14] <Laney> i'll look in a bit
[09:15] <seb128> error: branch 'focal' not found.
[09:15] <seb128> fun
[09:16] <seb128> that's not the error though
[09:18] <juliank> E: [2021-02-17T09:00:50+0000] - inconsistency found (end): binary snapd-xdg-open from source snapd-xdg-open not in binaries_t[riscv64]
[09:18] <juliank> leading to AssertionError: inconsistencies found in target suite
[09:18] <juliank> in https://people.canonical.com/~ubuntu-archive/proposed-migration/log/focal/2021-02-17/08:08:22.log
[09:20] <juliank> it should be in there - there are riscv64 debs
[09:36] <Laney> ok let's see now
[09:58] <didrocks> mwhudson: hey, is there the plan to switch to 1.16 by default now that it’s released and in proposed?
[09:58]  * didrocks would like to upload some packages using //go:embedeed
[10:32] <TJ-> Do we have a tool that can efficiently and quickly compare package dependency versions between releases (to determine if a package could be backported) ? I'm investigating if it'd be feasible to backport network-manager{,-gnome} from 21.04 to 20.04 to take advantage of nm-connection-editor's support for wireguard tunnels
[10:37] <doko> didrocks: see the release schedule for the planned changes. apparently we anticpated the upstream release a bit earlier
[11:22] <rbasak> xnox: bug 1915878 hit the technical-board@ ML moderation queue. Is this intentional, or an accident?
[11:22] <rbasak> I'm happy to let it through if that's what you want, but I think maybe it got there indirectly and you're not actually trying to raise it with the TB? In which case I might as well discard it.
[11:35] <Laney> oSoMoN: I removed some out of date snapd binaries, hopefully that will work around it
[11:36] <Laney> thanks for reporting
[11:38] <didrocks> doko: yeah, it’s usually start of february
[11:39] <didrocks> doko: surprised that golang 1.16 by default was set in January, Go 1.16 was always planned to be early February
[11:57] <xnox> rbasak:  i do not know how or why that hit tb moderation queue.
[11:57] <xnox> rbasak:  i only simply opended the bug report ah
[11:57] <xnox> rbasak:  reject
[11:57] <xnox> rbasak:  i meant to subscribe ~ubuntu-archive, not ~ubuntu-drivers
[11:58] <xnox> rbasak:  that's just an AA thing, not ~ubuntu-drivers thing.
[11:58] <xnox> but TB comments on package removals are always welcomed =)
[12:11] <slyon> Hey ginggs! I'm currently looking into the proposed-migration of some R packages (like r-bioc-delayedarray). Many autopkgtests fail because of "namespace ‘Matrix’ 1.2-18 is already loaded, but >= 1.3.2 is required". You uploaded rmatrix 1.3-2+really1.2-18-0ubuntu1 recently to fix a s390x autopkgtest failure...
[12:12] <slyon> I think we need to upgrade rmatrix again to unblock all those R packages, like r-bioc-delayedarray, r-bioc-matrixgenerics, r-cran-matrixstats, r-bioc-beachmat, r-bioc-summarizedexperiment, r-bioc-hdf5array, ...
[12:12] <slyon> Do you think we can find another fix for that s390x failure?
[12:12] <ginggs> yeah, and the whole pile would have migrated, except new uploads came along :(
[12:14] <slyon> damn... would you be fine with me upgrading rmatrix again? Or would that break other packages you're working on?
[12:15] <ginggs> slyon: upstream rmatrix are finally looking at it, see debian bug #980809 - so i'm hoping for a new rmatrix soon and we can sync
[12:16] <siretart> Any advise on getting golang packages migrated? It seems an awful lo tof them are waiting for glibc to migrate for quite a while...
[12:16] <siretart> I've received a couple of nag emails about my uploads being stuck in proposed
[12:16] <ginggs> but do go ahead with a rmatrix 1.3-2+really1.3-2xxx if you want, i don't think you can break anything that isn't already broken :)
[12:17] <slyon> ginggs: alright, so let's wait a bit more. I'll create an update-excuse bug for the affected packages then
[12:18] <rbasak> xnox: thanks. I'll discard to save you getting more spam. I guess it's because the TB is an admin of ~ubuntu-drivers?
[12:18] <ginggs> slyon: i think rebuilding the affected packages against rmatrix 1.2 is an option, but i think a waste of our time
[12:19] <xnox> rbasak:  something like that.
[12:26] <slyon> ACK
[12:27] <Laney> siretart: loads of things are backed up versus glibc at the minute, there's not a lot you can do but it will hopefully be unblocked soon
[12:28] <siretart> Laney: thanks for confirming!
[14:24] <oSoMoN> Laney, looks like the focal report was correctly generated, thanks!
[14:48] <Laney> \o\
[14:48] <Laney> /o/
[14:58] <rbasak> cjwatson: o/ just checking you still have my changes file proposal in your queue please?
[15:56] <slingamn> can anyone advise on how to confirm that python3-requests is no longer a dependency of the hirsute base system?
[16:49] <rbasak> slingamn: https://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.hirsute/rdepends/requests/python3-requests
[16:49] <rbasak> That's the reverse dependency tree for it in hirsute
[16:50] <rbasak> cloud-init does still depend on it, so that suggests to me that you would see it on a base Ubuntu Server install.
[16:51] <rbasak> ssh-import-id too, though that should go away as soon as my upload from yesterday lands
[16:52] <slingamn> rbasak: thanks! so if you remove cloud-init and autoremove, it'll go away, which is what i wanted
[16:54] <rbasak> slingamn: I'm not entirely sure though - easier to check when ssh-import-id lands and that page updates
[16:54] <slingamn> sweet
[16:55] <slingamn> still thinking about removing it from cloud-init (not for hirsute though)
[16:56] <slingamn> the basic change should be pretty easy, since cloud-init only uses it behind a compatibility layer / internal library function
[16:56] <rbasak> cloud-init needs to run on some very old distro releases. So you might have some trouble there.
[16:57] <slingamn> oh, hmm
[16:57] <slingamn> i'll ask in its channel
[16:57] <rbasak> You might be able to do something with a conditional import, requiring requests only on those older releases. But that would also carry a maintenance burden
[16:57] <rbasak> Sure
[23:24] <phibs> Anyone know why ipmitool won't build from the DSC on Ubuntu 20.04 ?