Some archive manipulation operation are not automated in the Debian upload process. These procedures should be manually followed by maintainers. This chapter gives guidelines in what to do in these cases.
Sometimes a package will change either its section or its subsection. For instance, a package from the `non-free' section might be GPL'd in a later version; in this case you should consider moving it to `main' or `contrib' (see the Debian Policy Manual for guidelines).
In this case, it is sufficient to edit the package control information
normally and re-upload the package (see the Debian Packaging Manual for
details). Carefully examine the installation log sent to you when the
package is installed into the archive. If for some reason the old
location of the package remains, file a bug against
ftp.debian.org asking that the old location be removed. Give
details on what you did, since it might be a dinstall
bug.
If for some reason you want to completely remove a package (say, if it is an old compatibility library which is not longer required), you need to file a bug against ftp.debian.org asking that the package be removed. Make sure you indicate which distribution the package should be removed from.
If in doubt concerning whether a package is disposable, email
debian-devel@lists.debian.org asking for opinions. Also of
interest is the apt-cache
program from the apt
package. When invoked as apt-cache showpkg
/var/cache/apt/pkgcache.bin package, the program will show
details for package, including reverse depends.
If you decide to remove a package from Incoming, it is nice but not required to send a notification of that to the appropriate announce list (either debian-changes@lists.debian.org or debian-devel-changes@lists.debian.org).
Sometimes you made a mistake naming the package and you need to rename
it. In this case, you need to follow a two-step process. First, set
your debian/control
file to replace and conflict with the
obsolete name of the package (see the Debian Packaging Manual for details). Once you've uploaded
that package, and the package has moved into the archive, file a bug
against ftp.debian.org asking to remove the package with the
obsolete name.
If you can no longer maintain a package, then you should set the package maintainer to Debian QA Group <debian-qa@lists.debian.org> and email wnpp@debian.org indicating that the package is now orphaned. If the package is especially crucial to Debian, you should instead email debian-devel@lists.debian.org asking for a new maintainer.
Periodically, a listing of packages in need of new maintainers will be sent to debian-devel@lists.debian.org list. This list is also available at in the Work-Needing and Prospective Packages document (WNPP), ftp://ftp.debian.org/debian/doc/package-developer/prospective-packages.html and at http://www.debian.org/doc/prospective-packages.html. If you wish to take over maintenance of any of the packages listed in the WNPP, or if you can no longer maintain a packages you have, or you simply want to know if any one is working on a new package, send a message to wnpp@debian.org.
It is not OK to simply take over a package that you feel is neglected -- that would be package hijacking. You can, of course, contact the current maintainer and ask them if you may take over the package. However, without their assent, you may not take over the package. Even if they ignore you, that is still not grounds to take over a package. If you really feel that a maintainer has gone AWOL (absent without leave), post a query to debian-private@lists.debian.org.
If you take over an old package, you probably want to be listed as the package's official maintainer in the bug system. This will happen automatically once you upload a new version with an updated Maintainer: field, although it can take a couple of weeks. If you do not expect to upload a new version for a while, send an email to override-change@debian.org so that bug reports will go to you right away.