[02:38] <amurray> RAOF: hey any chance you could take a look at my squashfs-tools SRU for bionic which is currently sitting in unapproved?
[02:42] <RAOF> amurray: Let me take a look.
[02:42] <amurray> thanks
[03:10] -queuebot:#ubuntu-release- Unapproved: accepted squashfs-tools [source] (bionic-proposed) [1:4.3-6ubuntu0.18.04.2]
[03:42] <amurray> thanks RAOF :)
[08:12] <utkarsh2102> o/
[08:12] <utkarsh2102> cjwatson: hello, are you around today?
[08:18] <utkarsh2102> also, doko_: if you're around, could you accept php-symfony-contracts from NEW? TIA!
[08:37] <laney> o/
[08:37] <laney> xnox: julian_k told me to get you to fill me in on something something kernel arm64 bos01
[08:38] <laney> :-)
[08:38] <laney> if hangout is better that's ok with me toooooooooooooooooooooo
[08:46] <cjwatson> utkarsh2102: ?
[08:46] <utkarsh2102> cjwatson: hey, I was gonna ask about the bootstrap thingy for symfony, whenever you have time.
[08:47] <cjwatson> utkarsh2102: So it sounds like LocutusOfBorg took over?
[08:49] <cjwatson> Or something, I couldn't really tell from backlog
[08:49] <utkarsh2102> cjwatson: ah, ok then, I am still confused.
[08:49] <utkarsh2102> if LocutusOfBorg has those "powers" to do that, then all well, I guess
[08:49] -queuebot:#ubuntu-release- New: accepted php-symfony-contracts [amd64] (impish-proposed) [2.4.0-1ubuntu1]
[08:49] -queuebot:#ubuntu-release- New: accepted php-symfony-contracts [amd64] (impish-proposed) [2.4.0-1ubuntu2]
[08:50] <utkarsh2102> yay, thank you!^
[08:50] <cjwatson> utkarsh2102: No, they were presumably ignoring / not noticing the previous conversation and doing it by stuffing in fake binaries or similar
[08:50] <cjwatson> utkarsh2102: They don't have access to do it the way I was working on
[08:50] <cjwatson> utkarsh2102: So where are we following php-symfony-contracts?
[08:52] <utkarsh2102> cjwatson: with php-symfony-contracts accepted, it's just a matter of giving back 3 builds and we're ready for continuing where we left off.
[08:53] <utkarsh2102> can you please give back: https://launchpad.net/ubuntu/+source/php-async-aws-core/1.10.0-1/+build/21595098? (it need php-symfony-contracts which has now been accepted)
[08:57] <utkarsh2102> oh well, it looks like it needs some time after the package has been accepted. how long should it take?
[08:57] <utkarsh2102> roughly^
[09:04] <cjwatson> utkarsh2102: However long a piece of string is^W^W^W^W^Wit takes for the publisher to run
[09:06] <cjwatson> Also my accepts just missed the start of the run currently in progress
[09:09] <utkarsh2102> cjwatson: alrighty, thank you! as soon as I am able to build php-async-aws-core in my sbuild, probably that'd be a good time to re-trigger that build, I guess. So I'll let you know.
[09:16]  * utkarsh2102 hopes he didn't miss any message :/
[09:18] <LocutusOfBorg> cjwatson, I was talking about copying stuff in bileto for bootstrapping symfony not accepting from new queue :)
[09:19] <cjwatson> LocutusOfBorg: I know, but on Friday or so I was doing this via bootstrap-package
[09:20] <cjwatson> As opposed to via bileto
[09:20] <cjwatson> We just had to stop because the bootstrapping process hit a bug in one of the involved packages which had to be fixed before proceeding
[09:21] <LocutusOfBorg> oh I wasn't aware of this new stuff :)
[09:22] <LocutusOfBorg> so I won't use bileto anymore for this package
[09:22] <cjwatson> I just didn't know where you'd got to, that's all
[09:22]  * cjwatson waits for the next publisher run
[09:37] -queuebot:#ubuntu-release- New binary: php-async-aws-core [amd64] (impish-proposed/universe) [1.10.0-1] (no packageset)
[10:04] -queuebot:#ubuntu-release- New: accepted php-async-aws-core [amd64] (impish-proposed) [1.10.0-1]
[10:26] <utkarsh2102> thanks for accepting php-async-aws-core! \o/
[10:26] <utkarsh2102> almost there now!
[10:26] <utkarsh2102> needs one more rebuild
[10:28] -queuebot:#ubuntu-release- New binary: php-async-aws-ses [amd64] (impish-proposed/universe) [1.4.0-1] (no packageset)
[10:28] <utkarsh2102> yet another^ :)
[10:28] <utkarsh2102> last re-trigger needed: https://launchpad.net/ubuntu/+source/php-async-aws-sqs/1.5.0-1/+build/21595086
[10:28] <utkarsh2102> thanks, LocutusOfBorg \o/
[10:31] -queuebot:#ubuntu-release- New: accepted php-async-aws-ses [amd64] (impish-proposed) [1.4.0-1]
[10:31] <utkarsh2102> thank you!
[10:32] -queuebot:#ubuntu-release- New binary: php-async-aws-sqs [amd64] (impish-proposed/universe) [1.5.0-1] (no packageset)
[10:35] <cjwatson> utkarsh2102: OK, so what follows these php-async-* builds?
[10:35] <cjwatson> Or is that it?
[10:35] -queuebot:#ubuntu-release- New: accepted php-async-aws-sqs [amd64] (impish-proposed) [1.5.0-1]
[10:41] <utkarsh2102> cjwatson: everything should be ready, let me just do a quick check of php-email-validator, else we're good to go
[10:48] <cjwatson> utkarsh2102: Good to go as in bootstrap done, or good to go as in I can go back and retry the bootstrap-package step?
[10:50] <utkarsh2102> cjwatson: good to go as in you can perform your step (the one you did on Friday) here -> ppa:utkarsh/symfony-bootstrap
[10:50] <utkarsh2102> that is, retry the bootstrap-package step but with my PPA^ :)
[10:52] <cjwatson> utkarsh2102: Does it need that php-email-validator build to publish in your PPA first?
[10:54] <utkarsh2102> cjwatson: Impish already has php-email-validator built, but just to be on the safe side, I've uploaded to my PPA as well (the rebuild has been sponsored by LocutusOfBorg, too). So I'd say let's wait a couple of minutes for it to be published and then you can wave your magic wand.
[10:54] <utkarsh2102> I'm keeping an eye on this and will let you know here once it's done!
[10:54] <cjwatson> PPA publishing is typically slower, may well be more than a couple of minutes
[10:54] <cjwatson> But I don't see the point in the "to be on the safe side" there
[10:55] <cjwatson> If anything it's more confusing than not to have the same version number built independently and available from two places
[10:56] <cjwatson> So I think it would be better to just wait until https://launchpad.net/ubuntu/+source/php-email-validator/3.1.1-2build1/+build/21629037 has finished publishing and ignore that PPA build
[10:56] <utkarsh2102> yeah, I thought I'd not let this get delayed but didn't knew Gianfranco would be really fast to sponsor.
[10:56] <utkarsh2102> absolutely, I agree
[10:57] <utkarsh2102> cjwatson: should I "delete" the package from PPA to make it less confusing, et al?
[10:59] <LocutusOfBorg> how do we deal with https://launchpad.net/ubuntu/+source/php-twig/3.3.2-1ubuntu1/+build/21599499 ?
[11:00] <cjwatson> utkarsh2102: I would, yes
[11:01] <utkarsh2102> LocutusOfBorg: that looks like another patch we'll need at some point, ugh
[11:02] <utkarsh2102> cjwatson: ok, done! \o/
[11:03] <utkarsh2102> cjwatson: also looks like https://launchpad.net/ubuntu/+source/php-email-validator/3.1.1-2build1/+build/21629037 is done & ready
[11:04] <cjwatson> utkarsh2102: Still "awaiting publication"
[11:04] <utkarsh2102> my bad, apologies!
[11:08] <utkarsh2102> Binary packages produced by this build: [...]; woot!
[11:09] <cjwatson> Yeah, still need to wait for the publisher to actually finish though.
[11:09] <cjwatson> I'm tailing logs
[11:09] <utkarsh2102> aha!
[11:09] <cjwatson> There's a stage where the DB row is marked as published but the package isn't quite fully on disk yet.
[11:10] <utkarsh2102> aah, I see
[11:10] <utkarsh2102> TIL! :)
[11:18] <cjwatson> utkarsh2102: bootstrapping now
[11:21] <cjwatson> Hm
[11:21] <cjwatson> utkarsh2102: Oh right - could you reconfigure that PPA to use -proposed please?  https://launchpad.net/~utkarsh/+archive/ubuntu/symfony-bootstrap/+edit-dependencies
[11:22] <utkarsh2102> cjwatson: ah, done!
[11:23] <utkarsh2102> should I retry as well?
[11:24] <cjwatson> I've done that
[11:24] <utkarsh2102> awesome, thanks
[11:24] <utkarsh2102> starts in 3 minutes
[11:24] <utkarsh2102> *fingers-crossed*
[11:28] <utkarsh2102> ugh
[11:31] <utkarsh210274> I'll never know how libera shows utkarsh2102 is already in use and assigned me this but whatever.
[11:32] <utkarsh210274> cjwatson: I'll work on fixing the new problems; looks like symfony itself needs a patch
[11:32] <utkarsh210274> thanks a bunch for your help! <3
[11:34] <cjwatson> utkarsh2102: right, no problem
[11:34] <utkarsh2102> \o/
[11:34] <cjwatson> Let me know when you have more buttons for me to push
[11:35] <utkarsh2102> absolutely, thanks!
[11:36] <utkarsh2102> not having core-dev powers will result in even more requests for re-triggers and re-builds, etc :)
[12:17] <utkarsh210228> cjwatson: hey, would you be interested in sponsoring a couple of fixes, too, for symfony thingy? :)
[12:29] <cjwatson> utkarsh2102: can do
[12:32] <utkarsh2102> cjwatson: awesome, thank you! here's everything you'll need: https://people.debian.org/~utkarsh/ubuntu/php-cache-integration-tests/
[12:52] <cjwatson> utkarsh2102: LGTM, uploaded
[12:52] <utkarsh2102> cjwatson: awesome, thank you!
[13:39] <icey> hey, there's been a point release of Neutron in the Groovy queue for almost two weeks now, wonder if that could get pushed forward? https://launchpad.net/ubuntu/groovy/+queue?queue_state=1&queue_text=neutron
[14:39] <seb128> SRU team, you can reject gupnp/focal from the queue, it has been waiting since april and now has been superseeded by a security update. That kind of situation is quite frustrating, do we understand why we get so long delay for reviews nowadays and how that can be addressed? (unsure what would be the right place for that disucssion, ubuntu-devel@?)
[14:52] <rbasak> seb128: I thought this was one of the GNOME MRE requests that hasn't been approved in the exception list yet?
[14:54] <rbasak> seb128: SRU documention for an MRE needs to either contain the information required by https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases, or link to an existing standing approval given by the SRU team, or contain a full justification and request for an exception.
[14:55] <seb128> rbasak, how am I supposed to know that without bug comment nor email/ping nor reject?
[14:55] <rbasak> This bug had none of the above, so I assumed it was one of the ones under discussion at https://discourse.ubuntu.com/t/scope-of-gnome-mru/18041/25 and pending a conclusion. I'm surprised you were expecting it to be processed in some other way.
[14:56] <seb128> rbasak, to me it's part of GNOME and has been handled like that for ever, those uniateral changes or policy are bit confusing
[14:57] <seb128> it wouldn't hurt to state on the bug when you think an update isn't consider as a valid GNOME one from SRU side
[14:57] <seb128> getting those silently sit in the queue isn't helping anyone, neither the SRU team nor the uploader nor the users waiting for the fix
[14:57] <rbasak> seb128: I'm sorry there's a mismatch of expectation here. I've never handled a GNOME MRE like this, and as a relatively new SRU team member I need it documented as much as you do. That's what we were trying to fix in the linked Discourse thread.
[14:58] <seb128> how can we help that discussion to go to resolution then?
[14:58] <seb128> so it's clear for everyone what the expectation are
[14:59] <rbasak> otp now, sorry
[15:01] <seb128> no worry, let me know when you get news
[15:20] -queuebot:#ubuntu-release- Unapproved: ply (focal-proposed/main) [3.11-3build1 => 3.11-3ubuntu0.1] (edubuntu, i386-whitelist, ubuntu-server)
[15:49] -queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (groovy-proposed) [2:17.1.2-0ubuntu1]
[17:09] <xnox> laney:  sorry didn't login to irc. Basically we have a couple of things.
[17:10] <xnox> laney:  old cloud images; do not boot the new kernel when one installs it. or they crash. The attempt to boot new kernel is sorted. but crashing is not.
[17:10] <xnox> laney:  can is speak?
[17:10] <xnox> yes i can. (just have scroll to see my text)
[17:11] <xnox> laney:  the crashiness seems to be cloud related. I.e. old qemu in bos01 arm64 or some such. I don't know if it is possible to upgrade bos01 arm64 nodes to have some newer cloud-archive qemu or some such.
[18:07] <laney> xnox: ok, if it's only bos01 then that's what I thought before. try to get 131130 worked on ... don't know how
[18:08] <laney> vorlon: can you access cranberry.c.c?
[18:09] <laney> if so, check out /home/ubuntureports/source/ubuntu-archive-tools/package-subscribers-py2 -- yes, it is what the name implies it is :( and it has a different list of allowed teams
[18:10] <rbasak> I just wondered about centralising the list somewhere. What if we created an uber-team on Launchpad that had all the magic teams as members? Would that work?
[18:11] <laney> it is effectively centralised in ubuntu-archive-tools, just the script that generates that page doesn't use it for stupid reasons
[18:11] <rbasak> Fair enough. It was just a random thought - more driven by curiousity of where that would lead, rather than a direct need.
[18:11] <laney> that page> http://reqorts.qa.ubuntu.com/reports/m-r-package-team-mapping.html
[18:12] <laney> rbasak or bdmurray: if you could sponsor a ticket to IS to get me added to the 'ubuntureports' group I'll try to make the py2 fork use the central list, at least
[18:12] <laney> or feel free to try yourselves :-)
[18:13] <rbasak> I have no particular sway in that department, I don't think?
[18:13] <laney> just as existing members of the group in question
[18:13] <laney> that'd be enough IME
[18:13] <rbasak> Oh
[18:13]  * rbasak doesn't remember anything about that
[18:13] <laney> heh
[18:13] <laney> well I think it'd give you power to edit ^- file
[18:14] <rbasak> cranberry. That rings a bell.
[18:14] <laney> it's the power behind re*q*orts.qa.ubuntu.com
[18:16] <rbasak> Amusingly I may have power to mess about on cranberry, but not being in ~ubuntu-archive I wouldn't be able to push it back to bzr.
[18:17] <rbasak> I'll file an IS ticket to add you to ubuntureports - seems to me you have all the appropriate hats and experience such that it's a no brainer.
[18:17] <bdmurray> I seem to recall trying to make an uber team years about but something about it didn't work out.
[18:17] <bdmurray> s/about/ago/
[18:17] <laney> I suspect it's something like: (1) arrange for the checkout to be pulled/updated; (2) use lputils.team_names instead of the list in package-subscribers-py2
[18:18] <laney> You wouldn't need to push it back as the latter is a local fork
[18:18] <laney> Assuming lputils can be imported as python 2, that is
[18:19] <laney> yeah, looks OK
[18:22] <laney> rbasak: thanks for the ticket!
[18:22] <rbasak> yw.
[18:22] <rbasak> Also I just noticed that you've changed case!
[18:27] <laney> conformism
[19:47] <cpaelzer> xnox: laney: if not in the cloud archive you can have a look at https://launchpad.net/~canonical-server/+archive/ubuntu/server-backports which has recent qemu & co for LTS/LTS-1
[20:37] <vorlon> laney: cranberry> no
[21:10] -queuebot:#ubuntu-release- Unapproved: accepted nfs-ganesha [source] (hirsute-proposed) [3.4-1ubuntu0.21.04.2]
[21:14] -queuebot:#ubuntu-release- Unapproved: accepted nfs-ganesha [source] (groovy-proposed) [3.2-2ubuntu3]
[21:27] -queuebot:#ubuntu-release- Unapproved: accepted u-boot [source] (hirsute-proposed) [2021.01+dfsg-3ubuntu9.1]
[21:43] -queuebot:#ubuntu-release- Unapproved: accepted freeipmi [source] (hirsute-proposed) [1.6.6-3ubuntu0.1]
[21:47] -queuebot:#ubuntu-release- Unapproved: accepted freeipmi [source] (groovy-proposed) [1.6.4-3ubuntu2.1]
[21:53] -queuebot:#ubuntu-release- Unapproved: accepted freeipmi [source] (focal-proposed) [1.6.4-3ubuntu1.2]
[22:02] -queuebot:#ubuntu-release- Unapproved: accepted freeipmi [source] (bionic-proposed) [1.4.11-1.1ubuntu4.2]
[22:06] -queuebot:#ubuntu-release- Unapproved: accepted ceph [source] (hirsute-proposed) [16.2.4-0ubuntu0.21.04.1]
[22:26] -queuebot:#ubuntu-release- Unapproved: pulseaudio (hirsute-proposed/main) [1:14.2-1ubuntu1 => 1:14.2-1ubuntu1.1] (core, i386-whitelist)
[22:27] -queuebot:#ubuntu-release- Unapproved: rejected pulseaudio [source] (hirsute-proposed) [1:14.2-1ubuntu2]
[22:28] -queuebot:#ubuntu-release- Unapproved: accepted pulseaudio [source] (hirsute-proposed) [1:14.2-1ubuntu1.1]
[22:36] -queuebot:#ubuntu-release- Unapproved: accepted pulseaudio [source] (focal-proposed) [1:13.99.1-1ubuntu3.11]
[22:46] -queuebot:#ubuntu-release- Unapproved: accepted systemd [source] (hirsute-proposed) [247.3-3ubuntu3.1]
[23:00] -queuebot:#ubuntu-release- Unapproved: accepted systemd [source] (groovy-proposed) [246.6-1ubuntu1.4]
[23:06] -queuebot:#ubuntu-release- Unapproved: accepted systemd [source] (focal-proposed) [245.4-4ubuntu3.7]
[23:12] -queuebot:#ubuntu-release- Unapproved: accepted systemd [source] (bionic-proposed) [237-3ubuntu10.48]
[23:28] -queuebot:#ubuntu-release- Unapproved: accepted crash [source] (groovy-proposed) [7.2.8-1ubuntu1.20.10.1]
[23:38] -queuebot:#ubuntu-release- Unapproved: accepted crash [source] (focal-proposed) [7.2.8-1ubuntu1.20.04.1]
[23:39] -queuebot:#ubuntu-release- Unapproved: accepted crash [source] (bionic-proposed) [7.2.8-1ubuntu0.18.04.2]