Package removal requests Contents Package removal requests Do you need to request removal? Removals from testing, stable and oldstable Removals from backports Before requesting removal Reverse Dependencies Who are you?
Upgrade path How to request removal Examples Do you need to request removal? As part of their archive maintenance role, the ftp-master team periodically daily, cron-job run a tool which searches for packages that should be removed.
This tool used to be known as "rene" and is still often referred to as such but has now become the "cruft-report" sub-command of dak.
In the cases handled by this tool, there is no need to request that your package be removed, they are handled in batches from times to times apart from the "Architecture Not Allowed In Source" case, which still need a removal request. You can view a recent copy of the tool's output at http: Debian package relationships dating most common cases that are handled by the tool are: Binary packages no longer built from any source package "NBS", i.
In addition they also handle removal of obsolete testing-security packages at the request of the testing security team. Removals from the oldstable, stable and testing distributions should be requested by e-mailing the Stable Release Managers debian-release lists. Per-architecture from testing are not handled by the Release Managers directly, but rather as a result of the package's state in unstable propagating to testing.
For example, assume that package foobar exists in both testing and unstable for s but it has been discovered that, despite building, the binaries do not work on that architecture.
In order to get the binary package removed from testing, you need to ensure that it is no longer built in unstable by e. Once the package is otherwise ready to transition to testing, the s binary in testing will be automatically removed during the transition.
Note that in most cases it is unnecessary to request removal of your package from both testing and unstable. Once the package is removed from unstable, it will automatically be removed from testing once there are no dependencies keeping it there.
If you do need the package simultaneously removed from both distributions, you will need to file a removal bug for unstable as usual, and contact the Release Managers to request removal from testing. Where possible, this will include suggesting either via bugs or direct contact with the maintainer a means of the dependent package handling the removal.
The ftp-team usually does not remove a package that still has a reverse dependency. For instance, if you are removing an obsolete version of a library that the dependent package is still using, you should suggest that they transition to the current version.
If you are a DD, you can execute the folllowing command on mirror. If this "Debian package relationships dating" to all reverse dependencies listed, you can go ahead with the removal request.
The ftp-masters will need to know your relationship to the package if any in order to process your request. In most cases, they will expect the request to be made by the maintainer including co-maintainers although there are a number of other parties who might be expected to submit removal requests for various reasons: Porters requesting removal of binaries for "Debian package relationships dating" architecture The Release Managers or Stable Release Managers, for packages which they do not consider to be suitable for release or which should be removed from stable although the latter happens very rarely The QA team.
In all cases, if there is a maintainer and it's not you, mention the maintainer's opinion or, if you don't know it, mention how and when you tried to contact them. If you didn't try to contact the maintainer, do so first.
If after a few weeks and some prodding there's still no reaction, and you believe the ftp-master team would process the removal anyway despite the maintainer not having replied, you might consider reassigning the bug yourself.
Upgrade path If you're requesting a removal because of a package rename, give some Debian package relationships dating to a proper upgrade path for existing users. Consider building a dummy upgrade pseudo-package from the new, renamed package.
For example, 'iceape' in etch also builds dummy 'mozilla', 'mozilla-browser', etc packages. Once such a dummy pseudo-package has appeared in a stable release, you can then simply stop building it and it'll get semi-automatically removed "Debian package relationships dating" above.
If the old name of the package has never appeared in a stable release, it also makes no sense to have it do so; make sure that such dummy packages do not appear in stable releases in this case. How to request removal File a bug against the ftp. The ftp-masters do not take account of the severity of the bug reported when processing removals and, except in very rare cases e.
Removal Debian package relationships dating should thus be filed as severity "normal"; if you believe the request to be "important" or "serious" then simply provide appropriate reasoning in the report.
The subject line of the bug report should be in the format described in the "About removals in Debian" section at the top of http: Examples The m68k porters request that bigpackage's m68k binaries be removed as they do not build RM: If a version of the package built on hppa is present in testing, this will stop the new version of foobar entering testing due to the "missing" hppa Debian package relationships dating. This can occur if, for example, the package was built and uploaded by neither the maintainer nor an official auto-builder, or if the list of supported architectures is being reduced.
Package wibble is orphaned, has release critical bugs and appears to have been abandoned upstream. In this case the package has never been part of a Debian release and the QA team request its removal.
Upgrade path How to request removal Examples. Hosting provided by Metropolitan Area Network Darmstadt.