All, it seems the changes below wasn't sufficient. The testing migration checks are still rebuilding 'sigstore-go' from testing (i.e, 0.6.2-2) with golang-github-google-certificate-transparency from unstable, which fails, so the latter will never migrate to fix the FTBFS in sigstore-go.
I got advice on #debian-mentors that led me to upload golang-github-google-certificate-transparency with a Breaks: sigstore-go (<= 0.6.2-3~) and I was told the testing migration logic would understand this and no longer prevent migration. Let's wait and see... /Simon Simon Josefsson <[email protected]> writes: > notfound 1093640 1.3.1-1 > reassign 1093640 sigstore-go 0.6.2-2 > fixed 1093640 0.6.2-3 > thanks > > Hi. I'm trying to resolve testing migration, and I hope the above is > the right way to do this. Considerations: > > - The FTBFS was actually happneing for sigstore-go 0.6.2-2 when used > with golang-github-google-certificate-transparency 1.3.1-1. > > - the FTBFS is fixed by sigstore-go 0.6.2-3 > > As far as I can tell, there was never a FTBFS bug in > golang-github-google-certificate-transparency. > > Maybe we also have to remove sigstore-go + reverse dependencies from > testing, to allow golang-github-google-certificate-transparency to > migrate first, but I'm hoping the above reassignments are sufficient. > > /Simon >
signature.asc
Description: PGP signature
