FYI.

In the future we should schedule soname transitions with the release team.

I don't think we have done in the past, but we sure should do it in the future.

We got "lucky" this time around.


---------- Forwarded message ----------
From: Adam D. Barratt <[email protected]>
Date: 10 April 2012 19:54
Subject: Re: Bug#668206: nmu: rebuild against libsword9
To: Dmitrijs Ledkovs <[email protected]>, [email protected]


On Mon, 2012-04-09 at 18:40 +0100, Dmitrijs Ledkovs wrote:
> Please schedule the following nmu to migrate to new libsword9 library.

This should really be a transition bug, not an NMU request; as such, it
should also preferably have been filed /before/ you started the
transition, not afterwards...

However, as it doesn't appear to clash with any other ongoing
transitions - scheduled.

> nmu biblememorizer . ALL . -m "Rebuild against libsword9"
> nmu bibletime . ALL . -m "Rebuild against libsword9"
> nmu xiphos . ALL . -m "Rebuild against libsword9"
>
> dw biblememorizer . ALL . -m "libsword-dev >= 1.6.2+dfsg-3"
> dw bibletime . ALL . -m "libsword-dev >= 1.6.2+dfsg-3"
> dw xiphos . ALL . -m "libsword-dev >= 1.6.2+dfsg-3"

The latter argument to a dep-wait is a package relationship so
"libsword-dev (>= 1.6.2+dfsg-3)".  "libsword9" was easier though, so I
used that.

Regards,

Adam

_______________________________________________
Pkg-crosswire-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel

Reply via email to