On Mon, 22 Jun 2015, Paul Wise wrote:
On Mon, Jun 22, 2015 at 3:28 PM, Thorsten Alteholz <deb...@alteholz.de> wrote:
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]?
You started a (minor) transition, please read this:
https://wiki.debian.org/Teams/ReleaseTeam/Transitions
As I maintain all involved packages, I didn't want to start the whole
formalism.
Looks like all the meep related source packages need a binNMU.
Yes, but as soon as I could solve the problems with harminv, there will be
also new versions of all meep packages. So from my point of view the
binNMU is not really needed.
Thorsten
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/alpine.deb.2.02.1506221134410.3...@jupiter.server.alteholz.net
