Hi Paul, Quoting Paul Gevers (2020-01-04 20:24:50) > With a recent upload of mmdebstrap the autopkgtest of mmdebstrap fails > in testing when that autopkgtest is run with the binary packages of > mmdebstrap from unstable. It passes when run with only packages from > testing. In tabular form: > pass fail > mmdebstrap from testing 0.5.1-3 > all others from testing from testing > > I copied some of the output at the bottom of this report. It seems that > this apparent regression is actually a sensitivity of the test to what > is in the base system. Recently libcrypt got split of from gcc (but > hasn't migrated to testing yet). So, without changes to your test, it > can either pass in unstable, or in testing, but not both. Please > consider how you want to fix this, as currently your package can't > migrate to testing [1].
yes, I was aware of the introduction of libcrypt, that's why I uploaded 0.5.1-3 which addresses precisely this change. My naive assumption was, that once libcrypt migrates to testing, mmdebstrap would migrate just fine. Thanks a lot for opening this bug report because apparently I have a misunderstanding about how our CI and migration work together with automatic migration and maybe you can help me clear up my understanding of it? :) Thanks! cheers, josch
signature.asc
Description: signature
