Bug#807002: marked as done (nmu: golang-golang-x-net-dev_0.0+git20151007.b846920+dfsg-1)
Your message dated Fri, 4 Dec 2015 12:04:46 +0100
with message-id <5661734E.9050203@debian.org>
and subject line Re: Bug#807002: nmu: golang-golang-x-net-dev_0.0+git20151007.b846920+dfsg-1
has caused the Debian Bug report #807002,
regarding nmu: golang-golang-x-net-dev_0.0+git20151007.b846920+dfsg-1
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.)
--
807002: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807002
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
User: release.debian.org@packages.debian.org
Usertags: binnmu
Severity: normal
X-Debbugs-CC: paultag@debian.org, pkg-go-maintainers@lists.alioth.debian.org
Hello,
Due to a typo of mine while preparing the upload, src:golang-go.crypto
1:0.0~git20151201.0.7b85b09-1 was uploaded and accidentally overwrote
the "golang-golang-x-net-dev" binary package from
src:golang-golang-x-net-dev.
I've pushed a new upload of src:golang-go.crypto fixing the issue
there (which is in binNEW now), but in talking with Paul he mentioned
that a binNMU _should_ be enough to fix the situation with the binary
package of src:golang-golang-x-net-dev, and that I ought to file a bug
here with RT to get some help figuring out whether that's really
sufficient (or whether we need to also do an FTP team RM or epoch bump
the -net package).
nmu golang-golang-x-net-dev_0.0+git20151007.b846920+dfsg-1 . all . -m
'Rebuild to bring back the proper binary packages'
♥,
- Tianon
4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4
--- End Message ---
--- Begin Message ---
On 04/12/15 00:55, Tianon Gravi wrote:
> Package: release.debian.org
> User: release.debian.org@packages.debian.org
> Usertags: binnmu
> Severity: normal
> X-Debbugs-CC: paultag@debian.org, pkg-go-maintainers@lists.alioth.debian.org
>
> Hello,
>
> Due to a typo of mine while preparing the upload, src:golang-go.crypto
> 1:0.0~git20151201.0.7b85b09-1 was uploaded and accidentally overwrote
> the "golang-golang-x-net-dev" binary package from
> src:golang-golang-x-net-dev.
>
> I've pushed a new upload of src:golang-go.crypto fixing the issue
> there (which is in binNEW now), but in talking with Paul he mentioned
> that a binNMU _should_ be enough to fix the situation with the binary
> package of src:golang-golang-x-net-dev, and that I ought to file a bug
> here with RT to get some help figuring out whether that's really
> sufficient (or whether we need to also do an FTP team RM or epoch bump
> the -net package).
>
> nmu golang-golang-x-net-dev_0.0+git20151007.b846920+dfsg-1 . all . -m
> 'Rebuild to bring back the proper binary packages'
We can't binNMU arch:all packages.
Besides, that is not going to work. A binNMU would give you
golang-golang-x-net-dev 0.0+git20151007.b846920+dfsg-1+b1
But golang-go.crypto is building:
golang-golang-x-net-dev 1:0.0~git20151201.0.7b85b09-1
Which is higher because of the epoch.
So AFAICS you need a sourceful upload with an epoch to fix this.
Cheers,
Emilio
--- End Message ---
Reply to: