Re: testing migration, excuses for package harminv

2015-06-22 Thread Emilio Pozuelo Monfort
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

Re: testing migration, excuses for package harminv

2015-06-22 Thread Paul Wise
On Mon, Jun 22, 2015 at 5:40 PM, Thorsten Alteholz wrote: > 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. So the solution is to rebuild all the meep packages against

Re: testing migration, excuses for package harminv

2015-06-22 Thread Thorsten Alteholz
On Mon, 22 Jun 2015, Paul Wise wrote: On Mon, Jun 22, 2015 at 3:28 PM, Thorsten Alteholz 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.d

Re: testing migration, excuses for package harminv

2015-06-22 Thread Paul Wise
On Mon, Jun 22, 2015 at 3:28 PM, Thorsten Alteholz 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

testing migration, excuses for package harminv

2015-06-22 Thread Thorsten Alteholz
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]? Thanks! Thorsten [1]https://tracker.debian.org/ -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Co