On Sun, Jan 06, 2019 at 12:35:05PM +0100, Paul Gevers wrote: > Hi Gilles, > > On Sat, 05 Jan 2019 17:04:05 +0100 Gilles Filippini <p...@debian.org> wrote: > > Please unblock package med-fichier. Is has currently to wait for 43 days > > because of an autopkgtest regression against the version of gmsh in testing > > (3.0.6+dfsg1-4) [1]. But it succeeds against version 3.0.6+dfsg1-4.1 in > > unstable [1] which waiting for med-fichier to migrate [2]. > > You can also handle this yourself by one of the following solutions: > > - in med-fichier: in any of the binary packages add a *versioned* breaks > on any of the binary packages from gmsh.
There is no package where you could place such a Breaks. The only package the gmsh autopkgtest picks up from unstable is the broken cruft package libmed1v5. No package that is still built by med-fichier/unstable is installed in the relevant autopkgtest. > - in gmsh: add a *versioned* test dependency on any of the med-fichier > binary packages This won't help since gmsh/testing is being tested. And gmsh can't migrate before med-fichier. > - in gmsh: in any of the binary packages add a *versioned* dependency on > any of the binary packages from med-fichier This won't help since gmsh/testing is being tested. And gmsh can't migrate before med-fichier. > The result of any of the actions above is that the autopkgtests will be > done with both packages from unstable and will be used for both > migrations. I didn't spend the time on the relations to see which is > most appropriate in your case. I don't think any of the above would help. With some luck the syrthes upload will result in automatic cruft removal. The root problem is that debci installs cruft packages from unstable. > Paul cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed