Bug#917788: libmedc11: Overwrites a file from libmedc1v5

Adrian Bunk bunk at debian.org
Sun Jan 6 07:29:30 GMT 2019


On Sat, Jan 05, 2019 at 11:10:52PM +0100, Mattia Rizzolo wrote:
> On Sat, Jan 05, 2019 at 09:53:13PM +0100, Gilles Filippini wrote:
>...
> > > Incidentally, I think that would also cover the just openend #918372,
> > > as with a Conflicts the libgmsh3 package from testing woudln't be
> > > installable, so it would force an upgrade to the version in unstable,
> > > making the test pass.
> >
> > Here I'm not sure. I think the problem is that libmed1v5 and libmedc1v5
> > from the broken med-fichier 4.0.0+repack-1 are still present into
> > unstable. Is there a way to have them removed?
> 
> He also said this.
> However, I think that -generally, at least- the presence of cruft
> packages in the archive should not be an excuse, and upgrades like the
> one debci is trying to emulate should just work.
>...

The problem is not the presence of a cruft package in general.

The problem is that there was one completely broken version of
a package, that was fixed by removing/renaming this package.

debci is trying to install a known-broken cruft package
that will never migrate to testing (due to it being cruft).

The actual bug is that debci considers such cruft packages still part of 
the source package, so the upgrade that is actually tested for gmsh is 
to the known-broken old med-fichier 4.0.0+repack-1.

> regards,
>                         Mattia Rizzolo

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



More information about the debian-science-maintainers mailing list