[00:29] -queuebot:#ubuntu-release- Unapproved: accepted lxcfs [source] (eoan-proposed) [3.0.4-2ubuntu1]
[00:30] -queuebot:#ubuntu-release- Unapproved: accepted lxcfs [source] (bionic-proposed) [3.0.3-0ubuntu1~18.04.2]
[01:01] <teward> at this point in the cycle, do seed changes need Release Team approval?
[01:01] <teward> for flavors
[01:06] -queuebot:#ubuntu-release- Unapproved: gnome-control-center (focal-proposed/main) [1:3.36.1-1ubuntu2 => 1:3.36.1-1ubuntu3] (ubuntu-desktop)
[01:40] <vorlon> teward: not "approval", but coordination at least since freeze lists would need updated etc
[01:41] <teward> vorlon: OK, you need to talk to Eickmeyer then before I sync this per his request
[01:41] <vorlon> mm?
[01:41] <teward> bug #1870248
[01:41] <vorlon> surely the seeding is separate from the syncing?
[01:42] <Eickmeyer> A similar sync request never happened last cycle.
[01:42] <Eickmeyer> In fact, it was never even looked at.
[01:42] <Eickmeyer> It's already seeded. Just needs a sync.
[01:42] <vorlon> ok, that wasn't what I understood as "seed change"
[01:43] <Eickmeyer> Not a seed change, teward.
[01:43] <vorlon> so you can sync anything you think is appropriate, and it will land in the unapproved queue due to the freeze
[01:43] <Eickmeyer> It's already seeded.
[01:43] <teward> bleh i'm dead then
[01:43] <teward> E:TIRED
[01:43] <Eickmeyer> lol
[01:43] <teward> vorlon: so if we sync it then it just needs approved then, assuming that the seed manager OKs?
[01:43] <teward> i.e. "JFDI" since Eickmeyer asked?
[01:43] <teward> (at least from me running syncpackage that is)
[01:43] <vorlon> Wimpress: nvidia-dkms-440 is at version 440.64-0ubuntu3 in the focal release pocket.  linux-modules-nvidia-440-generic Provides: nvidia-dkms-440 (= 440.64-0ubuntu2).  We have version skew that shouldn't be allowed to happen but that we currently don't have infrastructure to prevent. :/
[01:44] <vorlon> apw, tseliot: ^^ lrm vs nvidia-graphics-drivers-440 skew in the release pocket
[01:46] <teward> Eickmeyer: sync in progress.  *goes to find coffee*
[01:46] -queuebot:#ubuntu-release- Unapproved: obs-studio (focal-proposed/universe) [24.0.6+dfsg1-1build2 => 25.0.3+dfsg1-2] (ubuntustudio) (sync)
[01:48] <teward> ^ there it is in unapproved.
[01:48] <teward> *lurks*
[01:48] <teward> related: Eickmeyer (ubuntustudio lead) asked for the sync
[01:49] <apw> vorlon, is this the piece where automated upgrades would prevent update but manual dist-upgrade will allow skew to form ...
[01:49] <apw> Wimpress, it is really causing and actual dmesg report ?
[01:50] <apw> vorlon, or are we shy some breaks still
[01:51] <apw> (on the nvidia binaries)
[01:51] <Eickmeyer> teward: ack
[02:15] <Wimpress> apw: I've got to the bottom of the segfaults and kernel panics.
[02:15] <Wimpress> Not us.
[02:16] <Wimpress> TL;DR Z390 motherboards and over optimistic power targets in early BIOS revisions (that I was running) lead to segfaults due to stressing CPU cores.
[02:17] <Wimpress> That said, not sure the intended design is building nvidia driver DKMS modules based on prior chats with vorlon
[02:19] <Wimpress> Following a BIOS update which resulted in a new XMP memory profile and lower boost clock for unicore and multicore, the DKMS module builds successfully complete.
[02:19] <Wimpress> And I'm back in business.
[02:20] <sarnold> woot
[02:21] <Wimpress> sarnold: o/
[02:21] <sarnold> hey Wimpress :)
[04:14] <vorlon> apw: I don't see any breaks around here
[04:37] -queuebot:#ubuntu-release- Unapproved: initramfs-tools (focal-proposed/main) [0.136ubuntu2 => 0.136ubuntu3] (core, i386-whitelist)
[04:40] <vorlon> Eickmeyer: so are you expecting a respin of ubuntustudio beta image for this obs-studio update?
[04:58] <Eickmeyer> vorlon: No, it’s not “OMG must be in Beta” important, more like “let’s get this in for final” important.
[04:58] <vorlon> ok
[05:02] -queuebot:#ubuntu-release- Unapproved: accepted obs-studio [sync] (focal-proposed) [25.0.3+dfsg1-2]
[05:06] -queuebot:#ubuntu-release- Unapproved: accepted nodejs [source] (focal-proposed) [10.19.0~dfsg-3ubuntu1]
[06:09] -queuebot:#ubuntu-release- Unapproved: llvm-toolchain-9 (focal-proposed/main) [1:9.0.1-10 => 1:9.0.1-11] (i386-whitelist) (sync)
[06:09] -queuebot:#ubuntu-release- Unapproved: telegram-desktop (focal-proposed/universe) [1.9.21+ds-1 => 2.0.1+ds-1] (no packageset) (sync)
[06:09] -queuebot:#ubuntu-release- Unapproved: ocaml-deriving-ocsigen (focal-proposed/universe) [0.7.1-1ubuntu1 => 0.7.1-1.1] (no packageset) (sync)
[06:10] -queuebot:#ubuntu-release- Unapproved: accepted ocaml-deriving-ocsigen [sync] (focal-proposed) [0.7.1-1.1]
[06:10] -queuebot:#ubuntu-release- Unapproved: rejected telegram-desktop [sync] (focal-proposed) [2.0.1+ds-1]
[06:26] -queuebot:#ubuntu-release- Unapproved: rlottie (focal-proposed/universe) [0~git20190721.24346d0+dfsg-2build1 => 0~git20200305.a717479+dfsg-1] (no packageset) (sync)
[06:26] -queuebot:#ubuntu-release- Unapproved: accepted rlottie [sync] (focal-proposed) [0~git20200305.a717479+dfsg-1]
[06:57] <sil2100> mwhudson: hey! Thanks for working on that subiquity bug
[06:57] <sil2100> mwhudson: did you get any confirmation of anyone that it fixes the bug?
[06:57] <sil2100> s/of/from/
[07:08] <jibel> sil2100, Hi, do you have the diff of the manifests between ubuntu desktop 0331 and 0401 ?
[07:11] <sil2100> jibel: https://paste.ubuntu.com/p/RG732BVvfB/
[07:14] <jibel> thanks
[07:17] <sil2100> mwhudson: is there an easy way for paride to refresh subiquity to an edge version after booting for testing? I guess so, right?
[07:20] <mwhudson> sil2100: yeah, drop to shell and snap refresh --edge subiquity
[07:21] <mwhudson> sil2100: no, no confirmation yet
[07:23] <sil2100> paride: once you're up, could you give it a spin? Since if that helps, I'd like it promoted to stable and images respun ASAP ;) ^
[07:28] <paride> sil2100, mwhudson, up
[07:28] <paride> I've just read the new comments on the bugs
[07:28] <paride> and I'm going to try edge
[07:29] <mwhudson> hmm i think edge might have some other problems
[07:29] <mwhudson> but it would be interesting to know if it segfaults
[07:29] <paride> well let's see
[07:30] <mwhudson> oh ffs
[07:30] <mwhudson> paride: just don't rush :)
[07:30] <mwhudson> if you go a bit slowly i think it'll be fine...
[07:32] -queuebot:#ubuntu-release- Unapproved: python-seamicroclient (focal-proposed/universe) [0.4.0+2016.05.20.git.40ee44c664-2ubuntu1 => 0.4.0+2016.05.20.git.40ee44c664-3ubuntu1] (ubuntu-server)
[07:32] <sil2100> paride: thanks!
[07:33] <sil2100> mwhudson: hm, since you're saying edge is a bit risky right now, what would be the best steps to get this fix into stable then?
[07:34] <mwhudson> sil2100: ah i think i've found the bug and i think it's probably in stable already...
[07:34] <sil2100> mwhudson: do you have separate branches per channel?
[07:34] <mwhudson> sil2100: in general no, such a thing can always be arranged though
[07:34] <sil2100> Ouchy ;)
[07:34] <mwhudson> it's an obscure race, you'll only hit it if you're racing through the ui
[07:35] <mwhudson> or on a very slow network
[07:35] <cpaelzer> hi release team - I'd ask for the fix for https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1869629 which is in focal-unapproved to be evalauted and accepted
[07:35] <cpaelzer> it could cause test issues in various places (fix is in apparmor abstraction) - so having it fixed should reduce the noise of the beta test feedback a bit
[07:35] <sil2100> cpaelzer: the usual question: that's for post-beta, right?
[07:36] <cpaelzer> post-beta but pre-release
[07:36] <cpaelzer> but if post-beta someone shoudl know that any kind of mdns issues are likely due to that
[07:37] <mwhudson> sil2100, paride: i've just landed a branch that should make debugging the bug of doom easier
[07:38] <mwhudson> sil2100, paride: so if it does recur, retrying with the snap that will hit edge in 20 mins or so might make sense
[07:38] <cpaelzer> sil2100: totally different question - riscv is now enabled in bileto PPAs and since the checkbox is disabled I can't disable it
[07:38] <cpaelzer> sil2100 any chance to not have riscv enabled there?
[07:39] <cpaelzer> wasn't an issue a few hours ago ...
[07:40] <cpaelzer> wgrant:  you are MR riscv :-) - do you have a chance to disable riscv on a single PPA for me to be able to go on atm https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4000 ?
[07:41] <wgrant> cpaelzer: Huh, I wonder how that appeared there
[07:41] <wgrant> Ohhh, maybe bileto automatically configures all arches
[07:41] <wgrant> riscv64 isn't enabled in the primary archive yet...
[07:42] <cpaelzer> I know wgrant, but bileto usualyl enables all
[07:42] <cpaelzer> and until sil2100 found some time to make that be differentwe'd prefer to have some way to disable it
[07:42] <wgrant> Yeah, we didn't consider things dynamically creating PPAs using the whole set of processors, rather than just mirroring the primary rachive
[07:42] <wgrant> cpaelzer: I've disabled riscv64 on that PPA and cancelled the build
[07:43] <wgrant> I don't know if that'll be enough to make bileto happy
[07:43] <cpaelzer> wgrant: I can see why users can't enable it (like int he old devirt days) but maybe LP could allow everyone to "disable" it ?
[07:43] <cpaelzer> is that hard?
[07:43] <wgrant> Anyone can, on their own PPAs
[07:44] <cpaelzer> nope (for me) I can't on https://launchpad.net/~paelzer/+archive/ubuntu/test-is-riscv-on/+edit
[07:44] <cpaelzer> the checkbox is greyed out
[07:44] <cpaelzer> I can neither enable (my PPA) nor disable (Bileto PPA that starts with all enabled)
[07:45] <wgrant> Enablement is meant to be restricted
[07:45] <sil2100> cpaelzer: uh, yeah, we never had this problem, might need to tweak bileto a bit
[07:45] <wgrant> It's possible the UI disables the checkbox in both cases
[07:45] <wgrant> But the API should allow disablement
[07:45] <cpaelzer> wgrant: is there a cmdline to disable it through API?
[07:46] <cpaelzer> I might be able to use that against my bileto PPAs as well (not just the personal ones)
[07:46] <sil2100> cpaelzer: since IIRC bileto periodically fixes up the PPA right now, so that even if you disable it manaully, it will most probably switch it back on
[07:46] <sil2100> (not sure if it does that for arches, but does for other stuff)
[07:46] <wgrant> sil2100: How does bileto calculate the set of archs?
[07:46] <cpaelzer> sil2100: bad that is, but good to know :-)
[07:46] <wgrant> Looks like it might just be all processors
[07:46] <cpaelzer> that might also have been what swicthed it on
[07:46] <cpaelzer> since I as using that PPA for a while without issues
[07:46] <sil2100> wgrant: I think right now it's just 'all', but maybe it should be smarter ;p
[07:47] <wgrant> cpaelzer: It's just setting archive.processors in launchpadlib
[07:47] <sil2100> Will sit down on that in some minutes
[07:48] <wgrant> I'll remove the chroot for now to prevent any more builds from being created
[07:48] <wgrant> Done.
[07:52] <paride> mwhudson, mmh the install still failed but it didn't crash
[07:52] <mwhudson> paride: oh yay
[07:52] <paride>  /target is mounted so no ENOSPC. Let's see what's in the logs
[07:53] <mwhudson> paride: can you add my keys?
[07:53] <paride> sure
[07:54] <mwhudson> paride: or pastebin the .crash i guess
[07:59] <sil2100> wgrant, cpaelzer: ok, this will be a rather easy fix, will push it in some moments
[07:59] <wgrant> sil2100: Great, thanks.
[08:00] <paride> mwhudson, I attached the crash file to the bug. It's too big to pastebin
[08:01] <mwhudson> i should deploy myself a mcdivitt
[08:01] <paride> I also noticed it contains a broken string with non-utf8 non-ascii data, but this is unrelated
[08:01] <RikMills> morning. do we have any re-spine worth bugs? or looking ok so far?
[08:01] <paride> noticed because pastebinit didn't like it
[08:02] <cpaelzer> nice to hear that - thanks sil2100
[08:02] <RikMills> *re-spin
[08:02] <mwhudson>  FileNotFoundError: [Errno 2] No such file or directory: 'efibootmgr': 'efibootmgr'
[08:02] <mwhudson> LOLWUT
[08:02] <sil2100> RikMills: morning! So far I saw nothing like that on the ISOtracker (besides the known subiquity issues)
[08:03] <RikMills> :)
[08:03] <paride> mwhudson, /target/usr/bin/efibootmgr is there
[08:03] <mwhudson> paride: is it there in the live session?
[08:03] <paride> mwhudson, no, at least not in the obvious locations
[08:04] <mwhudson> paride: well isn't that a thing
[08:04] <paride> it is!
[08:06] <mwhudson> paride: i am now very confused
[08:06] <sil2100> RikMills: but anyway, mwhudson and paride are working on those, and I'm pretty sure this will not require any other re-spins besides subiquity - so I think all other isos might be 'final'
[08:07] <RikMills> ok. fingers crossed then :)
[08:07] <paride> sil2100, there's the s390x one
[08:07] <paride> which appears to be subiquity too, but there's a crash in the logs
[08:08] <paride> so I don't really know what the root cause is
[08:16] -queuebot:#ubuntu-release- New: accepted swig3.0 [source] (focal-proposed) [3.0.12-2.2ubuntu1]
[08:18] <mwhudson> as far as i can tell the s390x and arm64 subiquity things are the same
[08:20] <mwhudson> i wonder if i have tried a uefi install recently
[08:23] -queuebot:#ubuntu-release- New binary: swig3.0 [amd64] (focal-proposed/universe) [3.0.12-2.2ubuntu1] (no packageset)
[08:23] <paride> mwhudson, that is what I was hoping for
[08:24] <paride> a manual install run with subiquity edge on s390x succeeded
[08:24] <paride> now I'm running the -edge jenkins job
[08:25] <paride> we'll know in a few minutes
[08:33] <cpaelzer> sil2100: wgrant: FYI as expected the riscv build was turned on again on my PPA
[08:33] <cpaelzer> sil2100: once you got to code and deploy something let me know so I can retry things
[08:34] <mwhudson> paride: yes a uefi install fails locally on amd64 with edge
[08:34] <mwhudson> paride: this seems suboptimal
[08:35] <mwhudson> paride: i guess i should stage efibootmgr into the snap
[08:35] <paride> mwhudson, mmh :/ we test edge but not with uefi
[08:37] <paride> maybe we should switch to testing uefi by default at some point, and bios boot only as part of the 'smoke-default' test
[08:37] <paride> opposite of what we're doing now
[08:37] -queuebot:#ubuntu-release- Unapproved: zsnapd (focal-proposed/universe) [0.8.11h-1ubuntu1 => 0.8.11h-1ubuntu2] (no packageset)
[08:38] <mwhudson> paride: would probably make sense
[08:38] -queuebot:#ubuntu-release- Unapproved: accepted zsnapd [source] (focal-proposed) [0.8.11h-1ubuntu2]
[08:39] <mwhudson> eacb655263bc2177c4d7f9173bc3efd4a9e6bf75 in curtin invokes efibootmgr on the host not target
[08:39] <mwhudson> i wonder if that was intended
[08:39]  * mwhudson digs up the mp
[08:41] <sil2100> cpaelzer: yeah, eek, still need a few minutes, got context switched
[08:43] -queuebot:#ubuntu-release- Unapproved: ubuntu-report (focal-proposed/main) [1.6.0 => 1.6.1] (ubuntu-desktop)
[08:46] <mwhudson> paride: i dropped to a shell, installed efibootmgr and the install completed (on arm64)
[08:54] <paride> mwhudson, I had a look at eacb655263bc2177c4d7f9173bc3efd4a9e6bf75 and nothing makes me think that invoking efibootmgr from the host is intentional
[08:54] <mwhudson> paride: yeah i think so too
[08:55] -queuebot:#ubuntu-release- New: accepted swig3.0 [amd64] (focal-proposed) [3.0.12-2.2ubuntu1]
[08:55] <xnox> mwhudson:  i think it is intended to run efibootmgr on the host, not in target.
[08:56] <xnox> mwhudson:  and i think we used to depend/install efibootmgr, but then dropped. I wonder if cloud/maas images are affected too. Although normally curtin tries to install missing deps but yeah, snap.
[08:57] <mwhudson> xnox: it would work totally fine if it did try to install it
[08:57] <mwhudson> it's in the pool
[08:58] <paride> mwhudson, and I can't tell why https://github.com/CanonicalLtd/subiquity/pull/670 made the crash go away, if that's actually what did it...
[08:58] <gitbot> CanonicalLtd issue (Pull request) 670 in subiquity "write netplan directly to the target" [Closed]
[08:58] <mwhudson> paride: because it means curtin net-meta auto does less stuff
[08:58] <mwhudson> paride: i don't really get it, to be sure
[08:59] <xnox> mwhudson:  ah
[08:59] <mwhudson> xnox, paride: https://github.com/CanonicalLtd/subiquity/pull/678
[08:59] <gitbot> CanonicalLtd issue (Pull request) 678 in subiquity "stage efibootmgr for now" [Open]
[08:59] <xnox> if we don't understand it, let's ship it! that's how release weeks work, right?!
[09:00] <paride> xnox, at least it's not release week, yet!
[09:00] <mwhudson> i would like to understand where the crash came from yes :(
[09:00] <xnox> dry-run mode
[09:00] <paride> ok :)
[09:00] <xnox> mwhudson:  keep the image around, i guess =/
[09:01] <mwhudson> xnox: eh i was going to test that the efibootmgr change actually helps before i merged it :)
[09:01] <mwhudson> (it does, though)
[09:02] <sil2100> cpaelzer: ok, we need to wait for the nearest auto-deploy cycle for bileto
[09:02] <sil2100> cpaelzer: (and hope that the instance won't explode like the last time after an update, for no reason)
[09:05]  * mwhudson starts yet another subiquity edge build
[09:15]  * sil2100 fixes publish-image-set to support the renamed raspi images
[09:15] <xnox> mwhudson:  ah, ok
[09:16] <sil2100> cpaelzer: ...this happens every 30 minutes, so I htink we missed the previous tick. Do in ~15 minutes the changes should be deployed
[09:17] <sil2100> Laney: do you think it makes sense to pre-publish only the desktop images?
[09:20] <Laney> sil2100: why not
[09:21] <mwhudson> oh ffs eftbootmgr not available everywhere of course
[09:33] <rbalint> cpaelzer, chrony and ntp are now coinstallable in focal unlike in eoan, imo we should pick https://salsa.debian.org/pkg-ntp-team/ntp/-/commit/a696bf0bef7118039f04b41cb0688980f2ebe90b after the beta is out
[09:34] <rbalint> cpaelzer, i also rely on it with my fix in https://salsa.debian.org/systemd-team/systemd/-/merge_requests/61 but i can special case ntp if needed
[09:35] -queuebot:#ubuntu-release- Unapproved: bedtools (focal-proposed/universe) [2.27.1+dfsg-4 => 2.27.1+dfsg-4ubuntu1] (no packageset)
[09:36] <xnox> mwhudson:  yeas, not on ibm =)
[09:36] -queuebot:#ubuntu-release- Unapproved: accepted bedtools [source] (focal-proposed) [2.27.1+dfsg-4ubuntu1]
[09:37] <mwhudson> xnox: i am now trying to understand undocumented snapcraft features
[09:39] <xnox> mwhudson:  we should rename it to witchcraft
[09:39] <mwhudson> xnox: haha
[09:39] <mwhudson> granny weathercraft
[09:41] <sil2100> cpaelzer: ok, looks like it's working \o/ https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4002 <- as an example
[09:42] <sil2100> cpaelzer: bileto should auto-correct your PPA automatically at some point, but a diff on the PPA might trigger it earlier
[09:44] <wgrant> Thanks sil2100
[09:58] <mwhudson> xnox, paride: ok building yet another another edge snap
[09:58] <mwhudson> xnox, paride: please beat the heck out of this while i am sleeping :)
[09:59] <xnox> just beat it beat it
[10:00] <xnox> bdmurray:  omg, i understand what you mean now.
[10:01] -queuebot:#ubuntu-release- Unapproved: llvm-toolchain-10 (focal-proposed/main) [1:10.0.0-1ubuntu1 => 1:10.0.0-1ubuntu2] (i386-whitelist)
[10:03] -queuebot:#ubuntu-release- Unapproved: binutils-riscv64-unknown-elf (focal-proposed/universe) [2.32.2019.08+dfsg-1 => 2.34-0ubuntu1] (no packageset)
[10:03] -queuebot:#ubuntu-release- Unapproved: accepted binutils-riscv64-unknown-elf [source] (focal-proposed) [2.34-0ubuntu1]
[10:05] -queuebot:#ubuntu-release- Unapproved: accepted llvm-toolchain-10 [source] (focal-proposed) [1:10.0.0-1ubuntu2]
[10:05] -queuebot:#ubuntu-release- Unapproved: unity-greeter (focal-proposed/universe) [18.04.0+20.04.20200312-0ubuntu1 => 18.04.0+20.04.20200312-0ubuntu2] (mythbuntu)
[10:05] -queuebot:#ubuntu-release- Unapproved: gcc-snapshot (focal-proposed/universe) [1:20200401-1ubuntu1 => 1:20200402-0ubuntu1] (i386-whitelist)
[10:05]  * sil2100 fingers crossed that the new subiquity will fix the world
[10:05] -queuebot:#ubuntu-release- Unapproved: accepted gcc-snapshot [source] (focal-proposed) [1:20200402-0ubuntu1]
[10:06] <paride> sil2100, count me in, but let's remember there's something crashing hidden somewhere
[10:06] -queuebot:#ubuntu-release- Unapproved: accepted wine-development [source] (focal-proposed) [5.5-2ubuntu1]
[10:21] -queuebot:#ubuntu-release- Unapproved: ubuntu-settings (focal-proposed/main) [20.04.4 => 20.04.5] (ubuntu-desktop)
[10:23] -queuebot:#ubuntu-release- Unapproved: snapd (focal-proposed/main) [2.44+20.04 => 2.44.2+20.04] (core)
[10:33] <cpaelzer> sil2100: thanks for the work my ppa 4000 still isn't reset (despite runnign a diff a minute ago)
[10:33] <cpaelzer> I'll give it some time and recheck in a bit
[10:33] <cpaelzer> that PPA seems stuck overall
[10:33] <cpaelzer> also binaries won't publish for more than 2h now
[10:33] <cpaelzer> maybe I should just abandon and use a new one
[10:34] <cpaelzer> maybe that risc build fail + cancel + deactivate arch + reactivate arch confused it
[10:34] <cpaelzer> I can work with a new ticket just as much, so we don't have to debug the old one
[10:37] <RikMills> cpaelzer: I have things in a ppa pending for 1 3/4 hrs. I think the ppa publisher is backlogged or some problem
[10:38] -queuebot:#ubuntu-release- Unapproved: libarchive (focal-proposed/main) [3.4.0-1ubuntu2 => 3.4.0-2ubuntu1] (core, i386-whitelist)
[10:39] -queuebot:#ubuntu-release- Unapproved: zfs-linux (focal-proposed/main) [0.8.3-1ubuntu10 => 0.8.3-1ubuntu11] (core)
[10:40] <didrocks> sil2100: this one ^
[10:40] <sil2100> Laney is on it o/
[10:40] <didrocks> ack :)
[10:41] <wgrant> RikMills, cpaelzer: Forgot to turn something back on, sorry. Fixing.
[10:44] -queuebot:#ubuntu-release- Unapproved: accepted zfs-linux [source] (focal-proposed) [0.8.3-1ubuntu11]
[10:45] <cpaelzer> ah ok then wgrant
[10:45] <cpaelzer> thanks
[10:46] <cpaelzer> wgrant: what is the time we should re-check - immediately or in Xmin?
[10:46] <wgrant> cpaelzer: The PPA publisher isn't instantaneous. Will be 10 minutes at least
[10:46] <Laney> That zfs-linux is looking like a respin :(
[10:46] <cpaelzer> yeah I was expecting some delay, thanks for providing an ~ETA
[10:47] <didrocks> sorry Laney, sil2100 :/
[10:48] <didrocks> worked fine on already installed system, the bug is only on new install after the *second* boot (but it’s the first one which silently screws things up)
[10:50] <sil2100> And I have hoped we won't do any respins ;/
[10:50] <sil2100> Oh well!
[10:56] <seb128> could we also get ubuntu-settings approved if we respin?
[10:56] <seb128> it's only a change to our default launcher config to update for the gnome-software -> snap-store change we did in focal
[10:57] <seb128> the icon is currently missing due to the wrong name being used
[10:59] <sil2100> From the initial look of things, we'll need to respin: ubuntu, xubuntu, ubuntu-mate, ubuntu-budgie, ubuntustudio
[10:59] <sil2100> seb128: I think we'd like to play it very very safe and just get this one thing in, respin ASAP and hopefully get stuff tested in time
[10:59] <seb128> it's a gsettings override, no code
[11:00] <seb128> but as you wish
[11:13] <sil2100> paride: how's the new subiquity looking?
[11:13] <paride> sil2100, edge work on both arm64 and s390x
[11:13] <paride> *works
[11:13] <paride> (I commented on the bugs)
[11:14] <paride> sil2100, I think we're waiting for rharper take on mwhudson's question here: https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/379675
[11:14] <paride> to understand if the problem has to be fixed in subiquity or curtin
[11:18] <sil2100> paride: awesome! So late in the cycle I'd only want to get this into stable and released! Should we poke xnox to get the edge subiquity promoted?
[11:19] <xnox> sil2100:  i could release it to stable/ubuntu-20.04
[11:19] <xnox> sil2100:  not sure about releasing to stable (which is used by bionic too)
[11:19] <sil2100> xnox: ok, as long as we can get it for teh beta, I'm fine with ubuntu-20.04
[11:20] <sil2100> paride: are you relatively happy with the subiquity from edge in that case? Since the sooner we can get this into stable/ubuntu-20.04 the sooner we can respin the subiquity images
[11:21] <paride> xnox, that's a good point, why bionic-live-server-arm64 works if stable is the same for both
[11:21] <paride> and efibootmgr is missing
[11:22] <xnox> paride:  because curtin only calls it for some series, not others?
[11:22] <xnox> or some other per-series behaviour
[11:22] <paride> mmh don't we always need to call it at least once to add the boot entry?
[11:23] -queuebot:#ubuntu-release- Unapproved: firefox (focal-proposed/main) [74.0+build3-0ubuntu1 => 75.0+build1-0ubuntu1] (mozilla, ubuntu-desktop)
[11:24] <paride> sil2100, I am from this first round of tests, but I'm not fully aware of all the bits we have in edge that we don't have in stable
[11:25] <paride> so I'm not sure there is stuff in edge we don't expect to land in stable for the moment
[11:25] <paride> but xnox can probably give the green light on this
[11:30] <xnox> paride:  because bionic tests are not run in uefi
[11:30] <xnox> ?
[11:30] <paride> xnox, arm!
[11:39] <xnox> Skipping install of {'efibootmgr', 'vlan', 'bridge-utils', 'grub-efi-arm64', 'grub-efi-arm64-signed', 'ifenslave'}.  Not needed on netplan system.
[11:39] <xnox> start: cmd-install/stage-curthooks/builtin/cmd-curthooks: Installing packages on target system: ['efibootmgr', 'grub-efi-arm64', 'grub-efi-arm64-signed']
[11:39] <xnox> is confusing
[11:42] -queuebot:#ubuntu-release- Unapproved: update-notifier (focal-proposed/main) [3.192.29 => 3.192.30] (ubuntu-desktop, ubuntu-server)
[11:44] -queuebot:#ubuntu-release- Unapproved: pysmi (focal-proposed/main) [0.3.2-1build1 => 0.3.2-2] (ubuntu-server) (sync)
[11:44] -queuebot:#ubuntu-release- Unapproved: python-pysnmp4 (focal-proposed/main) [4.4.6+repack1-1build1 => 4.4.6+repack1-2] (ubuntu-server) (sync)
[11:46] <xnox> sil2100:  promoted edge subiquity to latest/stable/ubuntu-20.04 i think we can respin subiquity images for focal beta
[11:46] <xnox> sil2100:  and figure out more details if curtin is correct; and if bionic is affected later
[11:47] <sil2100> \o/
[11:48] <sil2100> Let me spin those in a moment
[11:49] <sil2100> Laney: ^
[11:49] <sil2100> (JFYI)
[11:49] <Laney> aye
[11:49] <Laney> probably do those separately as well
[11:50] <sil2100> I guess I'll do it in 2 batches, one for s390x, ppc64el and amd64 and one for arm64
[12:07] -queuebot:#ubuntu-release- Unapproved: chromium-browser (focal-proposed/universe) [80.0.3987.87-0ubuntu1 => 80.0.3987.162-0ubuntu1] (ubuntu-desktop)
[12:16] -queuebot:#ubuntu-release- Unapproved: gcc-riscv64-unknown-elf (focal-proposed/universe) [8.3.0.2019.08+dfsg-1build1 => 9.3.0-0ubuntu1] (no packageset)
[12:16] -queuebot:#ubuntu-release- Unapproved: accepted gcc-riscv64-unknown-elf [source] (focal-proposed) [9.3.0-0ubuntu1]
[12:17] -queuebot:#ubuntu-release- Unapproved: gnutls28 (focal-proposed/main) [3.6.11.1-2ubuntu3 => 3.6.12-2] (core, i386-whitelist) (sync)
[12:30] -queuebot:#ubuntu-release- Unapproved: rejected lintian [source] (focal-proposed) [2.59.0ubuntu1]
[13:00] <oibaf> Hi, can someone please sync https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1870339
[13:01] <oibaf> and https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/1870340 ? Thanks!
[13:22] -queuebot:#ubuntu-release- Unapproved: session-migration (focal-proposed/main) [0.3.4 => 0.3.5] (desktop-core)
[13:23] -queuebot:#ubuntu-release- Unapproved: fwupd (focal-proposed/main) [1.3.9-3 => 1.3.9-4] (core) (sync)
[13:26] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Focal Beta] has been updated (20200402)
[13:26] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Focal Beta] has been updated (20200402)
[13:26] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Focal Beta] has been updated (20200402)
[13:27] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Focal Beta] has been updated (20200402)
[13:43] <sil2100> Subiquity images respun ^!
[13:46] -queuebot:#ubuntu-release- Unapproved: xxhash (focal-proposed/universe) [0.7.2-1 => 0.7.3-1] (i386-whitelist, ubuntu-desktop) (sync)
[13:51] -queuebot:#ubuntu-release- Unapproved: gcc-8 (focal-proposed/universe) [8.4.0-3ubuntu1 => 8.4.0-3ubuntu2] (core, i386-whitelist)
[13:55] <paride> jibel, https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870356
[13:58] <doko> hmm, why is gcc-8 in the core seed?
[14:01] <Laney> So status update on the respin - we're waiting for proposed-migration to give us some green and copy zfs-linux
[14:02] <Laney> then as soon as rmadison shows it's published in the release pocket we'll be hitting the butan
[14:02] <Laney> A couple of hours out at least
[14:06] -queuebot:#ubuntu-release- Unapproved: rejected livecd-rootfs [source] (bionic-proposed) [2.525.42]
[14:11] -queuebot:#ubuntu-release- Unapproved: libvncserver (focal-proposed/main) [0.9.12+dfsg-8 => 0.9.12+dfsg-9] (i386-whitelist, ubuntu-desktop) (sync)
[14:28] -queuebot:#ubuntu-release- Unapproved: ms-gsl (focal-proposed/universe) [1.0.0-2 => 2.1.0-1] (no packageset) (sync)
[14:28] -queuebot:#ubuntu-release- Unapproved: accepted ms-gsl [sync] (focal-proposed) [2.1.0-1]
[14:31] <seb128> paride, jibel, can we get champagne bugs at a minimum be reported with apport? Reports without any information about the package versions used, nor the desktop environment nor logs are creating extra work...
[14:33] <paride> seb128, let me add some missing info to that one, in any case I'm file if it's demoted as non-champagne
[14:46] -queuebot:#ubuntu-release- Unapproved: mypaint (focal-proposed/universe) [2.0.0-1 => 2.0.0-1ubuntu1] (no packageset)
[14:48] <Laney> zfs-linux migrated, waiting for it to publish
[14:49] <didrocks> yep
[14:49] -queuebot:#ubuntu-release- Unapproved: python-traceback2 (focal-proposed/main) [1.4.0-5build1 => 1.4.0-5ubuntu1] (i386-whitelist, ubuntu-desktop, ubuntu-server)
[14:52] <sil2100> paride: btw. can you double check that the latest subiquity images we re-spun are good to go?
[14:53] <teward> sil2100: can you approve mypaint? it fixes a Fails To Run bug.
[14:53] <teward> (because of missing deps)
[14:53] <teward> (on behalf of the Studio team, cc RikMills)
[14:56] -queuebot:#ubuntu-release- Unapproved: jemalloc (focal-proposed/universe) [5.2.1-1build1 => 5.2.1-1ubuntu1] (i386-whitelist, ubuntustudio)
[15:08] <Laney> OK it's arrived
[15:09] <Laney> I'm going to respin everything that seeds zfs-linux now
[15:10] <paride> sil2100, the jenkins jobs failed :/ checking why.
[15:13] <sil2100> Laney: \o/
[15:13] <sil2100> paride: ouch
[15:20] <Laney> Ahhhhhh
[15:21] <Laney> my smart idea about doing the builds in parallel doesn't work because there's a lock
[15:21] <juliank> locks are nice
[15:21] <Laney> they are made to be picked
[15:24] <sil2100> Laney: just fire up the amd64 one for now and them arm64
[15:24] <sil2100> ;)
[15:24] <Laney> am doing
[15:24] <sil2100> Sweet!
[15:31] <Laney> sil2100: hm, it's on server too, should we respin that or leave it?
[15:37] <sil2100> zfs? Oh crap, forgot
[15:37] <sil2100> Been a while since I last installed a server
[15:37] <sil2100> image
[15:38] <sil2100> xnox: there is an option for using zfs in the subiquity installer?
[15:44] <Laney> sil2100: but this bug/fix shouldn't apply there anyway, so perhaps it's ok to not respin
[15:45] <sil2100> If that's the case, I wouldn't care for beta I think
[15:46]  * sil2100 is a bit distracted with everything going on
[15:46] <xnox> sil2100:  no
[15:47] <Laney> ok good
[15:47] <sil2100> SHIP IT
[15:47] <sil2100> I mean, not respin-it
[15:50] <vorlon> doko: why does your gnutls28 sync drop xnox's default-priority-string handling in debian/rules?
[15:50] <cpaelzer> sil2100: just FYI riscv still gets enabled in PPAs, but I understand that you are busy with other things right now - so really just FYI
[15:51] <xnox> block-propsed! or reject!
[15:52] <xnox> vorlon:  doko: ^ we have different levels set
[15:52] <vorlon> xnox, doko: rejected
[15:53] <xnox> vorlon:  doko: i'll look into merging openssl & gnutls28
[15:53] <xnox> (separetely, not together)
[15:53] <juliank> merge two tls libraries into one
[15:53] <vorlon> merging them together sounds good
[15:53] <juliank> go for it
[15:53] <vorlon> let's do that
[15:53] -queuebot:#ubuntu-release- Unapproved: rejected gnutls28 [sync] (focal-proposed) [3.6.12-2]
[15:53] -queuebot:#ubuntu-release- Unapproved: mstflint (eoan-proposed/universe) [4.11.0+1-1 => 4.13.3+2-2~ubuntu19.10.1] (no packageset)
[15:54] -queuebot:#ubuntu-release- Unapproved: mstflint (bionic-proposed/universe) [4.8.0-2 => 4.13.3+2-2~ubuntu18.04.1] (no packageset)
[15:59] <paride> seb128, thanks for finding the upstream bug for the bluetooth issue. I still think the "works with blueman" bit of information was a key part of my bug report, the one that allowed me to point to blame gnome-control-center. But OK.
[16:00] <seb128> paride, I find it quite confusing 'why is the description talking about blueman. what does blueman has to do with it. is he even using ubuntu/gnome'
[16:00] <seb128> paride, usually it's best to focus the description to be short and explaining the problem
[16:00] <seb128> then you can add comments with side points
[16:09] <sil2100> cpaelzer: hey! So uh, apparently riscv64 is now enabled in the archive
[16:09] <sil2100> cpaelzer: so not much I can do without hard-coding it in bileto right now ;/
[16:10] <sil2100> Since if you check via LP API lp.distributions['ubuntu'].main_archive.processors now has riscv64
[16:10] <sil2100> While in the morning it didn't, as we expected
[16:16] <sil2100> paride: did you manage to take a look why the jenkins job failed? Anything wrong with the images?
[16:17] <paride> sil2100, I am still not sure, I am now trying manually
[16:17] <sil2100> Beta release status update: as some of you might have seen the zfs-linux and subiquity fixes have migrated and we are now rebuilding the images that were affected
[16:17] <sil2100> Those should be built in some time - taking longer than usual due to the networking weirdness
[16:22] <paride> sil2100, seb128, local install works, but I didn't test all the archs yet. Looking at the jenkins jobs again as it's pretty strange they're failing
[16:31] -queuebot:#ubuntu-release- Unapproved: lxc (focal-proposed/universe) [1:4.0.0-0ubuntu1 => 1:4.0.0-0ubuntu2] (ubuntu-server)
[16:32] -queuebot:#ubuntu-release- Unapproved: accepted lxc [source] (focal-proposed) [1:4.0.0-0ubuntu2]
[16:34] <paride> seb128, sil2100, xnox, paramiko can't ssh to the testbed system: https://paste.ubuntu.com/p/KmhhpsXhjT/
[16:35] <paride> I think paramiko is not able to handle all types of key yet, I already saw this but now I don't remember the details
[16:36] <paride> was anything related to this changed in the latest respin?
[16:37] -queuebot:#ubuntu-release- Unapproved: snapd (disco-proposed/main) [2.42.1+19.04 => 2.44.2+19.04] (core)
[16:37] -queuebot:#ubuntu-release- Unapproved: snapd (eoan-proposed/main) [2.42.1+19.10 => 2.44.2+19.10] (core)
[16:39] -queuebot:#ubuntu-release- Unapproved: snapd (bionic-proposed/main) [2.42.1+18.04 => 2.44.2+18.04] (desktop-core, ubuntu-server)
[16:39] -queuebot:#ubuntu-release- Unapproved: snapd (xenial-proposed/main) [2.42.1 => 2.44.2] (desktop-core, ubuntu-server)
[16:42] <bdmurray> disco-proposed?
[16:42] <bdmurray> those crazy snapd developers
[17:06] <bdmurray> Should "Ctrl+C" to cancel filesystem checks work in QEMU?
[17:08] <jibel> bdmurray, it does, but it's slow to react
[17:09] <bdmurray> yeah, slow enough that I got bored
[17:09] -queuebot:#ubuntu-release- Unapproved: ubuntu-mate-meta (focal-proposed/universe) [1.261 => 1.262] (ubuntu-mate)
[17:09] <sil2100> paride: the latest respin should have been new-subiquity only
[17:10] <sil2100> (and zfs-linux, but that's not relevant to the subiquity images)
[17:10] <bdmurray> jibel: I'm testing bug 1824905 and it only took me like 3s. Do you know if this is better?
[17:10] <sil2100> Ah, actually, zfs-linux didn't change for subiquity images
[17:10] <jibel> bdmurray, well I had to press CTRL+C like 10 times
[17:10] <bdmurray> jibel: I've no idea if I *had* to but I did too. ;-)
[17:12] <bdmurray> It made it to 99% and then said check skipped
[17:13] <handsome_feng> Hi, I will mark ubuntukylin ready now although there are still some problems (will fix them after beta ASAP), It is  01:14 now in china... Thank you release team and happy release day! :)
[17:13] <jibel> No work has been done to improve it and there is still a long delay to switch to next page
[17:14] <jibel> bdmurray, ^
[17:15] -queuebot:#ubuntu-release- Unapproved: rejected mstflint [sync] (eoan-proposed) [4.13.3+2-2~ubuntu19.10.1]
[17:20]  * Laney cries
[17:21] <bdmurray> Well then release note it is
[17:22] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Focal Beta] has been marked as ready
[17:27] <bdmurray> release_notes_url points to http://www.ubuntu.com/getubuntu/releasenotes?...
[17:27] <bdmurray> So do we need to ping IS about the redirect?
[17:27] <bdmurray> sil2100: ^^
[17:28] <Laney> where's that used?
[17:28] <bdmurray> ubiquity/plugins/ubi-language.py:_release_notes_url_path = '/cdrom/.disk/release_notes_url'
[17:32] -queuebot:#ubuntu-release- Unapproved: accepted mstflint [source] (eoan-proposed) [4.13.3+2-2~ubuntu19.10.1]
[17:32] -queuebot:#ubuntu-release- Unapproved: rejected mstflint [sync] (bionic-proposed) [4.13.3+2-2~ubuntu18.04.1]
[17:34] <sil2100> The build uploads feel even slower today
[17:36] -queuebot:#ubuntu-release- Unapproved: accepted mstflint [source] (bionic-proposed) [4.13.3+2-2~ubuntu18.04.1]
[17:40]  * Laney holds sil2100 
[17:40] <Laney> it's still April 2 somewhere on the planet for quite some time ...
[17:42] <sil2100> ;)
[17:42] <Laney> I did once send a release announcement in Honolulu time
[17:46] <fo0bar> https://lists.ubuntu.com/archives/ubuntu-announce/2018-April/000231.html <-- check the time; ruined by mailman converting BST to UTC
[17:48] <Laney> :D
[17:48]  * Laney was in that room
[17:48] <Laney> it was a stressful one
[17:49] <fo0bar> yeah, I was handling cloud cache image uploads at the time, I think everything finished at about 23:59:15
[17:49] <Eickmeyer> Which bug had the zfs issue?
[17:49] <Eickmeyer> (somoene filed a duplicate)
[17:49] <Laney> Don't know if there's a bug report
[17:50] <Laney> Feel free to close it with a link to the zfs-linux upload I'd say
[17:50] <fo0bar> bdmurray: oh, and anything under ubuntu.com is now exclusively in webteam's domain; IS has no control over frontend content
[17:50] <Eickmeyer> I changed it from Ubuntu Studio (project) to zfs-ubuntu and marked it "Fix Released".
[17:50] <xnox> paride: hm but the machine has networking?
[17:51] <didrocks> Eickmeyer: second reboot after installation drop into grub command line
[17:51] <fo0bar> (previously the FEs had hardcoded redirects for some stuff, but that was eliminated about a month ago)
[17:51] <Eickmeyer> didrocks: bug 1870395
[17:51] <Eickmeyer> Looks like it.
[17:51] <paride> xnox, utah wait for it to reply to a ping before trying to ssh
[17:51] <Laney> fo0bar: That's probably when it broke ;-)
[17:51] <paride> this is *super* strange
[17:52] <didrocks> Eickmeyer: hum, shouldn’t be on first boot, but the report is vague
[17:52] <Eickmeyer> didrocks: Agreed. Should it be "Incomplete"?
[17:53] <fo0bar> Laney: likely.  during the migration, IS had given the list to webteam to cull and integrate the rest into the webapps, which they did.  but to webteam's credit, it was about 15 years worth of cruft, so it's not like every entry could be looked at with precision :)
[17:54] <xnox> paride:  on 30th of march new openssh did land
[17:54] <xnox> paride:  the 8.2p1 release, not sure if that changes things
[17:54] <bdmurray> fo0bar: oh cool, only a month of breakge
[17:55] <fo0bar> of course, that's just a guess.  IANACE (anymore), so this is from memory, heh
[17:56] <paride> xnox, it must be that. I checked the d/changelog and the latest entry was from february, but now I remember it was held in proposed for a long time
[17:57] <paride> mmh
[17:58] <paride> ssh(1), sshd(8), ssh-keygen(1): this release removes the "ssh-rsa" (RSA/SHA1) algorithm from those accepted for certificate signatures
[17:58] <paride> from the changelog
[17:58] <paride> sure enough utah is using a deprecated key type
[17:59] <didrocks> Eickmeyer: let’s keep it like this and ping me if you have people opening bugs
[18:01] <Eickmeyer> didrocks: Ok, will do. :)
[18:10] -queuebot:#ubuntu-release- Unapproved: opencryptoki (focal-proposed/universe) [3.13.0+dfsg-0ubuntu1 => 3.13.0+dfsg-0ubuntu3] (no packageset)
[18:10] -queuebot:#ubuntu-release- Unapproved: accepted opencryptoki [source] (focal-proposed) [3.13.0+dfsg-0ubuntu3]
[18:10] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (focal-proposed/main) [20.2.1~0ubuntu1 => 20.3] (core)
[18:11] <paride> xnox, the utah key works fine on focal apparently. that's not it.
[18:13] <xnox> paride:  so, i think maybe you need to disable ECC keys in paramiko, asking it to ignore them / not use them.
[18:13] <xnox> paride:  i thought i.e. something was done in launchpad to start supporting new key types or ignoring them. maybe grep through launchpad code to see things there?
[18:13] <xnox> i think it uses paramiko too, and like had to upgrade it or something?
[18:13] <xnox> (in the git ssh code stuff)
[18:23] <paride> xnox, the EC bit is often misleading, see https://github.com/paramiko/paramiko/issues/521 https://github.com/paramiko/paramiko/issues/387
[18:23] <gitbot> paramiko issue 521 in paramiko "misleading exception: not a valid EC private key file" [Closed]
[18:23] <gitbot> paramiko issue 387 in paramiko "Key handling is terribad" [Bug, Exception Handling, High Priority, Keys, Open]
[18:24] <paride> and the key is a static key utah always reuses
[18:24] <xnox> horum
[18:32] -queuebot:#ubuntu-release- Unapproved: opencryptoki (focal-proposed/universe) [3.13.0+dfsg-0ubuntu3 => 3.13.0+dfsg-0ubuntu4] (no packageset)
[18:33] -queuebot:#ubuntu-release- Unapproved: accepted opencryptoki [source] (focal-proposed) [3.13.0+dfsg-0ubuntu4]
[18:52] <RikMills> ummm. how come my existing bileto PPA is build riscv64?
[18:52] <RikMills> *building
[19:04] <RikMills> cpaelzer sil2100 can I land that after beta in that state? as the riscv64 builds will obviously dep wait
[19:05] <sil2100> RikMills: yeah, as mentioned above, I tweaked bileto to only set architectures that the archive builds for but as per LP currently riscv64 seems to be enabled for the archive
[19:06] <sil2100> So oh well...
[19:06] <RikMills> ok. I guess briteny will shrug at the depwaits
[19:07] <RikMills> seems an odd time to do this
[19:13] -queuebot:#ubuntu-release- Unapproved: abiword (focal-proposed/universe) [3.0.2-9build2 => 3.0.2-10] (desktop-extra) (sync)
[19:14] <LocutusOfBorg> it seems to be not an odd time, because we are in freeze, so building the archive now is a good time to bootstrap an architecture...
[19:14] <mwhudson> paride: did you get an answer about efibootmgr?
[19:14] <LocutusOfBorg> I'm interested in understanding why llvm-toolchain-10 is not showing risc64 builds...
[19:47] <cpaelzer> sil2100: for now I do my bileto PPA builds overriding architecture in d/control to not build riscv
[19:47] <cpaelzer> that way I can work around it until you had time to fix
[19:48] <paride> mwhudson, I guess it's my time to show up late :) rharper said running efibootmgr from the host is intentional and needed, as IIUC some efi files are not available in the target system (/sys/firmware/efi).
[19:48] <mwhudson> paride: ok
[19:48] <mwhudson> the fix i landed in subiquity can stay then :)
[19:48] <paride> but he was still surprised that it failed
[19:49] <paride> probably expecting curtin to install in efibootmgr to the host system on its own? I'm not sure
[19:49] <paride> rharper, ^^
[19:52] <sil2100> cpaelzer: there's not much to fix sadly
[19:53] <sil2100> cpaelzer: I can blacklist it, but if the architecture is enabled for the target archive, this would basically make syncing less reliable
[19:53] <sil2100> cpaelzer: and it is
[19:53] <cpaelzer> at least our team never uses it for syncs
[19:53] <cpaelzer> and IIRC riscv isn't expected to always build fine
[19:54] <cpaelzer> so there might be some magic dust in the main archive that makes it work there to not consider a build fully broken if one arch is FTFBS
[19:54] <cpaelzer> but in the PPAs that does not work yet
[19:54] <cpaelzer> until that happens I'd ask to disable it there (or allow us to disable it)
[19:54] <cpaelzer> otherwsie the bileto ppas that always were so handy for iterating on cross-arch autopkgests become mostly useless to us - which would be sad
[19:56] <cpaelzer> as discussed many times we don't use it to build and then publish from these PPAs, we use it if we need the real autopkgtest infrastructure to run across architectures
[19:56] <cpaelzer> and that use case is kind of broken if it never passes build state now due to riscv FTFBS
[19:57] <cpaelzer> maybe wgrant could outline how that will work in the actual archive
[19:57] <cpaelzer> if we upload package src:foo now and it FTFBS on riscv but otherwise works what happens then=
[19:57] <cpaelzer> ?
[19:58] <cpaelzer> I'd assume there must be a good share of FTFBS left and I can't imagine we further handicap (the already complex) late minute fixes by suddenly also all have to build fine on riscv
[19:58] <cpaelzer> sil2100: lets wait what wgrant says and then consider replicating that in the bileto PPAs ok?
[20:04] <sil2100> cpaelzer: yeah, let's get feedback from wgrant and I can then look into getting that sorted out
[20:08] <RikMills> so I abandon my landing ppa?
[20:14] <sil2100> hm, ok
[20:15] <RikMills> yes?
[20:17] <RikMills> back later
[20:18] <sil2100> I was considering maybe indeed temporarily give the option to disable arches, but then I noticed it might not be as easy
[20:19] <sil2100> I mean, from the LP POV, since the PPA UI was always graying out the riscv arch
[20:20] <RikMills> maybe I will just upload plasma 5.18.4 direct this time until things are clearer? that should work ok still?
[20:26] <RikMills> or maybe see it will let me land it in the state of the riscv64 depwaiting?
[21:01] -queuebot:#ubuntu-release- Unapproved: ubuntu-wallpapers (focal-proposed/main) [20.04.1-0ubuntu1 => 20.04.2-0ubuntu1] (desktop-core)
[21:24] <sbeattie> hi. The security team accidentally published a package to focal-security. (we were planning to have it sponsored into focal-proposed, but our documentation led our uploader astray.)
[21:24] <sbeattie> The source package is libgd2.
[21:24] -queuebot:#ubuntu-release- Unapproved: libstdc++-arm-none-eabi (focal-proposed/universe) [12build1 => 12build2] (no packageset)
[21:24] <sbeattie> What's the best approach to get this resolved.
[21:24] <sbeattie> ?
[21:24] <sil2100> sbeattie: ok, I think I'll do what Laney just suggested: I can copy it to -proposed for you and remove it from -security
[21:24] -queuebot:#ubuntu-release- Unapproved: accepted libstdc++-arm-none-eabi [source] (focal-proposed) [12build2]
[21:25] <sbeattie> sil2100: that would be awesome, thank you!
[21:25] <cjwatson> xnox: No, the LP work for this was to do with Twisted, not paramiko
[21:25] <cjwatson> (and remains not quite complete)
[21:28] -queuebot:#ubuntu-release- Unapproved: auctex (focal-proposed/universe) [11.91-2ubuntu1 => 11.91-2ubuntu2] (i386-whitelist, ubuntu-desktop)
[21:28] <sil2100> sbeattie: on it now o/
[21:29] <sbeattie> thanks again!
[21:29] -queuebot:#ubuntu-release- Unapproved: libgd2 (focal-proposed/main) [2.2.5-5.2ubuntu1 => 2.2.5-5.2ubuntu1] (desktop-core, i386-whitelist, ubuntu-server) (sync)
[21:34] -queuebot:#ubuntu-release- Unapproved: accepted libgd2 [sync] (focal-proposed) [2.2.5-5.2ubuntu1]
[21:34] <xnox> ok thanks.
[21:51] -queuebot:#ubuntu-release- Unapproved: ubuntu-mate-settings (focal-proposed/universe) [20.04.2 => 20.04.3] (ubuntu-mate)
[21:52] -queuebot:#ubuntu-release- Unapproved: ubiquity-slideshow-ubuntu (focal-proposed/main) [156 => 158] (ubuntu-desktop)
[21:56] -queuebot:#ubuntu-release- Unapproved: ido (focal-proposed/universe) [13.10.0+17.04.20161028-0ubuntu1 => 13.10.0+17.04.20161028-0ubuntu2] (ubuntu-desktop)
[22:02] -queuebot:#ubuntu-release- Unapproved: rejected ubiquity-slideshow-ubuntu [source] (focal-proposed) [158]
[22:23] -queuebot:#ubuntu-release- Unapproved: initramfs-tools (focal-proposed/main) [0.136ubuntu2 => 0.136ubuntu3] (core, i386-whitelist)
[22:26] -queuebot:#ubuntu-release- Unapproved: ubiquity-slideshow-ubuntu (focal-proposed/main) [156 => 158] (ubuntu-desktop)
[23:05] <bdmurray> The respins are still taking a really long time and based on our estimates it will be a few more hours provided everything goes well.
[23:07] <bdmurray> So if you are hanging around waiting to test the respun isos feel free to take a break for the evening / night - whatever it is where you are.
[23:07] <bdmurray> The release team will let you know when we have some news and isos to test.
[23:52] <amurray> hey AA's - I inadvertently published a security update for apport in focal yesterday to focal-security - I would be very grateful if someone could pocket copy it to the release pocket and delete it from focal-security