Control: tags -1 patch

On 25-07-15 01:42, Sebastiaan Couwenberg wrote:
> On 03-07-15 15:11, Matthias Klose wrote:
>>  - If there are no reverse dependencies, it should be the package
>>    maintainers decision if a transition is needed.  However this might
>>    break software which is not in the Debian archive, and built
>>    against these packages.
>>  - If a library transition is needed, please prepare for the change.
>>    Rename the library package, append "v5" to the name of the package
>>    (e.g. libfoo2 -> libfoo2v5). Such a change can be avoided, if you
>>    have a soversion bump and you upload this version instead of the
>>    renamed package.  Prepare a patch and attach it to this issue (mark
>>    this issue with patch), so that it is possible to NMU such a
>>    package. We'll probably have more than hundred transitions
>>    triggered. Then reassign the issue to and
>>    properly tag it as a transition issue, by sending an email to
>>      user
>>      usertag <this issue> + transition
>>      block <this issue> by 790756
>>      reassign <this issue>
> libcitygml has no reverse dependencies, so a transition won't be required.
> I've uploaded a the latest upstream release from the renew development
> on GitHub to experimental. It includes as SONAME bump, and has been
> built with GCC 5.2 from experimental. The symbols on the other
> architectures need to be updated after the builds become available.

The symbols for the other architectures were updated in libcitygml
(1.4.3-1~exp3) available in experimental.

How will it get to unstable? Shall I upload it to unstable when the
libstdc++ transition reaches libcitygml at dependency level 11?

Kind Regards,


 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Pkg-grass-devel mailing list

Reply via email to