On Mon, May 7, 2012 at 9:41 PM, Olе Streicher wrote: > I am the maintainer of the package "cpl". Upstream just released a new > version 6.0 and changed the SONAME for the built libraries from 12 to > 20. So, the source now builds a package "libcplcore20" instead of > "libcplcore12". There are a few dependencies of other packages from > libcplcore12, which I all maintain myself (esorex and python-cpl). > > The problem is now that I get migration excuses like > > "out of date on i386: [...], libcplcore12, [...] (from 5.3.1-1)" > > which I don't know how to handle. What is the usual way to get rid of > these?
Transitions should be co-ordinated with the release team before uploading to unstable: http://wiki.debian.org/Teams/ReleaseTeam/Transitions -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKTje6F-ytHzQ4giOvTLh�qdgmkunynyzkamyzbdqtppt...@mail.gmail.com
