From 353000ffb797d38970738f4454ea46be66e061ec Mon Sep 17 00:00:00 2001 From: hertzog Date: Mon, 17 Sep 2012 15:22:09 +0000 Subject: [PATCH] Add recommendations to re-introduce packages. Thanks to Paul Wise for the patch. Closes: #685039 git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@9362 313b444b-1b9f-4f58-a734-7bb04f332e8d --- common.ent | 1 + debian/changelog | 7 +++++++ pkgs.dbk | 50 +++++++++++++++++++++++++++++++++++++++++++++++- 3 files changed, 57 insertions(+), 1 deletion(-) diff --git a/common.ent b/common.ent index 9337c68..2071002 100644 --- a/common.ent +++ b/common.ent @@ -28,6 +28,7 @@ + diff --git a/debian/changelog b/debian/changelog index 9cbfe41..73b5d5e 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +developers-reference (3.4.10) UNRELEASED; urgency=low + + * Add recommendations to re-introduce packages. Thanks to Paul Wise for the + patch. Closes: #685039 + + -- Raphaël Hertzog Mon, 17 Sep 2012 17:20:49 +0200 + developers-reference (3.4.9) unstable; urgency=low * Team upload. diff --git a/pkgs.dbk b/pkgs.dbk index 8e64063..07b3f85 100644 --- a/pkgs.dbk +++ b/pkgs.dbk @@ -1238,7 +1238,7 @@ on &ftp-master-host;.
-Moving, removing, renaming, adopting, and orphaning packages +Moving, removing, renaming, orphaning, adopting, and reintroducing packages Some archive manipulation operations are not automated in the Debian upload process. These procedures should be manually followed by maintainers. This @@ -1486,6 +1486,54 @@ they will continue to receive the bugs during that time.
+
+Reintroducing packages + +Packages are often removed due to release-critical bugs, absent maintainers, +too few users or poor quality in general. While the process of reintroduction +is similar to the initial packaging process, you can avoid some pitfalls by +doing some historical research first. + + +You should check why the package was removed in the first place. This +information can be found in the removal item in the news section of the PTS +page for the package or by browsing the log of +removals. +The removal bug will tell you why the package was removed and will give some +indication of what you will need to work on in order to reintroduce the package. +It may indicate that the best way forward is to switch to some other piece of +software instead of reintroducing the package. + + +It may be appropriate to contact the former maintainers to find out if +they are working on reintroducing the package, interested in co-maintaining +the package or interested in sponsoring the package if needed. + + +You should do all the things required before introducing new packages +(). + + +You should base your work on the latest packaging available that is suitable. +That might be the latest version from unstable, which will +still be present in the snapshot archive. + + +The version control system used by the previous maintainer might contain useful +changes, so it might be a good idea to have a look there. Check if the control +file of the previous package contained any headers linking to the version +control system for the package and if it still exists. + + +Package removals from unstable (not testing, stable or oldstable) trigger the +closing of all bugs related to the package. You should look through all the +closed bugs (including archived bugs) and unarchive and reopen any that were +closed in a version ending in +rm and still apply. Any that +no longer apply should be marked as fixed in the correct version if that is +known. + +
+
-- 2.30.2