Re: testing migration, excuses for package harminv
On 22/06/15 09:28, Thorsten Alteholz wrote:
> Hi,
>
> I seem to miss the forest for the trees, but what does
> old binaries left on amd64: libharminv2 (from 1.3.1-10)
> mean at [1]?
It means what it says: the old binaries are still there. They need to be
decrufted, and for that, but that cannot happen at the moment because they still
have rdeps. What you need is for the rdeps to be built against the new harminv
version so they depend on on libharminv3. They were binNMUed but they failed to
build, see:
https://buildd.debian.org/status/package.php?p=meep,meep-lam4,meep-mpi-default,meep-mpich2,meep-openmpi&compact=compact
So those packages need fixing, and once they have all been successfully built,
then the libharminv2 binaries can be removed, and harminv can migrate.
Emilio
Reply to: