Bug#728698: nmu: nodejs_0.10.21~dfsg1-1~bpo7+1

[Niels Thykier <niels@thykier.net>]

Control: tags -1 moreinfo

On 2013-11-04 12:19, Mike Gabriel wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: binnmu
> 
> Hello,
> 

Hi,

> unfortuntely, I forgot to provide a build-dependency upload to wheezy-backports when I
> uploaded nodejs. Now, that all B-Ds for nodejs are in wheezy-backports, I'd be happy if
> you could re-trigger a second build of nodejs (0.10.21~dfsg1-1~bpo7+1).
> 

I am a bit puzzled by your request.  If B-D are lacking, packages
usually go into the "BD-Uninstallable" state, which seems to be the case
for nodejs[1].  When the packages become available, the buildd should
automatically change to "Needs-Build" and continue normally from there.
  Alternatively, if the amd64 version of nodejs was built against the
wrong version of a package, then we can do a binNMU for it.  But that
would only be for the amd64 package (since the rest have not been built
yet).

Secondly, for "give-back" requests you should contact
<debian-wb-team@lists.debian.org>.  The Release Team only handles
"binNMU" requests.

> gb nodejs_0.10.21~dfsg1-1~bpo7+1 . ALL . -m "Rebuild for wheezy-backports after all build-dependencies have been uploaded+accepted"
> 

(quick note, I believe you are missing a "wheezy-backports ." after the
"ALL ."; otherwise your request would target sid, so:

  gb nodejs_0.10.21~dfsg1-1~bpo7+1 . ALL . wheezy-backports . -m "[...]"
)

> Thanks a lot,
> Mike
> 
> [...]

~Niels

[1]
https://buildd.debian.org/status/package.php?p=nodejs&suite=wheezy-backports