Re: Do we upload buildd arch:all pkgs? (ie, where is python-mplexporter/0.0.1+20140921-4 ?)

2019-08-15 Thread Philipp Kern
On 8/15/2019 4:44 AM, Sandro Tosi wrote:
>>> what can we do?
>>
>> Nothing?
>>
>> kibi@armor:~$ rmadison -s unstable -S python-mplexporter
>> python-mplexporter  | 0.0.1+20140921-3 | unstable   | source, all
>> python-mplexporter  | 0.0.1+20140921-4 | unstable   | source
>> python3-mplexporter | 0.0.1+20140921-4 | unstable   | all
> 
> i see, any idea when the old package will be removed from unstable?
> 

It's more a question for ftp-master manually processing [1]. That said,
the package does not appear there, which might be a bug. If I were you
I'd go and file a binary rm bug, probably.

Kind regards
Philipp Kern

[1] https://ftp-master.debian.org/cruft-report-daily.txt



Re: Do we upload buildd arch:all pkgs? (ie, where is python-mplexporter/0.0.1+20140921-4 ?)

2019-08-14 Thread Sandro Tosi
> > what can we do?
>
> Nothing?
>
> kibi@armor:~$ rmadison -s unstable -S python-mplexporter
> python-mplexporter  | 0.0.1+20140921-3 | unstable   | source, all
> python-mplexporter  | 0.0.1+20140921-4 | unstable   | source
> python3-mplexporter | 0.0.1+20140921-4 | unstable   | all

i see, any idea when the old package will be removed from unstable?

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi



Re: Do we upload buildd arch:all pkgs? (ie, where is python-mplexporter/0.0.1+20140921-4 ?)

2019-08-14 Thread Cyril Brulebois
Hello,

Sandro Tosi  (2019-08-14):
> i hope this is the right address to send my question.
> 
> As part of the effort to remove Python 2, i was looking at the
> reverse-dependencies of matplotlib. I noticed pyhton-mplexporter was
> uploaded recently
> (https://packages.qa.debian.org/p/python-mplexporter.html) to its -4
> revision, but only -3 is available in sid/testing
> (https://packages.debian.org/sid/python-mplexporter).
> 
> It looks like the package was built
> (https://buildd.debian.org/status/package.php?p=python-mplexporter=unstable)
> but somehow it never reached the archive? check for example madison:
> 
> $ rmadison python-mplexporter
> python-mplexporter | 0.0.1+20140921-1 | oldoldstable | source, all
> python-mplexporter | 0.0.1+20140921-2 | oldstable| source, all
> python-mplexporter | 0.0.1+20140921-3 | stable   | source, all
> python-mplexporter | 0.0.1+20140921-3 | unstable | source, all
> python-mplexporter | 0.0.1+20140921-4 | testing  | source
> python-mplexporter | 0.0.1+20140921-4 | unstable | source
> 
> what can we do?

Nothing?

kibi@armor:~$ rmadison -s unstable -S python-mplexporter 
python-mplexporter  | 0.0.1+20140921-3 | unstable   | source, all
python-mplexporter  | 0.0.1+20140921-4 | unstable   | source
python3-mplexporter | 0.0.1+20140921-4 | unstable   | all


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature


Do we upload buildd arch:all pkgs? (ie, where is python-mplexporter/0.0.1+20140921-4 ?)

2019-08-14 Thread Sandro Tosi
Hello,
i hope this is the right address to send my question.

As part of the effort to remove Python 2, i was looking at the
reverse-dependencies of matplotlib. I noticed pyhton-mplexporter was
uploaded recently
(https://packages.qa.debian.org/p/python-mplexporter.html) to its -4
revision, but only -3 is available in sid/testing
(https://packages.debian.org/sid/python-mplexporter).

It looks like the package was built
(https://buildd.debian.org/status/package.php?p=python-mplexporter=unstable)
but somehow it never reached the archive? check for example madison:

$ rmadison python-mplexporter
python-mplexporter | 0.0.1+20140921-1 | oldoldstable | source, all
python-mplexporter | 0.0.1+20140921-2 | oldstable| source, all
python-mplexporter | 0.0.1+20140921-3 | stable   | source, all
python-mplexporter | 0.0.1+20140921-3 | unstable | source, all
python-mplexporter | 0.0.1+20140921-4 | testing  | source
python-mplexporter | 0.0.1+20140921-4 | unstable | source

what can we do?

thanks,
Sandro