On 2018-04-09 7:51, Ritesh Raj Sarraf wrote:
On Mon, 2018-04-09 at 06:02 +0100, Adam D. Barratt wrote:
Control: reassign -1 ftp.debian.org
On Mon, 2018-04-09 at 09:25 +0530, Ritesh Raj Sarraf wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian....@packages.debian.org
> Usertags: rm
>
> Please remove bpfcc version 0.3.0-4 from the archives. These are
> outdated binaries on unsupported architectures.
>
> With newer 0.5.0 release, we have narrowed down the list of
> architectures where bpfcc can be run. 0.5.0 is already in Unstable.
>
They need removing from unstable, which is ftp-master's territory;
re-
assigning.
That's what I thought initially. But reportbug recommended that I file
it against release.debian.org, for specific package removals from
testing only.
How can anything be removed from testing? There are no bpfcc packages in
testing to remove.
bpfcc version 0.5.0 in unstable is fine. We only want to remove left
over, outdated version 0.3.0, from unsupported architectures. So that,
the newer version can migrate to testing.
Yes. And you need them removed from unstable.
The only thing that's ever removed from testing (other than by britney
automatically) is source packages. If you're in a position where
specific architecture's binary packages need removing, that needs to
happen in unstable.
(If your package only exists in unstable, then clearly that's where the
removal needs to happen in any case.)
Regards,
Adam
