Hi Jonas, On 23-04-2020 12:56, Jonas Smedegaard wrote: > Ohh, the test failure I reference was for _testing_ - I thought it was > for _unstable_ and was puzzled why it also failed there. > > Yes, I agree that this looks like just an autopkgtest issue (but makes > me wonder if eye should include Build-Using:). > > @Paul: Please let this through, despite autopkgsuite failing for > testing.
You mean, this is *only* an autopkgtest issue and does *not* point at missing *versioned* dependencies? I.e. if *only* eye from unstable would migrate to testing, but *not* swi-prolog, eye works correctly in testing? To be clear, I don't intent to "let this through". What I can do is schedule the tests for both swi-prolog and eye with *both* packages from unstable. I *assume* they would pass and that would unblock their migration from autopkgtest point of view. Paul
signature.asc
Description: OpenPGP digital signature
