Paul Gevers <elb...@debian.org> writes: > Hi Noah, > > On Thu, 08 May 2025 10:10:06 +0200 Simon Josefsson > <si...@josefsson.org> wrote: >> The testing migration seems a bit unclear to me, can you take a look if >> this will actually migrate? It is scheduled for autoremoval right now. >> https://tracker.debian.org/pkg/gsasl >> https://tracker.debian.org/pkg/libgssglue >> I think you need a dependence on 'dovecot (>= 2.4~)' in >> gsasl/libgssglue, and a 'Breaks: gsasl (<< 2.2.2-1.1~), libgsasl (<< >> 0.9-1.1~)' in dovecot. > > Without having spend a lot of time checking, this appears to be > correct to me. To get more confidence, is the failure of the > autopkgtest only a *test* regression, or is this also impacting > regular use cases for users?
My reading is that the autopkgtest failure happens because it install dovecot 2.3 and the NMU changed gsasl to only work with dovecot 2.4: https://ci.debian.net/packages/g/gsasl/testing/amd64/60433568/#S15 67s Get:35 http://deb.debian.org/debian testing/main amd64 dovecot-imapd amd64 1:2.3.21.1+dfsg1-1+b2 [1,547 kB] I think a 'dovecot (>= 2.4~) in gsasl/debian/tests/control would have helped here. I clicked the 'retry' buttons for debci now, but I never grok how debci picks dependency package versions. Maybe it will install dovecot 2.4 now and things will look green soon. I'm not so sure about my statement above, is a Breaks: appropriate when it is not breaking the package build but only breaks debci for that package? Seems like that ought to be handled by gsasl/debian/tests/control Depends:. As for test vs user-facing, as far as I understand, nothing except the self-test changed in gsasl here, and dovecot upstream created a patch to make things work with gsasl and that is in the Debian devecot 2.4 package. I haven't reviewed details to see if dovecot really was buggy here or if they decided to just silence the problem by patching things on their side, but I'm also not sure that matters. The gsasl patches had nothing to do with the interop failure, it was just to make the gsasl self-test start again after dovecot changed their configuration syntax. Sorry for not really answering your question, but maybe the above helps you make a better assessment of the situation than I'm able to. /Simon > In the latter case, the Breaks and versioned Depends are > appropriate. In the former case I can get the tests to be scheduled to > use both packages from unstable. (And I wonder the same about the > other autopkgtest failures triggered by dovecot). > > For avoidance of doubt, if we think these are only test failures and > not user facing failures, I rather avoid further upload before things > migrate to testing. /Simon
signature.asc
Description: PGP signature
