Micha Lenk <[email protected]> writes: > It's not clear why a backport is sensible for this arch:all package. > What is the intended usecase? What is the userbase? > What is blocked if there was no backport? > > Please, let's discuss on [email protected] first.
Ah, sorry, I guess I should have put the reasoning somewhere (in the changelog?) The reason for this backport is that recent versions of openqa depend upon bootstrap 5.3.3, and I would like to upgrade the backport of openqa (which is already in bookworm-backports) when I upgrade the version of openqa in trixie. BTW The openqa upload that needs this is currently waiting on a couple of node packages that are in the NEW queue (node-ace-code & node-anser) that will need to be in the archive before I can update openqa, which now depends upon them. I'll be wanting to backport those node packages too, once they've got through NEW. Cheers, Phil. -- Philip Hands -- https://hands.com/~phil
signature.asc
Description: PGP signature
