Bug#848648: RM: python-ffc [amd64, arm64, armel, armhf, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x] -- RoQA; now an arch:all package

[Drew Parsons]

The Architecture:all status is now fixed in the unstable archive;
python-ffc 2016.2.0-1 is now accessible to apt.

Thanks for the fixes,
Drew

Bug#848648: RM: python-ffc [amd64, arm64, armel, armhf, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, ppc64el, s390x] -- RoQA; now an arch:all package

[Ansgar Burchardt]

Package: ftp.debian.org
User: ftp.debian@packages.debian.org
Usertags: rm

Drew Parsons writes:
> ffc 2016.2.0-1 was uploaded to unstable nearly a week ago. 
> But python-ffc is still not showing up after an apt-get update, it's
> still stuck at 2016.1.0-1.
>
> We need the ffc update so we can complete the dolfin update to
> 2016.2.0.

When packages switch from arch-dep to arch-indep (arch: all), the old
binaries do not get removed automatically (yet) and need a manual
removal request.

The new arch:all binary package also gets "hidden": dak tries to keep
arch-indep and arch-dep packages in the exported view (Packages index)
at the same version to keep packages installable.  The arch-dep packages
often have a `Depends: ${arch-indep} (= ${source:Version})` relationship
that apt would not be able to satisfy otherwise as apt only considers
the newest version by default.

Ansgar