Your message dated Fri, 11 May 2012 00:59:46 +0200 with message-id <20120510225946.GB20737@mraw.org> and subject line Re: Bug#672416: nmu: mercurial_2.2.1-2 has caused the Debian Bug report #672416, regarding nmu: mercurial_2.2.1-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 672416: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672416 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: nmu: mercurial_2.2.1-2
- From: Javi Merino <vicho@debian.org>
- Date: Thu, 10 May 2012 22:52:30 +0100
- Message-id: <[🔎] 20120510215230.9087.76369.reportbug@einstein.local>
Package: release.debian.org Severity: normal User: release.debian.org@packages.debian.org Usertags: binnmu gb mercurial_2.2.1-2 . kfreebsd-amd64 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/6 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
- To: Javi Merino <vicho@debian.org>, 672416-done@bugs.debian.org
- Subject: Re: Bug#672416: nmu: mercurial_2.2.1-2
- From: Cyril Brulebois <kibi@debian.org>
- Date: Fri, 11 May 2012 00:59:46 +0200
- Message-id: <20120510225946.GB20737@mraw.org>
- In-reply-to: <[🔎] 20120510215230.9087.76369.reportbug@einstein.local>
- References: <[🔎] 20120510215230.9087.76369.reportbug@einstein.local>
Hi Javi, Javi Merino <vicho@debian.org> (10/05/2012): > gb mercurial_2.2.1-2 . kfreebsd-amd64 you didn't mean “nmu”, which is for triggering “binNMUs”, meaning a re*build* of an already successfully built package against a new set of packages. The release team is the right entry point for that. You actually want a give back (hence “gb”, as you wrote), meaning a re*try* of a failed build. The buildd maintainers ($arch@buildd.d.o) or the wanna-build team (debian-wb-team@lists.d.o) are the right entry points for those. Anyway, given back. Mraw, KiBi.Attachment: signature.asc
Description: Digital signature
--- End Message ---