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. 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. Currently, it is stuck because of: excuses: 14 days old (5 needed) missing build on i386: bpfcc-lua, libbpfcc (from 0.3.0-4) missing build on armel: bpfcc-lua, libbpfcc (from 0.3.0-4) missing build on armhf: bpfcc-lua, libbpfcc (from 0.3.0-4) missing build on mips: bpfcc-lua, libbpfcc (from 0.3.0-4) missing build on mips64el: libbpfcc (from 0.3.0-4) missing build on mipsel: bpfcc-lua, libbpfcc (from 0.3.0-4) missing build on s390x: libbpfcc (from 0.3.0-4) old binaries left on all: bpfcc-tools, bpfcc-tools, bpfcc-tools, bpfcc-tools, bpfcc-tools, bpfcc-tools, bpfcc-tools, libbpfcc-dev, libbpfcc-dev, libbpfcc-dev, libbpfcc-dev, libbpfcc-dev, libbpfcc-dev, libbpfcc-dev, python-bpfcc, python-bpfcc, python-bpfcc, python-bpfcc, python-bpfcc, python-bpfcc, python-bpfcc (from 0.3.0-4) (but ignoring cruft, so nevermind) Piuparts tested OK - https://piuparts.debian.org/sid/source/b/bpfcc.html Not considered -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System
signature.asc
Description: This is a digitally signed message part
