Paul Gevers writes ("Re: Bug#901897 closed by Jonathan Nieder <jrnie...@gmail.com> (Bug#901897: fixed in git 1:2.18.0~rc2-2)"): > On 22-06-18 12:45, Ian Jackson wrote:
> > to the bad run which prompted your intervention, and the good run > > which resulted ? > > [2] for the bad one. You already found the good one: [1]. Ah, thanks. > > But that is appropriate, because the new git Breaks earlier versions > > of dgit. AIUI britney will therefore not migrate the new git until > > the new dgit is migrated, which is correct. > > Ack. That is why I allow myself to intervene in such a situation. If you had done nothing, I guess after dgit was migrated, git would get a retest and then things would pass ? So there would be a small delay to the git migration. > This is very much not dgit specific. Today I had to do that for about 5 > packages (coincidence, last two months I have done it about 15-20 times > or so). Autopkgtest doesn't detect that the installed version of the > package that it is testing is not the one that it was asked to test. It > must, and then start over again in some form with the test suite from > the right version. This sounds quite annoying. I think the right fix is for britney to tell ci.d.n a set of packages which might migrate. ISTR discussing that on debian-ci recently. I don't know exactly what autopkgtest command line rune you are using but certainly it was designed to be able to run the test suite of one version against a different version. Regards, Ian. -- Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.