/srv/irclogs.ubuntu.com/2021/08/05/#ubuntu-release.txt

LocutusOfBorgwow xnox!07:16
LocutusOfBorgso R^3: no was actually correct in vbox?07:16
-queuebot:#ubuntu-release- New: accepted oem-sutton.newell-adkins-meta [sync] (focal-proposed) [20.04~ubuntu1]07:36
apwvorlon, the abi changes on 99% of all uploads07:37
-queuebot:#ubuntu-release- New binary: oem-sutton.newell-adkins-meta [amd64] (focal-proposed/none) [20.04~ubuntu1] (canonical-oem-metapackages)07:43
apwvorlon, we may have also transitioned you between streams at the same time though, 460->470 or some such.07:44
-queuebot:#ubuntu-release- New: accepted oem-sutton.simon-barbara-meta [sync] (focal-proposed) [20.04~ubuntu1]07:45
-queuebot:#ubuntu-release- New binary: oem-sutton.simon-barbara-meta [amd64] (focal-proposed/none) [20.04~ubuntu1] (canonical-oem-metapackages)07:49
-queuebot:#ubuntu-release- New: accepted oem-sutton.newell-canyon-meta [sync] (focal-proposed) [20.04~ubuntu1]07:51
-queuebot:#ubuntu-release- New binary: oem-sutton.newell-canyon-meta [amd64] (focal-proposed/universe) [20.04~ubuntu1] (canonical-oem-metapackages)08:02
-queuebot:#ubuntu-release- New: accepted oem-sutton.newell-aenedleah-meta [sync] (focal-proposed) [20.04~ubuntu1]08:02
-queuebot:#ubuntu-release- New binary: oem-sutton.newell-aenedleah-meta [amd64] (focal-proposed/none) [20.04~ubuntu1] (canonical-oem-metapackages)08:05
laneysil2100: you reviewing those oem metas?08:09
laneyjust as a reminder, they need to be accepted into main08:09
sil2100laney: yessir! I remember that, will promote them afterwards08:11
sil2100I just can't insta-accept them into main as sru-review doesn't support such an operation08:11
sil2100But it's on my radar, will do that once I accept all the binaries08:12
laneyokey08:12
laneysru-review needs sorting out a bit for these things08:12
laneylike fixing the tasks properly08:12
laneyanyway thanks for doing that!08:13
sil2100Yeah, I'm for instance sadly adding the bug tasks manually after each accept, since only then it's possible to do that - earlier the package is still unknown08:13
sil2100But it's okay08:14
-queuebot:#ubuntu-release- New: accepted oem-sutton.newell-adrian-meta [sync] (focal-proposed) [20.04~ubuntu1]08:14
laneyI'm not sure which order LP will let things happen in, but the tool could do the accept(); fix_tasks(); dance08:15
laneyalso take the component to accept into main directly08:15
laneyanywayyayay08:15
RikMillssil2100: if I upload a focal plasma SRU later today, is there a chance to get it in the point release?08:16
RikMillsit is just the bugfixes, so 12 packages instead of 40+08:17
sil2100RikMills: oh my, if you feel this isn't too risky, sure08:18
sil2100We'd have to get the SRUs prepared and accepted today08:18
-queuebot:#ubuntu-release- New binary: oem-sutton.newell-adrian-meta [amd64] (focal-proposed/none) [20.04~ubuntu1] (canonical-oem-metapackages)08:18
RikMillssil2100: if you think its better, I can do this right after the point release. not a big deal08:23
mwhudsonsil2100: can we get a focal live server image build with livecd-rootfs from proposed?08:24
sil2100mwhudson: hey! Sure, I can do that o/08:24
mwhudsonty08:24
sil2100Though I don't think I have any way of stopping it from going to current/08:24
sil2100...guess that's fine?08:24
laneydo another non proposed one straight after ;-)08:25
RikMillssil2100: in fact lets wait on the plasma SRU. would hate to make a mistake in haste. I will let it be tested in a PPA for a week or two08:28
RikMillssorry for the noise08:28
sil2100RikMills: no worries! I mean, maybe I'm oversensitive, but with the recent point-release hiccups we had, I feel as if playing it safe is a much better option08:29
RikMillsyep, very fair point08:29
mwhudsonsil2100: yeah i think what laney says is probably ok09:09
mwhudsonsil2100: i can probably sabotage the ci runs somehow :)09:09
dokofyi, gcc-defaults pointing to GCC 11 is now in impish-proposed, but not yet built on all archs. will follow-up once it it built everywhere09:45
schopinwhat's the policy regarding autopkgtests failures caused by testbed limitations rather than the tested software itself? i.e. Debian bug https://bugs.debian.org/961138 causing the following failures https://autopkgtest.ubuntu.com/packages/r/r-bioc-rtracklayer/bionic/amd6409:49
ubottuDebian bug 961138 in autodep8 "autodep8 uses host APT packages to generate dependencies for pkg-r-autopkgtest tests" [Normal, Open]09:49
schopinis it reasonable to add a britney override on a case-by-case basis?09:49
mwhudsonsil2100: can you ping me / comment on one of the SRU bugs when that proposed=1 build finishes?10:19
* mwhudson falls azleep10:19
sil2100o/10:33
sil2100uh, what the heck, the build died10:33
sil2100I'll restart those without --live once the arm64 live build finishes10:35
sil2100Ok, this time it didn't barf, I see it's moving on as expected10:57
-queuebot:#ubuntu-release- New: accepted oem-sutton.newell-adrion-meta [sync] (focal-proposed) [20.04~ubuntu1]10:59
-queuebot:#ubuntu-release- New binary: oem-sutton.newell-adrion-meta [amd64] (focal-proposed/none) [20.04~ubuntu1] (canonical-oem-metapackages)11:02
sil2100mwhudson: hey! Ok, so the build seems to have finished, 20210805.1 is the publish ID11:03
sil2100Let me comment on the bug as well11:03
-queuebot:#ubuntu-release- New: accepted oem-sutton.newell-carin-meta [sync] (focal-proposed) [20.04~ubuntu1]11:08
-queuebot:#ubuntu-release- New binary: oem-sutton.newell-carin-meta [amd64] (focal-proposed/none) [20.04~ubuntu1] (canonical-oem-metapackages)11:12
slyonHey! I have a question regarding systemd vs snapd for the ubuntu-release team: For this cycle we wanted to switch to cgroups v2 in systemd by default and feature freeze is approaching, but snapd isn't quite ready yet (pending review & testing: https://github.com/snapcore/snapd/pulls?q=is%3Apr+is%3Aopen+label%3Acgroupv2), thus enabling cgroups v2 would break snapd and systemd autopkgtest and block migration.13:32
slyonHow to handle this situation? I see 3 options (non of which is ideal):13:32
slyon1/ postpone cgroups v2 to next cycle13:32
slyon2/ upload systemd, blocking the migration and wait for snapd to deploy the pending fixes13:32
slyon3/ wait for snapd to deploy the fixes and request a FFe for systemd13:32
slyonwhat's the release team's opinion on this?13:32
stgraberI'd go with 2). It'd also be interesting to understand what the adt failures would be for snapd. With my LXD hat on, we have our snap running on a variety of distros that made the switch to cgroup2 and it's working just fine. The main visible issue is the snapd warning message every time a command is run and in the backend there's the issue that some operations that use the freezer cgroup13:37
stgraberwill run without it.13:37
stgraberbut if that's the extent of it, I'd probably argue we shouldn't even hold the entire migration in -proposed but let it hit the release pocket so we have more time to find additional issues with cgroup2 and just get a commitment from the snapd team that cgroup2 support will be there by beta or final freeze13:37
stgraberpostponing by one release means switching to cgroup2 on an LTS which seems like a terrible plan to me13:38
stgraberand similarly, switching systemd at the last minute in the 21.10 cycle makes it very likely we'll be dealing with a bunch of potentially complex issues as SRUs13:39
LocutusOfBorgvorlon, hello, please hint node-websocket-driver? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991820 regressed in release, rc buggy in Debian, fails testsuite too there13:43
ubottuDebian bug 991820 in src:node-websocket-driver "node-websocket-driver: autopkgtest needs update for new version of nodejs: DeprecationWarning: The legacy HTTP parser is deprecated." [Serious, Open]13:43
bdmurrayv_orlon is out this week13:43
bdmurraylaney: could you look at bug 1843049 and add boxer-data to the sync-blacklist?13:44
ubottuBug 1843049 in boxer-data (Ubuntu) "boxer-data: please keep it out from eoan" [Undecided, New] https://launchpad.net/bugs/184304913:44
slyonthanks for your stance on this, stgraber! I'm currently doing some testing around this here: https://bileto.ubuntu.com/excuses/4602/impish.html For snapd it seems to be the "tests/smoke/sandbox" test that is failing, for systemd its only the "tests-in-lxd" tests that are failing, only for that LXD/snapd "WARNING" message that you mentioned. That warning message is logged to stderr and picked up by autopkgtest, failing those tests. systemd13:45
slyontests would most probably pass it the warning wouldn't be there13:45
slyonoption (2) was also what was suggested to do by the snapd team. So it's good being on the same page here. I'll let this age a bit to give others a chance to jump in and do some more testing on my side. If I do not hear any objections, I'll enable cgroups v2 in systemd within the next two weeks13:48
laneybdmurray: will do14:15
-queuebot:#ubuntu-release- New: accepted oem-sutton.simon-aenescumb-meta [sync] (focal-proposed) [20.04~ubuntu1]14:38
-queuebot:#ubuntu-release- New binary: oem-sutton.simon-aenescumb-meta [amd64] (focal-proposed/none) [20.04~ubuntu1] (canonical-oem-metapackages)14:40
-queuebot:#ubuntu-release- Unapproved: accepted gnome-control-center [source] (focal-proposed) [1:3.36.5-0ubuntu3]15:22
stgraberslyon: we could probably have the snapd team make the warning disappear when a particular env variable is set15:38
stgraberslyon: that would then make it easier to still run normal adt tests without the warning on stderr causing everything to fail15:38
stgraber(while retaining it for actual users)15:38
slyonstgraber: that's a good idea! I might come up with a snapd PR tomorrow and propose that change to the snapd team15:44
-queuebot:#ubuntu-release- New: accepted oem-sutton.simon-cabernet-meta [sync] (focal-proposed) [20.04~ubuntu1]15:44
juliankDebian's release is next Saturday, I wonder if it would make sense to stop the importer a few days earlier to not get all the fancy new stuff hitting unstable directly before feature freeze15:45
laneycould be a good idea15:46
-queuebot:#ubuntu-release- New binary: oem-sutton.simon-cabernet-meta [amd64] (focal-proposed/none) [20.04~ubuntu1] (canonical-oem-metapackages)15:46
juliankI'll write an emaail15:48
bdmurraycabernet15:48
laney🍷15:49
juliankAn email has been sent to ubuntu-devel15:56
schopinbdmurray: could you have a look and merge https://code.launchpad.net/~schopin/britney/+git/hints-ubuntu/+merge/406727 ? Once this is done, the openssl SRUs should all be good to go.15:57
bdmurrayschopin: It looks like there's a conflict or something in the diff16:01
-queuebot:#ubuntu-release- New: accepted oem-somerville-sanbernardino-meta [sync] (focal-proposed) [20.04~ubuntu1]16:03
-queuebot:#ubuntu-release- New binary: oem-somerville-sanbernardino-meta [amd64] (focal-proposed/none) [20.04~ubuntu1] (canonical-oem-metapackages)16:05
-queuebot:#ubuntu-release- New: accepted oem-sutton.newell-adkins-meta [amd64] (focal-proposed) [20.04~ubuntu1]16:07
-queuebot:#ubuntu-release- New: accepted oem-sutton.newell-aenedleah-meta [amd64] (focal-proposed) [20.04~ubuntu1]16:07
-queuebot:#ubuntu-release- New: accepted oem-sutton.simon-barbara-meta [amd64] (focal-proposed) [20.04~ubuntu1]16:07
-queuebot:#ubuntu-release- New: accepted oem-sutton.newell-adrian-meta [amd64] (focal-proposed) [20.04~ubuntu1]16:07
-queuebot:#ubuntu-release- New: accepted oem-sutton.newell-canyon-meta [amd64] (focal-proposed) [20.04~ubuntu1]16:07
-queuebot:#ubuntu-release- New: accepted oem-somerville-sanbernardino-meta [amd64] (focal-proposed) [20.04~ubuntu1]16:08
-queuebot:#ubuntu-release- New: accepted oem-sutton.newell-carin-meta [amd64] (focal-proposed) [20.04~ubuntu1]16:08
-queuebot:#ubuntu-release- New: accepted oem-sutton.simon-cabernet-meta [amd64] (focal-proposed) [20.04~ubuntu1]16:08
-queuebot:#ubuntu-release- New: accepted oem-sutton.newell-adrion-meta [amd64] (focal-proposed) [20.04~ubuntu1]16:08
-queuebot:#ubuntu-release- New: accepted oem-sutton.simon-aenescumb-meta [amd64] (focal-proposed) [20.04~ubuntu1]16:08
bdmurrayschopin: anyway, I'll sort it out16:13
schopinI guess my remote wasn't up-to-date.16:15
bdmurrayschopin: also won't this be a problem for other releases sometime?16:18
schopinHence my asking earlier about the policy when the bug is in the testbed :)16:21
schopinbdmurray: I don't know enough about how our autopkgtest infra is set up nor the R packages to be able to predict how the problem might evolve over time.16:23
bdmurrayschopin: okay, maybe sending a note to ubuntu-devel is appropriate then so its not just you and I who know that there could be more autopkgtest failures in the future16:24
bdmurraywell you, me and avid readers of #ubuntu-release16:25
schopineh, not just the two of us, there's at least ginggs and tumbleweed :P16:25
schopinOK, I'll write an advisory to the ML :)16:26
bdmurraythanks!16:26
ginggsi'm a bit surprised that issue showed up in bionic, I thought it only appeared later16:38
ginggsbut we do try to prevent it from happening since hirsute16:39
ginggshttps://launchpad.net/ubuntu/+source/dh-r/20210218ubuntu116:39
vorlonapw: the nvidia ABI? (not the kernel abi)17:02
-queuebot:#ubuntu-release- Unapproved: accepted base-files [source] (focal-proposed) [11ubuntu5.4]19:58
-queuebot:#ubuntu-release- Unapproved: accepted zhmcclient [source] (hirsute-proposed) [0.31.0-0ubuntu3~21.04.1]23:16
-queuebot:#ubuntu-release- Unapproved: accepted zhmcclient [source] (focal-proposed) [0.31.0-0ubuntu3~20.04.1]23:19
=== Kamilion is now known as Kamilion|KV

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!