Hi, On 24-10-2022 12:00, Adrian Bunk wrote:
On Sun, Oct 23, 2022 at 12:35:41PM +0200, Paul Gevers wrote:We'll handle it somehow yes.It seems someone already handled it or it disappeared by itself.
Yes, I scheduled the tests with *less* packages from unstable than britney and those passed.
Any further ideas how to handle the situation?We'll handle perl, you can handle TL yourself by filling an RC bug.The autopkgtest regression in latexml already prevents the migration of TL.
I think Hilmar was afraid of what happens after latexml is removed from testing. Than TL migrates and breaks latexml for users of testing that don't immediately remove packages that are no longer in testing.
The only possible action on the TL side will be after latexml is fixed to add Breaks in TL against unfixed versions of latexml to avoid users (or test environments) ending up with incompatble combinations.
That, but I think it's reasonable *for some time* to prevent TL to migrate even if latexml is already removed. Having said that, being 60 days out-of-sync between unstable and testing is by default RC too, so the "for some time" isn't extremely long.
Paul
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature