On 2018-03-06 9:04, Emilio Pozuelo Monfort wrote:
On 06/03/18 09:58, Bas Couwenberg wrote:
On 2018-03-06 09:47, Emilio Pozuelo Monfort wrote:
On 05/03/18 19:38, Sebastiaan Couwenberg wrote:
On 03/04/2018 12:33 PM, Sebastiaan Couwenberg wrote:
On 03/04/2018 09:45 AM, Emilio Pozuelo Monfort wrote:
On 03/03/18 12:10, Bas Couwenberg wrote:
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: transition
Control: block -1 by 889931 889936 876934
Control: forwarded -1

PROJ 5.0.0 has been released and bumps the SOVERSION from 12 to 13,
requiring a transition.

Almost all reverse dependencies rebuilt successfully with the new proj
packages from experimental (as summarized below),

Please also schedule binNMUs for the affected packages in experimental if those have not yet moved to unstable when the transition starts.

Go ahead.

Thanks. proj (5.0.0-1) was uploaded earlier this morning and is now
built & installed on all release architectures.

Please also schedule binNMUs for the rdeps in experimental:

 dw spatialite_4.4.0~rc1-1~exp2 . ANY . experimental . \
 -m 'libproj-dev (>= 5.0.0-2)'

 dw spatialite-tools_4.4.0~rc1-1~exp1 . ANY . experimental . \
 -m 'libproj-dev (>= 5.0.0-2)'

There's no binNMU command there.

My understanding of wanna-build is that dep-wait achieves the same and adds a
dependency constraint, which nmu does not.

It does not. dep-wait only adds the dependency constraint, so it's useful if the package is in needs-build or bd-uninstallable. If it's e.g. Installed, it will
do nothing.

dep-wait could be seen as effectively being the same as a give back with the added dependency constraint, which may be where the confusion has arisen. A give back only requests the current (if any) build to be retried, it can't generate a new build (which is what a binNMU does)



Reply via email to