Your message dated Mon, 26 May 2014 11:43:13 +0000
with message-id <[email protected]>
and subject line Bug#747043: Removed package(s) from unstable
has caused the Debian Bug report #747043,
regarding RM: python-pipeline; orphaned and conflicts with django-pipeline
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 [email protected]
immediately.)
--
747043: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747043
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
Hello,
python-pipeline was renamed upstream to python-grapevine.
http://jwilk.net/software/python-grapevine
python-pipeline itself has been orphaned:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620067
python-pipeline conflicts with python-django-pipeline, there is a grave
bug opened:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674042
Please remove the python-pipeline package, so we can close the grave
bug.
This has been discussed on debian-devel (see thread titled "future of
python-pipeline package" from 2012 and last week), and nobody has raised
any objections to removing python-pipeline from Debian.
According to the documentation, this this request is suppose to come
from the maintainer (package is orphaned), or QA team (really?), however
as the package is orphaned, it the cause of a grave bug, and it appears
nobody is trying to get this fixed, I am taking on this matter.
Thanks.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
python-pipeline | 0.1.3-3 | source, all
python3-pipeline | 0.1.3-3 | all
------------------- Reason -------------------
RoQA; orphaned, naming conflict with django-pipeline
----------------------------------------------
Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it). Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.
Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.
We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected].
The full log for this bug can be viewed at https://bugs.debian.org/747043
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
