Your message dated Sat, 28 Jan 2017 18:44:36 +0100
with message-id <20170128174436.t56utch7l7tn6...@betterave.cristau.org>
and subject line Re: Bug#852970: RM: pbcopper/0.0.1+20161202-2
has caused the Debian Bug report #852970,
regarding RM: pbcopper/0.0.1+20161202-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 ow...@bugs.debian.org
immediately.)
--
852970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: rm
X-Debbugs-Cc: Afif Elghraoui <a...@debian.org>
Afif Elghraoui wrote:
> There is nothing actually wrong with pbcopper, but there is no sense in
> releasing this package for stretch since it basically only exists to
> support unanimity, which did not make the cutoff.
I think the hint for this would be:
# RoM, #852654
remove pbcopper/0.0.1+20161202-2
Regards,
smcv
not actually anywhere near the Cambridge BSP
--- End Message ---
--- Begin Message ---
On Sat, Jan 28, 2017 at 15:45:58 +0000, Simon McVittie wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian....@packages.debian.org
> Usertags: rm
> X-Debbugs-Cc: Afif Elghraoui <a...@debian.org>
>
> Afif Elghraoui wrote:
> > There is nothing actually wrong with pbcopper, but there is no sense in
> > releasing this package for stretch since it basically only exists to
> > support unanimity, which did not make the cutoff.
>
> I think the hint for this would be:
>
> # RoM, #852654
> remove pbcopper/0.0.1+20161202-2
>
Added.
Cheers,
Julien
signature.asc
Description: PGP signature
--- End Message ---
