[10:59] -queuebot:#ubuntu-release- Unapproved: accepted thermald [source] (hirsute-proposed) [2.4.3-1ubuntu1]
[11:00] <sil2100> laney: hey hey! re: the autopkgtest staging deployment of the private esm stuffs - how are things going? Guess the changes are okayish for testing now, right?
[11:00] <laney> sil2100: should be as I left it on Friday
[11:00] <laney> so, yeah
[11:12] <sil2100> Ooooh! I see a lot of fixes from you from Friday! Thanks!
[11:19] <sil2100> Now I read the backlog, thanks a lot! Will start experimenting with the britney branch of mine
[11:22] <laney> sil2100: probably want to try a request, see if it all goes through fine and you can view it in the end
[11:43] <sil2100> laney: will do!
[11:43] <sil2100> jamespage: hey! Did you see my comment in: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1929179/comments/1 ?
[11:49] -queuebot:#ubuntu-release- Unapproved: accepted ubuntustudio-menu [source] (focal-proposed) [0.38.1]
[12:44] <jamespage> sil2100_: looking now
[12:45] <jamespage> sil2100_: mdeslaur ^^ what do you think? that point release is mainly CVE AFAICT
[12:46] <mdeslaur> jamespage, sil2100_ yes, building it as a security update would be ideal
[12:47] <sil2100> mdeslaur, mdeslaur: basically in that case it would be good to build that in a security PPA and then bin-copy to -proposed
[12:47] <mdeslaur> jamespage: I can stick it in the security team PPA, just let me know where it is
[12:52] <jamespage> mdeslaur: OK
[12:53] <jamespage> mdeslaur: they will appear in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3535 shortly
[12:54] <mdeslaur> ok
[13:02] <sil2100> Hey guys! Does anyone remember what's the situation with ubuntu backports?
[13:03] <rbasak> IIRC, the backporters team is inactive, and we don't have anyone currently looking to take it on.
[13:03] <rbasak> teward did ask a while back, but AIUI the lack of response to his request never got addressed, and he's no longer available to take it on.
[13:05] <rbasak> Meanwhile I think a couple of AAs have been backporting their own packages into there bypassing the backporters team, which isn't great but understandable given the circumstances.
[13:11] -queuebot:#ubuntu-release- Unapproved: accepted initramfs-tools [source] (focal-proposed) [0.136ubuntu6.6]
[13:33] <jibel> doko, sil2100 what is blocking sssd in focal-proposed from being published to -updates?
[13:34] <jibel> we have another sru of sssd that we'd like to upload
[13:43] <rbasak> jibel: looks like nothing - the change is staged and won't land until the next SRU. Docs at https://wiki.ubuntu.com/StableReleaseUpdates#Staging_low_priority_uploads and https://wiki.ubuntu.com/StableReleaseUpdates#Staging_an_upload. That means you can just go ahead and upload an SRU based on  2.2.3-3ubuntu0.5
[13:49] <doko> jibel, yes, just do another SRU on top of it, if needed
[13:50] <doko> or wait for the migration
[13:51] <rbasak> It won't get released on its own - there's no point, and it's disruptive to users.
[13:51] <rbasak> The idea is to prepare the new SRU on top and release the two changes together.
[13:54] <jibel> rbasak, doko , understood. thanks
[13:55] <doko> rbasak, how can I see that "It won't get released on its own"?
[13:55] <rbasak> doko: it's tagged block-proposed-focal, and there's a label on the pending-sru page
[13:59] <rbasak> doko: https://lists.ubuntu.com/archives/ubuntu-devel/2019-August/040791.html and https://lists.ubuntu.com/archives/ubuntu-devel/2019-October/040835.html was the original discussion. I tried to make sure it's documented well. If there's something remaining unexplained I'd appreciate feedback to improve the docs on this.
[14:57] -queuebot:#ubuntu-release- Unapproved: sssd (focal-proposed/main) [2.2.3-3ubuntu0.5 => 2.2.3-3ubuntu0.6] (ubuntu-desktop, ubuntu-server)
[14:57] <didrocks> rbasak: FYI, here is then sssd uploaded with -v ^
[15:23] <LocutusOfBorg> archive-admins, are we ready to remove php7.4 and let the transition finish?
[15:23] <LocutusOfBorg> migrating php-common/2:82~0build1/i386 to testing makes php7.4-common/7.4.16-1ubuntu2/i386 uninstallable
[15:23] <LocutusOfBorg> utkarsh2102, ^^
[15:24] <utkarsh2102> LocutusOfBorg: yep, I was waiting for vorlon to start their day, since we've been discussing back-and-forth.
[15:24] <LocutusOfBorg> yay!
[15:24] <LocutusOfBorg> looks like in one britney run we will have a better picture
[15:25] <utkarsh2102> LocutusOfBorg: see LP: #1927264.
[15:26] <LocutusOfBorg> and then sync php8.0, right?
[15:26] <utkarsh2102> I am also waiting for phpseclib, which you sponsored, to be updated on the excuses page. So the only blocker will also turn green and the only thing that'll be left is only php7.4 which can be removed & php8.0 will transition.
[15:28] <utkarsh2102> also, as the bug states, I'll file an MP to add the hints so that php-defaults complete its transition and everything should fall into its place.
[15:29] <LocutusOfBorg> vorlon, what about just removing php7.4-common binary? it might work and let britney do its thing (together with badtesting php7.4 autopkgtests)
[15:29] <LocutusOfBorg> after one run we can just remove the whole php7.4 maybe?
[16:28] <juliank> oh laney, I added the sys.stderr blocking change to autopkgtest for autopkgtest-virt-ssh last week, should check logs if we still see that weird error when writing to sys.stderr
[16:28] <juliank> when I did the phased updates fix
[16:28] <juliank> gotta forward it if it helped
[16:32] <juliank> journalctl too slow
[17:05] <juliank> oh yeah, apparently it did not help either
[17:05] <juliank> sooo weird
[17:06]  * juliank was distracted by just whipping out a new spec
[17:15] <laney> bah what
[17:18] -queuebot:#ubuntu-release- Unapproved: strongswan (bionic-proposed/main) [5.6.2-1ubuntu2.5 => 5.6.2-1ubuntu2.6] (ubuntu-server)
[17:21] <juliank>                                                                                                                File "/home/ubuntu/autopkgtest/virt/autopkgtest-virt-ssh", line 208, in execute_setup_script
[17:21] <juliank>                                                                                                                  sys.stderr.write(err)
[17:21] <juliank>                                                                                                              BlockingIOError: [Errno 11] write could not complete without blocking
[17:21] <juliank> bad paste
[17:22] <juliank> something is broken in Python IMO
[17:34] -queuebot:#ubuntu-release- New binary: hg-git [amd64] (impish-proposed/universe) [0.10.1-1] (no packageset)
[19:22] <utkarsh2102> vorlon: have an opinion on what steps for php8.0 would you want us to follow?
[19:22] <utkarsh2102> LocutusOfBorg suggested few things, too^^
[19:24] <sergiodj> PSA: I will upload openldap 2.5.5 to the archive.  it will introduce a new binary package for the library, and will start a somewhat large transition (100+ packages affected)
[19:25] <sergiodj> I have extensively tested and made sure that everything is building & the tests are passing, but there may be some small bumps here and there, of course
[19:55] -queuebot:#ubuntu-release- New binary: openldap [s390x] (impish-proposed/main) [2.5.5+dfsg-1~exp1ubuntu1] (i386-whitelist, ubuntu-server)
[19:56] -queuebot:#ubuntu-release- New binary: openldap [amd64] (impish-proposed/main) [2.5.5+dfsg-1~exp1ubuntu1] (i386-whitelist, ubuntu-server)
[19:56] -queuebot:#ubuntu-release- New binary: openldap [i386] (impish-proposed/main) [2.5.5+dfsg-1~exp1ubuntu1] (i386-whitelist, ubuntu-server)
[19:57] -queuebot:#ubuntu-release- New binary: openldap [ppc64el] (impish-proposed/main) [2.5.5+dfsg-1~exp1ubuntu1] (i386-whitelist, ubuntu-server)
[20:12] -queuebot:#ubuntu-release- New binary: openldap [armhf] (impish-proposed/main) [2.5.5+dfsg-1~exp1ubuntu1] (i386-whitelist, ubuntu-server)
[20:14] -queuebot:#ubuntu-release- New binary: openldap [arm64] (impish-proposed/main) [2.5.5+dfsg-1~exp1ubuntu1] (i386-whitelist, ubuntu-server)
[20:36] -queuebot:#ubuntu-release- New binary: openldap [riscv64] (impish-proposed/main) [2.5.5+dfsg-1~exp1ubuntu1] (i386-whitelist, ubuntu-server)
[20:56] <sergiodj> ubuntu-archive: hey, could you please process the new openldap 2.5.5?  TIA
[20:58] <vorlon> LocutusOfBorg: php-defaults vs phpseclib/armhf?
[20:58] <vorlon> LocutusOfBorg: my comment on the bug report was that we should force php-defaults once php7.4 is the only hold-up, then remove php7.4
[20:59] <vorlon> but there's still an outstanding, unhinted autopkgtest regression for phpseclib
[21:00] <vorlon> sergiodj: why are we merging openldap from experimental?  Have you done a rebuild test to confirm this is going to go smoothly and not clog up proposed-migration for months?
[21:00] <vorlon> (> 120 reverse-build-depends in the archive)
[21:01] <sergiodj> vorlon: we're merging because I'd like to start the transition ASAP.  yes, I have done extensive tests to make sure that all rdeps are fine (modulo a few packages that are already broken in the archive)
[21:01] <vorlon> ok
[21:01] <vorlon> accepted
[21:02] <sergiodj> Debian will not have openldap in unstable for the foreseeable future, and we need to start the transition in Ubuntu because we'd like to have openldap 2.5.5 in impish
[21:02] <sergiodj> vorlon: thanks!
[21:02] -queuebot:#ubuntu-release- New: accepted openldap [amd64] (impish-proposed) [2.5.5+dfsg-1~exp1ubuntu1]
[21:02] -queuebot:#ubuntu-release- New: accepted openldap [armhf] (impish-proposed) [2.5.5+dfsg-1~exp1ubuntu1]
[21:02] -queuebot:#ubuntu-release- New: accepted openldap [ppc64el] (impish-proposed) [2.5.5+dfsg-1~exp1ubuntu1]
[21:02] -queuebot:#ubuntu-release- New: accepted openldap [s390x] (impish-proposed) [2.5.5+dfsg-1~exp1ubuntu1]
[21:02] -queuebot:#ubuntu-release- New: accepted openldap [arm64] (impish-proposed) [2.5.5+dfsg-1~exp1ubuntu1]
[21:02] -queuebot:#ubuntu-release- New: accepted openldap [riscv64] (impish-proposed) [2.5.5+dfsg-1~exp1ubuntu1]
[21:02] -queuebot:#ubuntu-release- New: accepted openldap [i386] (impish-proposed) [2.5.5+dfsg-1~exp1ubuntu1]