Re: binNMU order of ObjC/GNUstep packages
- To: Yavor Doganov <yavor@gnu.org>
- Cc: debian-release@lists.debian.org, dktrkranz@debian.org
- Subject: Re: binNMU order of ObjC/GNUstep packages
- From: Mehdi Dogguy <mehdi@dogguy.org>
- Date: Mon, 23 Aug 2010 07:55:44 +0200
- Message-id: <[🔎] 4C720D60.3020700@dogguy.org>
- In-reply-to: <87wrrixonm.GNU's_Not_Unix!%yavor@gnu.org>
- References: <4C6E93A1.8080909@dogguy.org> <87aaohz5fq.GNU's_Not_Unix!%yavor@gnu.org> <20100820174355.GI20626@dogguy.org> <878w40yogx.GNU's_Not_Unix!%yavor@gnu.org> <4C718916.90104@dogguy.org> <87wrrixonm.GNU's_Not_Unix!%yavor@gnu.org>
On 08/23/2010 12:34 AM, Yavor Doganov wrote:
> [CCing -release because this is a FAQ during GNUstep transitions;
> hope you don't mind.]
If you want…
>
> [...]
>
I usually schedule binNMUs according to a topological order computed
from build-dependencies informations. The transition monitor shows that
order. If the order inferred from the build-dependencies is incorrect,
then there is a problem in your packages.
Now, from all involved packages, there are a few that I hadn't binNMUed:
adun.app, gnustep-back and talksoup.app. The first two compiled with new
versions and there is no need to re-schedule them. The last one is the
only one "affected". I'll schedule the necessary binNMU request.
Regards,
--
Mehdi Dogguy مهدي الدڤي
http://dogguy.org/
Reply to: