[05:35] <juliank> xnox: that specifically looked good to me, no problems rebooting, nö kernel crash, test ran until the end.
[05:37] <juliank> Oh I guess it still booted the old kernel
[05:38] <juliank> Which is what the SRU takes care off
[05:38] <juliank> *of
=== juergh is now known as juergh_
=== juergh_ is now known as juergh
[09:38] -queuebot:#ubuntu-release- Unapproved: rejected pulseaudio [source] (focal-proposed) [1:13.99.1-1ubuntu3.11]
[09:39] -queuebot:#ubuntu-release- Unapproved: pulseaudio (focal-proposed/main) [1:13.99.1-1ubuntu3.10 => 1:13.99.1-1ubuntu3.11] (desktop-core, i386-whitelist, ubuntu-server)
[09:39] <xnox> juliank:  retried with all-proposed a bit. Let's see if that starts to be better.
[09:40] <xnox> juliank:  and yes, we do need the kernel from the trigger to boot for the test.
[09:41] <juliank> xnox: right
[09:43] <xnox> anyway the queue is long at the moment will go work on something else and check it afterwards.
[09:44] <juliank> xnox: I was too tired yesterday I guess to get all this sorted out the right way, but at least I'm Covid negative :)
[09:45] <xnox> horay!
[10:33] -queuebot:#ubuntu-release- New sync: xf86-video-armsoc-endlessm (hirsute-proposed/primary) [1.4.1-0ubuntu4]
[11:30] <tjaalton> sil2100: hey, I'm preparing xorg-server for hwe stack, but I wonder if we should backport src:xwayland too? otherwise it might become bit of a mess to get the versioned C/R/B right when backporting from impish (xwayland should bump C/R/B for each backport)
[11:32] <tjaalton> I mean when upgrading from focal -> impish/JJ would need an update to xwayland there, or things go bad
[13:23] -queuebot:#ubuntu-release- Unapproved: rejected linux-firmware [source] (focal-proposed) [1.187.13]
[15:12] -queuebot:#ubuntu-release- Unapproved: linux-firmware (focal-proposed/main) [1.187.12 => 1.187.14] (core, kernel)
[15:12] -queuebot:#ubuntu-release- Unapproved: linux-firmware (hirsute-proposed/main) [1.197 => 1.197.1] (core, kernel)
=== bryyce is now known as bryceh
=== bryceh is now known as bryyce
=== bryyce is now known as bryce_
=== bryce_ is now known as bryce__
=== bryce__ is now known as bryyyce
=== bryyyce is now known as bryceh
[16:15] <bryceh> @utkarsh2102, hi
[16:15] <utkarsh2102> bryceh: hello o/
[16:16] <bryceh> ubuntu-archive, we have a circular dependency situation with php-twig and symfony
[16:17] <bryceh> we've poked at it a few ways but think the solution may be to binary copy bits from debian
[16:17] <bryceh> utkarsh2102, I am getting called to breakfast, can you fill in details?
[16:17] <utkarsh2102> yep, the one doesn't build without the other, do you think you can help here?
[16:17] <utkarsh2102> bryceh: sure
[16:17] <bryceh> I'll be back in 15m
[16:17] <utkarsh2102> ack
[16:18] <utkarsh2102> symfony doesn't build: https://launchpad.net/ubuntu/+source/symfony/5.2.6+dfsg-1/+build/21592316
[16:19] <vorlon> bryceh: binary copy from Debian isn't possible directly because LP doesn't import binaries from Debian; and this shouldn't be done in the main archive.  You could do a bootstrap build in a ppa that embeds the binaries you want in a faked-up source package and outputs them in the .changes and go from there
[16:22] <utkarsh2102> vorlon: just to be explicitly sure, you mean that we should have have a fake source package providing the binaries we need -> build this in PPA -> get .changes -> build the other packages with against this changes and upload to the archive?
[16:22] <cjwatson> Or use the bootstrap archive
[16:23] <cjwatson> (Ubuntu archive admins with access to snakefruit can do that)
[16:23] <utkarsh2102> cjwatson: is it documented somewhere?
[16:23] <vorlon> utkarsh2102: yes (or what cjwatson says, but a ppa is likely easier for you all to manage yourselves)
[16:23] <vorlon> tbf the last time I tried to put something in the bootstrap archive I couldn't remember how to drive it
[16:23] <cjwatson> utkarsh2102: Only by inference from the bootstrap-package tool in lp:ubuntu-archive-tools, I'm afraid
[16:24] <vorlon> ah :)
[16:24] <utkarsh2102> I see
[16:25] <utkarsh2102> do I even need a PPA, though? what if I do a binary build and just build the other package locally from there and upload to the main archive?
[16:25] <cjwatson> I agree that the shove-debs-into-source-package is more self-service, although my goodness that's hacky
[16:25] <cjwatson> utkarsh2102: Launchpad unconditionally rejects binary uploads that don't come from builders
[16:25] <utkarsh2102> aah! that was the missing piece, fair enough
[16:26] <cjwatson> And also the rule is that all builds in the main archive must use only build-dependencies that were built in Launchpad
[16:26] <cjwatson> So any bootstrapping hackery has to be done in a PPA
[16:26] <utkarsh2102> gotcha!
[16:27] <utkarsh2102> since Debian takes binary uploads, I haven't yet needed to create a faked-source package with the binary embedded, how do we go about doing that? are there any sorts of restrictions or recommendations for this, too?
[16:29] <utkarsh2102> s/faked-source/faked-up source/g
[16:29] <cjwatson> I can imagine making up a process for that but don't know if there's prior art
[16:30] <utkarsh2102> if vorlon doesn't know, I guess there's no prior art :)
[16:30] <cjwatson> Honour-system recommendations would be that the binaries are from a trusted source and that the process is either driven or signed off by an Ubuntu core developer, IMO
[16:30]  * vorlon nods
[16:30] <cjwatson> s/recommendations/restrictions/
[16:31] <vorlon> I don't know of prior art, it would just be "throw the .deb in a source package and shortcut debian/rules"
[16:31] <vorlon> if I could figure out again how to use the bootstrap archive, I'd be happy to do that
[16:32] <vorlon> which package needs its binaries imported?
[16:32] <utkarsh2102> symfony
[16:32] <utkarsh2102> listed missing stuff here: https://launchpad.net/ubuntu/+source/symfony/5.2.6+dfsg-1/+build/21592316
[16:33] <utkarsh2102> uh, if we have php-twig built somehow (that is binaries), probably symfony would build and unblock other bunch of stuff
[16:33] <utkarsh2102> and we can take it from there
[16:34] <vorlon> php-twig would be fewer binary packages to wrangle :)
[16:34] <bryceh> back
[16:34] <utkarsh2102> vorlon: hah, yeah
[16:35] <cjwatson> vorlon: Basically you copy the needs-bootstrapped source package into a PPA, wait for the build to fail, chuck the necessary build-deps into snakefruit:~ubuntu-archive/public_html/bootstrap/$ARCH/, run ./make-release.sh in that directory, check that the resulting Packages looks right, then point bootstrap-package at the failing build in the PPA
[16:35] <vorlon> ok
[16:36] <cjwatson> vorlon: Then IIRC you copy the successful build output from the PPA, put that in the same bootstrap directory, ./make-release.sh again (which may require manually removing Packages.db first so apt-ftparchive's cache doesn't get in the way), and point bootstrap-package at the corresponding failing build in the primary archive
[16:38] <cjwatson> Hm, bootstrap-package may require being quite privileged, I might need to help there
[16:39] <vorlon> utkarsh2102: ^^ so if you want to upload symfony to a ppa, I'll push php-twig to the bootstrap archive
[16:40] <utkarsh2102> vorlon: yeah, I think that'd hopefully work & would be very helpful!
[16:40] <utkarsh2102> bryceh: do you concur? ^^
[16:43] <bryceh> utkarsh2102, I'm not sure I completely follow the process there, but I can certainly shoot symfony into a ppa
[16:44] <cjwatson> Normally copy it from the primary archive to a PPA
[16:44] <cjwatson> Rather than doing a separate upload
[16:44] <utkarsh2102> bryceh: I do follow the process (I hope), I just want to be double-sure that symfony would build if we have php-twig built already.
[16:44] <utkarsh2102> which I think should work
[16:45] <utkarsh2102> though interestingly we have 2 circular-dependencies, the symfony <-> php-twig is one and the other one will come later when we try to sort out the first :)
[16:45] <vorlon> php-twig added to amd64 bootstrap
[16:45] <utkarsh2102> vorlon: awesome, thanks
[16:47] <utkarsh2102> vorlon: the link to bootstrap PPA would be? :)
[16:47] <vorlon> utkarsh2102: it's not a ppa, it's launchpad Magic
[16:47] <utkarsh2102> ah, okay, gotcha
[16:47] <cjwatson> Well, also, you make you own PPA
[16:47] <vorlon> utkarsh2102: you just copy symfony to a ppa of your choosing
[16:47] <cjwatson> *your
[16:47]  * vorlon nods
[16:48] <cjwatson> It's not *very* magic, it's basically an API call that tells LP to add a caller-chosen line to sources.list when it runs the build
[16:48] <cjwatson> It's just fairly heavily restricted since we don't want people doing this except for special circumstances when there's no other reasonable option
[16:49] <utkarsh2102> ok, so will the LP already know about this internal magic if I upload symfony to my personal PPA?
[16:49]  * utkarsh2102 is trying to connect the dots here
[16:51] <bryceh> I've just uploaded symfony in a PPA at ppa:bryce/symfony-bootstrap
[16:51] <utkarsh2102> awesome!
[16:52] <cjwatson> utkarsh2102: It's an operation that a suitably privileged person applies on request to an individual build
[16:52] <utkarsh2102> cjwatson: aah, I see
[16:53] <utkarsh2102> https://launchpad.net/~bryce/+archive/ubuntu/symfony-bootstrap/+build/21601095 -> we should have a failed symfony build here
[16:53] <cjwatson> (need to wait for it to actually fail first)
[16:53] <utkarsh2102> of course :)
[16:56] <utkarsh2102> build failed!
[16:56] <cjwatson> vorlon: OK, so try "bootstrap-package -A ppa:bryce/ubuntu/symfony-bootstrap -s impish -a amd64 symfony"?  I think it may need me to do it though
[16:58] <vorlon> let's see
[16:59] <vorlon> lazr.restfulclient.errors.Unauthorized: HTTP Error 401: Unauthorized
[16:59] <vorlon> cjwatson: would it be a good idea for me to have that access?
[17:02] <cjwatson> vorlon: I think we probably do need to liberalize that slightly, but it's not a trivial thing, needs LP code changes
[17:03] <cjwatson> Maybe
[17:03] <cjwatson> So yes, in principle I think you ought to have that access, just need to think through what actual rules should generate that result
[17:03] <vorlon> ok.  I seem to recall Adam used to have access?  by virtue of some group I've never been in? :)
[17:03]  * vorlon nods
[17:04] <cjwatson> Yeah, I don't remember the exact details ...
[17:04] <cjwatson> I've run bootstrap-package now
[17:04] <utkarsh2102> sweet!
[17:04] <cjwatson> vorlon: Could you file a bug about this?
[17:04] <cjwatson> Quoting this conversation or whatever
[17:15] <utkarsh2102> cjwatson: is it just me or LP went down?
[17:16] <utkarsh2102> yeah, can't seem to reach LP or the excuses page
[17:17] <cjwatson> utkarsh2102: GS2 network issues apparently
[17:17] <cjwatson> See ~is-outage on MM
[17:18] <utkarsh2102> ah, thanks
[17:18] <utkarsh2102> would've been interesting if bootstrapping had taken down LP :P
[17:18] <bryceh> o_O
[17:19] <bryceh> utkarsh2102, well, it *is* php we're dealing with, so...
[17:19] <utkarsh2102> haha
[17:20] <bryceh> thanks btw, cjwatson and vorlon
[17:21] <utkarsh2102> indeed, thanks cjwatson and vorlon
[17:29] <utkarsh2102> btw, cjwatson: when things fall back to its place, where will we find symfony or php-twig built?
[17:29] <utkarsh2102> (I am just trying to lay down next steps for us)
[17:29] <bryceh> utkarsh2102, -proposed presumably
[17:31] <utkarsh2102> that'd be super helpful
[17:31] <cjwatson> utkarsh2102: In that PPA first, then in -proposed on the second iteration
[17:31] <cjwatson> Assuming it all works
[17:32] <utkarsh2102> cool, thank you!
[17:32] <cjwatson> utkarsh2102: But https://launchpad.net/~bryce/+archive/ubuntu/symfony-bootstrap/+build/21601095 is sort of back now and is reporting several other missing dependencies
[17:33] <cjwatson> Can you figure those out and get back to us?
[17:46] <utkarsh2102> sure; php-async-aws-sqs and php-async-aws-ses both are waiting for php-async-aws-core to be built, which is missing dependency on php-symfony-contracts, whose build (https://launchpad.net/ubuntu/+source/php-symfony-contracts/2.4.0-1/+build/21595068) needs to be re-tried.
[17:46] <utkarsh2102> bryceh: could you please trigger the build and take a look at this^?
[17:47]  * utkarsh2102 has no access to trigger builds, retries, etc yet :/
[17:48] <bryceh> utkarsh2102, looking
[17:48] <utkarsh2102> thanks!
[17:48] <vorlon> cjwatson: LP: #1930092
[18:01] <bryceh> php-symfony-contracts looks like it needs more than just a rebuild, it hitting a syntax change introduced in php8.  But I've done a rebuild anyway, can't hurt.
[18:02] <bryceh> I'll get php-email-validator copied into the PPA directly
[18:02] <bryceh> the other packages that symfony is build dependent on, themselves are build-dependent on symfony.
[18:02] <utkarsh2102> php-email-validator (>=3) is in -proposed already
[18:04] <ddstreet> bdmurray lp:1785383 has a MR open for impish, i usually just open MR and let rbalint review and merge into the devel release
[18:05] <bdmurray> ddstreet: I'd like to at least see it merged before approving the SRUs.
[18:16] <bryceh> LP seems to be super intermittent now
[18:16] <bdmurray> bryceh: Yeah, I think its a sign to start the long weekend early!
[18:17] <bryceh> utkarsh2102, ok I *think* php-symfony-contracts failed as I anticipated, I think it needs patched.  But bdmurray has a point, this might be a better task for next week.
[18:18] -queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (focal-proposed) [1.187.14]
[18:18] -queuebot:#ubuntu-release- Unapproved: procps (focal-proposed/main) [2:3.3.16-1ubuntu2.1 => 2:3.3.16-1ubuntu2.2] (core, i386-whitelist)
[18:18] -queuebot:#ubuntu-release- Unapproved: procps (hirsute-proposed/main) [2:3.3.16-5ubuntu3 => 2:3.3.16-5ubuntu3.1] (core, i386-whitelist)
[18:18] -queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (hirsute-proposed) [1.197.1]
[18:18] -queuebot:#ubuntu-release- Unapproved: procps (groovy-proposed/main) [2:3.3.16-5ubuntu2.1 => 2:3.3.16-5ubuntu2.2] (core, i386-whitelist)
[18:19] <utkarsh2102> haha
[18:19] <utkarsh2102> by all means, it's 12 here so I'm afk already :)
[19:09] <vorlon> bdmurray: feedback on LP: #1903351
[19:09] <ubot3> Launchpad bug 1903351 in procps (Ubuntu Groovy) "ignore_eacces and ignore_erofs patches don't work properly" [Medium, In Progress] https://launchpad.net/bugs/1903351
[19:31] -queuebot:#ubuntu-release- Unapproved: yaru-theme (focal-proposed/main) [20.04.10.1 => 20.04.11.1] (desktop-core, ubuntu-desktop)
[19:59] -queuebot:#ubuntu-release- Unapproved: samba (focal-proposed/main) [2:4.11.6+dfsg-0ubuntu1.8 => 2:4.11.6+dfsg-0ubuntu1.9] (core, i386-whitelist)
[20:01] -queuebot:#ubuntu-release- Unapproved: samba (groovy-proposed/main) [2:4.12.5+dfsg-3ubuntu4.3 => 2:4.12.5+dfsg-3ubuntu4.4] (core, i386-whitelist)
[20:39] -queuebot:#ubuntu-release- Unapproved: update-notifier (xenial-proposed/main) [3.168.14 => 3.168.15] (ubuntu-desktop, ubuntu-server)
[20:40] -queuebot:#ubuntu-release- Unapproved: update-notifier (bionic-proposed/main) [3.192.1.10 => 3.192.1.11] (ubuntu-desktop, ubuntu-server)
[20:41] -queuebot:#ubuntu-release- Unapproved: update-notifier (focal-proposed/main) [3.192.30.7 => 3.192.30.8] (ubuntu-desktop, ubuntu-server)
[20:41] -queuebot:#ubuntu-release- Unapproved: update-notifier (hirsute-proposed/main) [3.192.40.2 => 3.192.40.3] (ubuntu-desktop, ubuntu-server)
[23:16] -queuebot:#ubuntu-release- New binary: golang-github-google-go-intervals [amd64] (impish-proposed/none) [0.0.2-2] (no packageset)