[06:10] morning everyone [06:12] there's an annoying bug with jitterentropy-rngd/hirsute -> https://bugs.launchpad.net/ubuntu/+source/jitterentropy-rngd/+bug/1922272 [06:12] Launchpad bug 1922272 in jitterentropy-rngd (Ubuntu) "jitterentropy-rngd uses 100% CPU on Linux >= 5.11" [Undecided,New] [06:13] I think it would make sense to fix it before releasing hirsute [06:14] btw, the solution is to update the ubuntu version with the one in debian/testing [06:15] I experienced the bug on my laptop (running hirsute/hirsute-proposed), and with the patched version jitterentropy-rngd does not show that behaviour [08:44] mwhudson: well..... if you are up on VPN you can actually fuse mount rsync of the mirror. [08:44] mwhudson: you can also only have a partial mirror (rsync unsplit mirror on people.canonical.com and then locally) after that only do `apt download` a few bits and pieces. [08:45] mwhudson: or fix ubuntu-cdimage & debian-cd to use things over the network. [08:45] mwhudson: btw i edit the mirror script a lot to skip most of the things. [08:45] i ponder if it will not be too hard to change everything to file:/// and then later allow for http:// [09:21] mwhudson, hey, did you plan to fix the ubuntu-drivers-common build issue? [10:04] seb128: i filed a PR a couple of hours ago [10:04] seb128: https://github.com/tseliot/ubuntu-drivers-common/pull/52 [10:04] mwhudson, ah, thanks [10:04] i suppose i should test build it this time... [10:20] yes it builds now [10:20] seb128: last time my PR got merged and uploaded pretty quickly, but i guess i can upload my change tomorrow if it doesn't [10:31] mwhudson, let's see if tseliot is around === alan_g_ is now known as alan_g [11:11] seb128: I just noticed the size we're getting for ubuntu isos is the arm64 one, do we need to add the arch in there as a tag maybe? [12:46] kanashiro_: looks like there are a bunch of other packages that build-depend on docker. Are these also going to FTBFS now due to the change in docker in bundling in the proposed pockets - same as libpod, etc? http://paste.ubuntu.com/p/BPPktym6dR/ [13:18] wgrant: doko: I'm seeing an odd build fail on groovy (for an SRU build). https://launchpadlibrarian.net/532344737/buildlog_ubuntu-groovy-riscv64.nss_2%3A3.55-1ubuntu3.1_BUILDING.txt.gz [13:18] kanashiro_: could you maybe stick the depending packages into a PPA (both Focal and Groovy I guess) with proposed enabled to check that they still successfully build? [13:18] wgrant: doko: only riscv64 fails while it worked yesterday just fine [13:18] good: https://launchpadlibrarian.net/532187116/buildlog_ubuntu-groovy-riscv64.nss_2%3A3.55-1ubuntu3.1_BUILDING.txt.gz bad https://launchpadlibrarian.net/532344737/buildlog_ubuntu-groovy-riscv64.nss_2%3A3.55-1ubuntu3.1_BUILDING.txt.gz [13:19] one can see that in the good case, the same spot emits a warning "note: variable tracking size limit exceeded with ‘-fvar-tracking-assignments’, retrying without" [13:19] is that anything known from your riscv64 or toolchain experience? === cpaelzer__ is now known as cpaelzer [13:21] cjwatson: I think this might be the 150 vs 1500 timeout that possibly got reverted? [13:23] Hm could be [13:23] May have forgotten about that while reflashing, pesky manual steps [13:31] Laney, ups, yes the arch should be a tag, the script does collect it it meant to be used, I've submitted a change for that now [13:59] node/npm experts, what's going wrong with https://launchpadlibrarian.net/532496413/buildlog_ubuntu-hirsute-amd64.greenbone-security-assistant_20.8.0-2ubuntu1_BUILDING.txt.gz ? [14:03] cpaelzer: I'll fix the timeout, though the reflash process is pretty slow so may take a while [14:07] thank you cjwatson, if you maybe could just restart https://launchpad.net/ubuntu/+source/nss/2:3.55-1ubuntu3.1/+build/21363729 after that is completed that would be great [14:09] Sure [14:18] cpaelzer: Done (still reflashing, but I gave it an updated builder) [14:20] thanks cjwatson [14:43] Reflashing managed to kill one of the VM hosts, sigh [14:44] Sorry for the lost build time on 001..030 [14:46] doko: transient network error it looks like to me. The request looks reasonable otherwise. [14:48] dbungert: builds don't have access to the network, so that points to a missing b-d ... but which one? [14:48] doko: try node-babel-cli please [14:50] note also that babel tends to bring a lot of friends, so that one missing build-dep might be hiding 10 more [14:57] dbungert: how did you see that from the build log? [14:59] npm ERR! network request to https://registry.npmjs.org/@babel%2fcli failed - the @babel/cli part should be the package name in npm-speak [16:04] doko: see debian bug #986531 - maybe you don't want to fix greenbone [16:04] Debian bug 986531 in release.debian.org "RM: gvm-libs/20.8.0-2" [Normal,Open] http://bugs.debian.org/986531 [16:14] dbungert: ^^^ [16:15] doko: I think I concur with this analysis. Even if we wanted to try to fix this, I think that the package has other dependencies that aren't available in ubuntu. [16:20] ok, I'll see that I remove these tomorrow [20:21] you can find the ubuntuÃ-live memstick for backup of Windows 1, using Ubuntu, the perfect suite for developers like YOU !!! it features partclone: https://openbsdtai123.shell.ircnow.org/ubuntu-live-memstick.html