[00:15] <RAOF> blackboxsw: That looks sensible, but ubuntu-release-upgrader hasn't had the usual 7 day aging process. I'm unclear if you're asking for an expedited release, and whether it's appropriate if so.
[00:22] <RAOF> blackboxsw: The update-notifier one is a little weird - all the bugs listed are fix released, and uploaded to Trusty, but these weren't fixed in the subsequent series?
[00:31] <amurray> RAOF: so sil2100 looked at apparmor-3.0.0 in groovy unapproved yesterday and asked if there was a list of changes from the previous -beta1 to the final version - I have highlighted in the changelog that most of the changes was dropping patches that got incorporated in this final release plus the addition of a minor leaf utility binary - is there anything else you need to review this?
[00:32] <RAOF> amurray: Does that apparmor want to be a 0-day SRU, or to go into groovy release?
[00:32] <RAOF> Because I'm not a release team member, so I can only do the former :)
[00:37] <amurray> RAOF: ah apologies - I thought you were release team too - yes ideally this goes into the release, not 0day SRU
[00:40] <amurray> Laney bdmurray: ^^^ ?
[02:01] -queuebot:#ubuntu-release- Unapproved: ukui-control-center (groovy-proposed/universe) [3.0.0-1 => 3.0.1-1] (ubuntukylin) (sync)
[06:51] -queuebot:#ubuntu-release- Unapproved: gcc-bpf (groovy-proposed/universe) [3 => 4] (no packageset) (sync)
[06:51] -queuebot:#ubuntu-release- Unapproved: accepted gcc-bpf [sync] (groovy-proposed) [4]
[07:16] -queuebot:#ubuntu-release- Unapproved: vips (groovy-proposed/universe) [8.10.1-4 => 8.10.2-1] (no packageset) (sync)
[07:17] -queuebot:#ubuntu-release- Unapproved: accepted vips [sync] (groovy-proposed) [8.10.2-1]
[07:51] -queuebot:#ubuntu-release- Unapproved: accepted designate [source] (groovy-proposed) [1:11.0.0~rc1-0ubuntu1]
[07:52] -queuebot:#ubuntu-release- Unapproved: accepted calamares-settings-ubuntu [source] (groovy-proposed) [1:20.10.10]
[07:53] -queuebot:#ubuntu-release- Unapproved: accepted ukui-control-center [sync] (groovy-proposed) [3.0.1-1]
[07:54] -queuebot:#ubuntu-release- Unapproved: accepted gobject-introspection [sync] (groovy-proposed) [1.66.1-1]
[07:58] <mwhudson> hi release team, would any of you care to weigh in on the plan to reintroduce a bug to fix the server installer: https://bugs.launchpad.net/subiquity/+bug/1893818
[07:59] <mwhudson> apw, Laney, sil2100, vorlon, bdmurray, stgraber, tumbleweed: ^
[08:04] <apw> mwhudson, what is the downside of the bug being introduced; just those nodes existing and the risk of someone using them?
[08:05] <mwhudson> apw: the debian bug talks says 'I believe this causes problems further
[08:05] <mwhudson> down in the device stack / udev rule chain which then sometimes
[08:05] <mwhudson> doesn't create some device symlinks." but i don't know what they mean by that
[08:06] <mwhudson> the idea that anyone actually has expectations about what device mapper / udev do here that can then be violated seems a bit unlikely to me
[08:06] <mwhudson> vs just trying stuff and assuming what happens was what was intended
[08:06] <mwhudson> (but i may be a bit jaded)
[08:07] -queuebot:#ubuntu-release- Unapproved: jackd2 (groovy-proposed/main) [1.9.14-0ubuntu3 => 1.9.14-0ubuntu3.1] (i386-whitelist, ubuntustudio)
[08:07] <apw> well we are saying this makes it the same as the focal installer i assume
[08:07] <mwhudson> yes
[08:08] <apw> if the installer isn't working at all without the bug, and will if we go back to focal form, then that feels like a way forward.  sad that we are only finding out about it so near to release
[08:09] <cpaelzer> also I wanted to mention that the new multipath is in groovy-proposed since mid July and -release since August. So there might be an unknown amount of other packages that rely on the new behavior
[08:09] <paride> apw, we hit the bug only on s390x LPAR installs
[08:10] <cpaelzer> Debian even backported the fix to active releases, so we can expect that Debian-syncs and updates will rely on the new (fixed) behavior
[08:10] <Laney> what is the moving forward option?
[08:11] <apw> paride, indeed, but that is an automatable testing platform unlike snapdragon or something
[08:11] <apw> cpaelzer, a good point; that is a concern
[08:11] <sil2100> Laney: reintroducing bug #959727 is the proposed way forward, as this is what we had in focal
[08:11] <cpaelzer> Laney: option 1) re-break the udev rule to fix the installer, but break an unknown amount of other things Option 2) try to fix curtin/subiquity for the new behavior (short runway)
[08:12] <mwhudson> it would be an awful hack
[08:12] <Laney> yeah talking more about 2 and what that entails, by 'moving forwards' (vs. 'backwards' which is the (1) proposal)
[08:12] <mwhudson> but we could disable the problematic rule *only* in the server installer
[08:13] <mwhudson> (by just rm-ing it in livecd-rootfs)
[08:13] <cpaelzer> mwhudson: would that carry over to the installed system or just matter in the install-env?
[08:13] <mwhudson> cpaelzer: latter
[08:13] <cpaelzer> awful hack that works for now, reduces the risk and can later be replaced by a proper fix
[08:14] <mwhudson> yeah
[08:14] <amurray> sil2100: so re apparmor/groovy - the main changes are summarised in the changelog (previous patches now upstream, new leaf binary util) plus minor tweaks of some profiles
[08:14] <cpaelzer> to me that sounds better than the two options we had considered so far
[08:14] <mwhudson> i think so too
[08:15] <paride> I agree. What we don't want to do is to forget about it forever
[08:16] <Laney> the udev rule mentions a kernel parameter or an environment variable that you can set to skip it fwiw
[08:17] <sil2100> mwhudson: just in theory, how risky and how much work do you anticipate is needed in subiquity/curtin to cope with this properly?
[08:17] <sil2100> Out of curiosity
[08:17] <mwhudson> ah maybe setting the environment variable would be better then
[08:18] <mwhudson> sil2100: not sure, it's definitely a bit non-trivial
[08:30] <paride> anyway we do test a multipath install, I wonder why this is LPAR specific
[08:30] <paride> (the current test is amd64 only)
[08:30] <Laney> does subiquity have the chance to install such a udev rule (to set that env var) or will it need to be in the image?
[08:32] <paride> just tested: an s390x multipath install succeeds in a VM.
[08:36] <mwhudson> Laney: i think it needs to be in the image
[08:36] <mwhudson> paride: ah so the multipathed disk needs to have partitions to hit this bug
[08:37] <mwhudson> Laney: well practically speaking, of course subiquity runs as root so it could install the new rule and restart udevd but that would be even more gross i think
[08:38] <Laney> dear me
[08:38] <Laney> I mean yeah, you can udevadm trigger, but nooooo
[08:39] <Laney> I was more getting at whether it would be able to install the rule early enough to have it run at the proper time :-)
[08:40] <Laney> image is ok with me if that's the best way
[08:43] <mwhudson> no
[08:43] <mwhudson> it can't install the rule early enough
[08:43] <Laney> I suppose the snap is unpacked during boot which is already too late
[08:47] <mwhudson> exactly
[08:58] <paride> utah doesn't support exposing existing disk images as multipath devices, but it shouldn't be too difficult to do
[08:59] <paride> then testing a "reuse existing partitions on multipath device" scenario should hit this bug
[09:05] <mwhudson> paride: right
[09:05] <mwhudson> paride: need some kind of "scenario combiner" :)
[09:32] -queuebot:#ubuntu-release- Unapproved: nmap (groovy-proposed/universe) [7.80+dfsg1-5 => 7.91+dfsg1-1] (no packageset) (sync)
[09:33] -queuebot:#ubuntu-release- Unapproved: accepted nmap [sync] (groovy-proposed) [7.91+dfsg1-1]
[09:45] -queuebot:#ubuntu-release- Unapproved: gcc-snapshot (groovy-proposed/universe) [1:20200917-1ubuntu1 => 1:20201014-0ubuntu1] (i386-whitelist)
[09:46] -queuebot:#ubuntu-release- Unapproved: accepted gcc-snapshot [source] (groovy-proposed) [1:20201014-0ubuntu1]
[10:02] -queuebot:#ubuntu-release- New binary: linux-signed-bluefield [arm64] (focal-proposed/universe) [5.4.0-1006.8] (no packageset)
[10:09] -queuebot:#ubuntu-release- New: accepted linux-signed-bluefield [arm64] (focal-proposed) [5.4.0-1006.8]
[10:19] <xnox> Laney:  mwhudson: paride: sil2100: however, this multipath-tools improvement I guess also affects maas ephemeral environment, and I guess it doesn't matter there, as they always wipe all the partitions? Or would it trip things up there too, if it had to remove partitions from multipath?
[10:21] <xnox> and purging udev rule in livecd-rootfs for subiquity isos only will not help maas.
[10:21] <xnox> however, we can fix maas with SRUs later.
[10:23] <Laney> no idea, sounds like one to check with the maas team to me ;-)
[10:39] <xnox> pinged ~MAAS as I don't see mass-y people here
[10:41] <Laney> nice one
[11:07] -queuebot:#ubuntu-release- Unapproved: accepted jackd2 [source] (groovy-proposed) [1.9.14-0ubuntu3.1]
[11:20] -queuebot:#ubuntu-release- Unapproved: netplan.io (groovy-proposed/main) [0.100-0ubuntu4 => 0.100-0ubuntu5] (core)
[12:25] -queuebot:#ubuntu-release- Unapproved: ubiquity (groovy-proposed/main) [20.10.10 => 20.10.11] (desktop-core)
[12:33] -queuebot:#ubuntu-release- Unapproved: ubuntu-mate-artwork (groovy-proposed/universe) [20.10.0 => 20.10.1] (ubuntu-mate)
[12:39] <apw> l
[12:42] -queuebot:#ubuntu-release- Unapproved: ubuntu-mate-settings (groovy-proposed/universe) [20.10.0 => 20.10.1] (ubuntu-mate)
[12:54] -queuebot:#ubuntu-release- Unapproved: rejected sbsigntool [source] (bionic-proposed) [0.6-3.2ubuntu2.18.04.1]
[13:10] -queuebot:#ubuntu-release- Unapproved: rejected budgie-desktop [source] (focal-proposed) [10.5.1-6.1]
[13:10] -queuebot:#ubuntu-release- Unapproved: budgie-desktop (focal-proposed/universe) [10.5.1-6 => 10.5.1-6ubuntu0.1] (personal-fossfreedom, ubuntu-budgie)
[13:11] -queuebot:#ubuntu-release- Unapproved: accepted budgie-desktop [source] (focal-proposed) [10.5.1-6ubuntu0.1]
[13:21] -queuebot:#ubuntu-release- Unapproved: accepted indicator-applet [source] (focal-proposed) [12.10.2+20.04.20201004-0ubuntu1]
[13:26] -queuebot:#ubuntu-release- Unapproved: accepted prometheus-alertmanager [source] (focal-proposed) [0.15.3+ds-3ubuntu1]
[13:30] -queuebot:#ubuntu-release- Unapproved: accepted masakari [source] (focal-proposed) [9.0.0-0ubuntu0.20.04.3]
[13:44] -queuebot:#ubuntu-release- Unapproved: accepted accountsservice [source] (focal-proposed) [0.6.55-0ubuntu12~20.04.2]
[13:48] <rbasak> sil2100: there's an s390-tools 2.12.0-0ubuntu3.1 in the queue and also already accepted. Normally I'd just reject on the assumption that's been superseded, but there's a pocket copy and signing going on so I thought I'd just check first. Am I right in thinking it can be rejected?
[13:51] <sil2100> rbasak: no no, let me accept that
[13:52] <sil2100> Those were the signed bits
[13:52] <sil2100> (if that was what you were talking about)
[13:52] -queuebot:#ubuntu-release- Unapproved: accepted s390-tools [s390x] (focal-proposed) [2.12.0-0ubuntu3.1]
[13:52] <rbasak> Ah. Good thing I asked :)
[13:53] <sil2100> Forgot s390-tools-signed is a thing!
[13:53] <sil2100> So I didn't wait for those to pop up after accepting
[13:56] <sil2100> cpaelzer: hey! Do you want me to do the promotions from LP: #1891157 ?
[13:57] <sil2100> jibel: hey! Any progress with LP: #1898029 ?
[13:58] <jibel> sil2100, it's fixed in master, it'll be in next release of Ubiquity
[13:58] <jibel> waiting for another fix from Laney
[13:59] <sil2100> o/
[13:59] <Laney> it is in the queue
[13:59] <sil2100> Awesome
[13:59] <sil2100> Oh my, didn't see it! Excellent
[13:59] <sil2100> Let me review
[14:09] <sil2100> Looking sane
[14:10] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (groovy-proposed) [20.10.11]
[14:10] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-mate-artwork [source] (groovy-proposed) [20.10.1]
[14:11] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-mate-settings [source] (groovy-proposed) [20.10.1]
[14:23] -queuebot:#ubuntu-release- Unapproved: neutron (focal-proposed/main) [2:16.1.0-0ubuntu2 => 2:16.2.0-0ubuntu1] (openstack, ubuntu-server)
[14:25] <cpaelzer> sil2100: I thourght we said last time that didrocks will do it
[14:25] <cpaelzer> sil2100: let me recheck, but the answer likely is yes
[14:26] <cpaelzer> sil2100: yes, ack to promote golang-github-openprinting-goipp
[14:27] <didrocks> cpaelzer: did we? I didn’t track it and the last message was 09/10. Maybe we discussed it in yesterday’s MIR meeting but I don’t remember in that case :)
[14:28] <cpaelzer> didrocks: it doesn't matter who promotes it :-) - it is ready and can be done
[14:28] <didrocks> right, if I forgot about it, sorry, but I really have 0 memory of this, which scares me :)
[14:29] <didrocks> let me handle this now
[14:29] <didrocks> sil2100: ^
[14:29] <cpaelzer> didrocks: don't mind, it might as well be my bad memory
[14:30] <sil2100> \o/
[14:31] <didrocks> (done)
[14:47] -queuebot:#ubuntu-release- New binary: ubuntu-mate-artwork [amd64] (groovy-proposed/universe) [20.10.1] (ubuntu-mate)
[14:51] -queuebot:#ubuntu-release- Unapproved: gdm3 (groovy-proposed/main) [3.38.0-1ubuntu1 => 3.38.1-2ubuntu1] (desktop-core)
[15:08] <jdstrand> sil2100: hey, I know you and amurray have been talking about the aa3 upload. is there anything else you need?
[15:10] -queuebot:#ubuntu-release- Unapproved: rejected bind9 [source] (focal-proposed) [1:9.16.1-0ubuntu2.4]
[15:11] -queuebot:#ubuntu-release- Unapproved: bind9 (focal-proposed/main) [1:9.16.1-0ubuntu2.3 => 1:9.16.1-0ubuntu2.4] (core, i386-whitelist)
[15:14] -queuebot:#ubuntu-release- Unapproved: accepted bind9 [source] (focal-proposed) [1:9.16.1-0ubuntu2.4]
[15:15] <Laney> jdstrand: sil2100: I'll review that one if you like (unless you already started)
[15:16] -queuebot:#ubuntu-release- Unapproved: flash-kernel (groovy-proposed/main) [3.100ubuntu3 => 3.100ubuntu4] (core)
[15:17] <vorlon> sil2100: https://code.launchpad.net/~xubuntu-dev/ubuntu-seeds/+git/xubuntu/+merge/392239
[15:17] <sil2100> I started looking at it, but feel free to take over o/ There's also netplan.io and flash-kernel that I'd like someone to review and accept
[15:17] <sil2100> vorlon: awesome, looking
[15:17] <jdstrand> Laney: amurray may have provided additional context in backscroll. I had this to say right after uploading: 10:27 < jdstrand> fyi, we consider the apparmor upload bug fix. we got aa3 beta in, with patches a while ago. this is aa3 final without those patches (and a few others). there is a new aa-features-abi command that is arguably a new feature, but it is a very small, convenience leaf utility
[15:17] <jdstrand> not used by anything else, so I didn't think it needed an ffe
[15:18] <Laney> alright, cheers
[15:18] <Laney> just getting the patches applied view was quite helpful
[15:19] <Laney> woah, a manually written manpage
[15:19] <jdstrand> Laney: it looks like the most interesting thing wrt from amurray was: 03:14 < amurray> sil2100: so re apparmor/groovy - the main changes are summarised in the changelog (previous patches now upstream, new leaf binary util) plus minor tweaks of some profiles
[15:20] <jdstrand> Laney: at this time of day, if you have specific questions outside of the packaging, I suggest asking jjohansen
[15:21] <jdstrand> well, that said, he isn't here and I think he might've gone offline
[15:23] <Laney> No worries, I'll find someone if necessary
[15:25] <jdstrand> thanks!
[15:29] <jdstrand> Laney: ok, I'm not sure why gitlab doesn't have a tag for beta1, but you might find this helpful as well: https://gitlab.com/apparmor/apparmor/-/commits/master/. Sept 22 through Oct 1 inclusive has the upstream commits from beta to final (and a number of those we pulled in as patches for what is in groovy now that we dropped in the upload)
[15:32] <tjaalton> some nodejs tests are now failing because phantomjs is missing?
[15:33] <jdstrand> Laney: sorry, I believe the start commit is 5a31e943 on Sept 18
[15:34] <jdstrand> (the beta orig.tar.gz does not have that, but has the one before)
[15:37] <icey> can the upload of Neutron that's in the focal queue be rejected please, it needs another change for re-upload
[15:43] <tjaalton> so, since phantomjs is now gone, jquery.sparkline, node-headjs, node-platform need to be badtested
[15:58] -queuebot:#ubuntu-release- Unapproved: accepted apparmor [source] (groovy-proposed) [3.0.0-0ubuntu1]
[15:58] -queuebot:#ubuntu-release- Unapproved: accepted shared-mime-info [sync] (groovy-proposed) [2.0-1]
[16:08] <jdstrand> thanks Laney :)
[16:21] <Laney> jdstrand: np!
[16:21] <Laney> WCPGW?
[16:21] <jdstrand> hehe
[16:21] <jdstrand> it should be 'nothing' and 'only better' :)
[16:21] <jdstrand> we'll obviously be responsive if that is not the case
[16:22]  * jdstrand is glad we did beta as an FFe earlier in the cycle so this update is incremental
[16:23] <Laney> indeed, I think the full update right now would be untenable
[16:28] -queuebot:#ubuntu-release- Unapproved: python-bleach (groovy-proposed/universe) [3.1.5-2 => 3.2.1-1] (no packageset) (sync)
[16:28] <jamespage> sync of python-bleach into groovy ^^ will unblock the html5lib currently stuck in proposed
[16:28] -queuebot:#ubuntu-release- Unapproved: accepted python-bleach [sync] (groovy-proposed) [3.2.1-1]
[16:30] -queuebot:#ubuntu-release- Unapproved: mariadb-10.3 (groovy-proposed/universe) [1:10.3.24-2 => 1:10.3.25-0ubuntu1] (kubuntu)
[16:45] -queuebot:#ubuntu-release- Unapproved: ubuntu-settings (groovy-proposed/main) [20.10.2 => 20.10.3] (ubuntu-desktop)
[16:53] -queuebot:#ubuntu-release- Unapproved: accepted flash-kernel [source] (groovy-proposed) [3.100ubuntu4]
[16:54] -queuebot:#ubuntu-release- Unapproved: accepted netplan.io [source] (groovy-proposed) [0.100-0ubuntu5]
[16:54] -queuebot:#ubuntu-release- Unapproved: accepted mariadb-10.3 [source] (groovy-proposed) [1:10.3.25-0ubuntu1]
[17:29] -queuebot:#ubuntu-release- Unapproved: clevis (bionic-proposed/universe) [8-1ubuntu0.1 => 8-1ubuntu0.2] (no packageset)
[17:29] -queuebot:#ubuntu-release- Unapproved: clevis (focal-proposed/universe) [12-1ubuntu2.1 => 12-1ubuntu2.2] (no packageset)
[18:41] <mwhudson> xnox: does maas use the curtin.storage_config stuff? i didn't think it did
[18:43] -queuebot:#ubuntu-release- Unapproved: libfm-qt (groovy-proposed/universe) [0.15.1-0ubuntu2 => 0.15.1-0ubuntu3] (lubuntu)
[18:57] -queuebot:#ubuntu-release- New: accepted r-bioc-monocle [sync] (groovy-proposed) [2.16.0-2]
[18:57] -queuebot:#ubuntu-release- New: accepted r-cran-hdf5r [sync] (groovy-proposed) [1.3.3+dfsg-2]
[18:57] -queuebot:#ubuntu-release- New: accepted sagemath [amd64] (groovy-proposed) [9.2~beta12-1]
[18:57] -queuebot:#ubuntu-release- New: accepted ubuntu-mate-artwork [amd64] (groovy-proposed) [20.10.1]
[19:08] -queuebot:#ubuntu-release- New binary: r-cran-hdf5r [amd64] (groovy-proposed/none) [1.3.3+dfsg-2] (no packageset)
[19:08] -queuebot:#ubuntu-release- New binary: r-cran-hdf5r [s390x] (groovy-proposed/none) [1.3.3+dfsg-2] (no packageset)
[19:08] -queuebot:#ubuntu-release- New binary: r-cran-hdf5r [ppc64el] (groovy-proposed/none) [1.3.3+dfsg-2] (no packageset)
[19:09] -queuebot:#ubuntu-release- New binary: r-cran-hdf5r [arm64] (groovy-proposed/none) [1.3.3+dfsg-2] (no packageset)
[19:09] -queuebot:#ubuntu-release- New binary: r-cran-hdf5r [armhf] (groovy-proposed/none) [1.3.3+dfsg-2] (no packageset)
[19:23] -queuebot:#ubuntu-release- New binary: r-cran-hdf5r [riscv64] (groovy-proposed/universe) [1.3.3+dfsg-2] (no packageset)
[19:23] -queuebot:#ubuntu-release- Unapproved: ec2-hibinit-agent (groovy-proposed/main) [1.0.0-0ubuntu9 => 1.0.0-0ubuntu11] (core)
[19:24] <rbalint> ^stability fixes to be sru-d, too
[19:24] <rbalint> ^fginther,
[19:31] <mwhudson> vorlon, Laney, apw, sil2100, etc: https://code.launchpad.net/~mwhudson/livecd-rootfs/+git/livecd-rootfs/+merge/392248
[19:31] <mwhudson> oh hm should add changelog
[19:37] -queuebot:#ubuntu-release- New sync: r-cran-proxy (groovy-proposed/primary) [0.4-24-2]
[19:40] -queuebot:#ubuntu-release- Unapproved: cd-boot-images-amd64 (groovy-proposed/main) [8 => 9] (desktop-core)
[19:47] <vorlon> mwhudson: why is this done in livecd-rootfs rather than in multipath-tools?
[19:48] <mwhudson> vorlon: because the discussion here yesterday was that it was less risky to do it in the installer live session only
[19:48] <vorlon> ok
[19:49] <mwhudson> which i think i agree with -- i don't think it would in fact break anything to do it in multipath-tools but why risk it
[19:51] <vorlon> mwhudson: approved then
[19:51] <mwhudson> vorlon: thanks
[19:51] <mwhudson> vorlon: i was doing a ppa build in prep for a test build but given the timing shall we test in prod?
[19:55] <vorlon> mwhudson: I'm good with test in prod
[19:56] -queuebot:#ubuntu-release- Unapproved: pitivi (groovy-proposed/universe) [2020.09-1 => 2020.09.1-1] (no packageset) (sync)
[19:56] <mwhudson> ok uploading
[19:56] <mwhudson> i'll ping you when it migrates to start an iso build
[19:57] -queuebot:#ubuntu-release- Unapproved: accepted pitivi [sync] (groovy-proposed) [2020.09.1-1]
[19:57] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (groovy-proposed/main) [2.690 => 2.691] (desktop-core, i386-whitelist)
[20:01] <mwhudson> vorlon: well of course you need to accept it first :)
[20:10] -queuebot:#ubuntu-release- New: accepted r-cran-hdf5r [amd64] (groovy-proposed) [1.3.3+dfsg-2]
[20:10] -queuebot:#ubuntu-release- New: accepted r-cran-hdf5r [armhf] (groovy-proposed) [1.3.3+dfsg-2]
[20:10] -queuebot:#ubuntu-release- New: accepted r-cran-hdf5r [riscv64] (groovy-proposed) [1.3.3+dfsg-2]
[20:10] -queuebot:#ubuntu-release- New: accepted r-cran-proxy [sync] (groovy-proposed) [0.4-24-2]
[20:10] -queuebot:#ubuntu-release- New: accepted r-cran-hdf5r [arm64] (groovy-proposed) [1.3.3+dfsg-2]
[20:10] -queuebot:#ubuntu-release- New: accepted r-cran-hdf5r [s390x] (groovy-proposed) [1.3.3+dfsg-2]
[20:10] -queuebot:#ubuntu-release- New: accepted r-cran-hdf5r [ppc64el] (groovy-proposed) [1.3.3+dfsg-2]
[20:12] -queuebot:#ubuntu-release- New binary: r-cran-proxy [s390x] (groovy-proposed/none) [0.4-24-2] (no packageset)
[20:13] -queuebot:#ubuntu-release- New binary: r-cran-proxy [amd64] (groovy-proposed/none) [0.4-24-2] (no packageset)
[20:13] -queuebot:#ubuntu-release- New binary: r-cran-proxy [ppc64el] (groovy-proposed/none) [0.4-24-2] (no packageset)
[20:14] -queuebot:#ubuntu-release- New binary: r-cran-proxy [arm64] (groovy-proposed/universe) [0.4-24-2] (no packageset)
[20:14] -queuebot:#ubuntu-release- New binary: r-cran-proxy [armhf] (groovy-proposed/universe) [0.4-24-2] (no packageset)
[20:15] <vorlon> mwhudson: accepted
[20:15] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (groovy-proposed) [2.691]
[20:20] -queuebot:#ubuntu-release- New: accepted r-cran-proxy [amd64] (groovy-proposed) [0.4-24-2]
[20:20] -queuebot:#ubuntu-release- New: accepted r-cran-proxy [armhf] (groovy-proposed) [0.4-24-2]
[20:20] -queuebot:#ubuntu-release- New: accepted r-cran-proxy [s390x] (groovy-proposed) [0.4-24-2]
[20:20] -queuebot:#ubuntu-release- New: accepted r-cran-proxy [arm64] (groovy-proposed) [0.4-24-2]
[20:20] -queuebot:#ubuntu-release- New: accepted r-cran-proxy [ppc64el] (groovy-proposed) [0.4-24-2]
[20:27] -queuebot:#ubuntu-release- New binary: r-cran-proxy [riscv64] (groovy-proposed/universe) [0.4-24-2] (no packageset)
[20:32] -queuebot:#ubuntu-release- Unapproved: cctools (groovy-proposed/universe) [7.1.2-1ubuntu1 => 7.1.2-2] (no packageset) (sync)
[20:32] -queuebot:#ubuntu-release- Unapproved: accepted cctools [sync] (groovy-proposed) [7.1.2-2]
[20:37] -queuebot:#ubuntu-release- Unapproved: cctools (groovy-proposed/universe) [7.1.2-1ubuntu1 => 7.1.2-2ubuntu1] (no packageset)
[20:37] -queuebot:#ubuntu-release- Unapproved: accepted cctools [source] (groovy-proposed) [7.1.2-2ubuntu1]
[22:49] <amurray> Laney: thanks re apparmor/groovy :)
[23:24] <mwhudson> ha, *now* i'm getting waiting for approvals mails for all my uploads for the last few weeks
[23:26] -queuebot:#ubuntu-release- Unapproved: calamares-settings-ubuntu (groovy-proposed/universe) [1:20.10.10 => 1:20.10.11] (lubuntu, ubuntustudio)
[23:40] -queuebot:#ubuntu-release- Unapproved: calamares-settings-ubuntu (focal-proposed/universe) [1:20.04.2 => 1:20.04.2.1] (lubuntu)
[23:47] <cjwatson> mwhudson: Yep, just got the postfix config fixed.  Sorry for the inconvenience
[23:48] <cjwatson> (I wasn't sure whether mail would have been lost or queued)