[00:32] <mwhudson> hooray for past me adding autopkgtests to casper
[10:49] <paride> Hi! There is one thing I don't understand about `apt-get instal -t <target> <package>` vs. `apt install <package>/<target> `: the former doesn't prompt me to downgrade the package to the version in <target>, while the latter does. (<target> is in sources.list and offers a lower version than the installed one.)
[10:49] <paride> See: https://paste.ubuntu.com/p/4CGtcTMTJB/
[10:50] <paride> as asked in the pastebin: where am I wrong?
[10:52] <rbasak> paride: -t is a pin override, whereas / selects the version available from a specific suite?
[10:53] <rbasak> So the behaviour you see makes sense to me
[10:54] <rbasak> The -t gives you a pin priority of 990, but you need 1000 for a downgrade to be permitted
[10:55] <paride> rbasak, thanks, this makes sense. I thought the only mechanism for selecting a version from a specific suite (/target) was bumping the pin-priority for the package, which is basically what -t does
[10:56] <paride> and could still be, maybe with priority >=1000
[11:10] <paride> Well the mechanism isn't clear to me, but I'll accept that <package>/<target> selects only versions from the <target> suite, and so it's stronger than -t
[15:21] <ddstreet> rbasak can you check the git-ubuntu import of systemd? it seems behind by a couple days
[15:22] <rbasak> Hmm. The backlog seems to have exploded.
[15:23] <rbasak> I bumped the priority of systemd for you.
[15:23] <ddstreet> thanks!
[15:23] <rbasak> Not sure why just about every package suddenly appeared in the queue
[15:25] <rbasak> Ah it's because bullseye got "published" according to LP I think.
[15:26] <schopin> hmm? already ?
[15:27] <rbasak> For example the first entry in https://launchpad.net/debian/+source/adwaita-icon-theme/+publishinghistory
[15:27] <rbasak> I don't know what action that corresponds to in Debian
[15:29] <schopin> tracker.d.o doesn't list any recent action on that package.
[15:35] <cjwatson> rbasak,schopin: Ah, this is probably because I recently nagged IS to land https://code.launchpad.net/~cjwatson/lp-production-crontabs/import-bullseye/+merge/370477 after nearly two years
[15:36] <cjwatson> I didn't realize it would affect git-ubuntu or I'd have warned you, sorry
[15:37] <rbasak> No problem. I'm not sure what I could have done anyway. Essentially this means that a refs/heads/debian/bullseye needs adding to every repository, so everything needs touching anyway
[15:38] <rbasak> I have a performance optimisation I need to do to make the importer far more efficient, but that's quite a bit of work I haven't done yet
[15:43] <dbungert> may I get a retest click for evdi, which is currently blocking glibc?  https://autopkgtest.ubuntu.com/request.cgi?release=impish&arch=s390x&package=evdi&trigger=glibc/2.33-0ubuntu9
[15:56] <RikMills> dbungert: clicked
[16:05] <dbungert> RikMills: passed, thanks.
[21:24] <teward> ddstreet: for your backports proposal: if you need more for day to day my FT job is starting to die down, not sure if anyone will whine because of my having 'all the hats' but as long as i'm not in the admins/leadership for.  Assuming of course that TB approves (since it might need permissions overhauls...).  Otherwise, I'll just keep an eye :)
[21:24] <teward> (my email server took a crap so I can't email outbound atm)
[21:25] <teward> wow that was a poor sentence
[21:25] <rbasak> I'll write to the thread tomorrow, but FWIW, IMHO this plan doesn't need TB approval as we have unanimous consensus in ubuntu-devel@
[21:26] <teward> rbasak: check.  I meant specifically if there's something special for 'approval' rights that TB has to instruct relevant teams to implement, etc.
[21:26] <teward> assuming nobody objects.
[21:26] <teward> assuming nobody objects, I'm volunteering day to day activities for backports as my FT job is dying down in terms of how busy i'm being kept.
[21:26] <rbasak> I'm not aware of anything. Therefore I intend to seek forgiveness rather than permission here, and JFDI.
[21:26] <teward> (Tis what I was trying to say before xD)
[21:26] <teward> yep
[21:27] <rbasak> I've asked ScottK to tranfer ownership to ~techboard, but I haven't been able to reach him.
[21:28] <rbasak> I'll give him some time longer, and then ask Launchpad admins to make the change. Everyone involved knows the background here and I believe it's completely non-controversial and that nobody would object, including ScottK.
[21:28] <rbasak> Once owned by ~techboard I intend just to make the changes agreed.
[21:28] <rbasak> So JFDIng it all the way through.
[21:28] <rbasak> If somebody want to object, then please reply to the thread, and I'll then ask the TB who I'm sure will just say yes anyway :)
[21:36] <bdmurray> jawn-smith: Do you know if there is any reason to believe bug 1912385 isn't fixed?
[21:36] <teward> rbasak: yep.  I only save "ask for permission first" if something I'm touching has the major major risk of blowing everything up (like apparmor xD)
[21:37] <bdmurray> dbungert: Do you happen to know if bug 1914075 is really fixed?
[21:37] <bdmurray> teward: "major major"?
[21:38] <teward> sue me i'm on the tail end of a long day
[21:38] <teward> bdmurray: i avoid kernel like the plague, but something owned by Security (apparmor) I don't touch unless i have to :P
[21:38] <teward> and spotcheck along the way
[21:38] <teward> yes 'major major' is the equivalent of "Basically if this breaks everything else breaks" :)
[21:39] <bdmurray> then what is major risk?
[21:42] <jawn-smith> bdmurray: I believe that's fixed but I actually have a focal CM4 booted at the moment so I can double check
[21:44] <bdmurray> jawn-smith: that'd be helpful thanks!
[21:56] <jawn-smith> bdmurray that bug does not seem to be affecting my CM4. Per the latest comment by juergh I think the original bug was caused by the user installing an unofficial version of pi-bluetooth
[21:56] <jawn-smith> but I can confirm that with pi-bluetooth 0.1.15ubuntu0~20.04.1 installed my wifi device is still detected
[21:57] <jawn-smith> ah read it a little more closely, the second user's bug was the weird pi-bluetooth version. So yes I can confirm the original bug is fixed
[21:57] <bdmurray> Okay, feel free to comment and set it to Fix Released.
[21:58] <jawn-smith> done!
[22:06] <dbungert> bdmurray: re 1914075, not sure
[22:19] <bdmurray> dbungert: Okay, I'll punt it down to 20.04.3 and discuss it with "people"