[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#685039: marked as done (developers-reference: please document what is needed to reintroduce a package)

Your message dated Thu, 16 May 2013 23:18:13 +0000
with message-id <E1Ud7R7-0007Fh-IJ@franck.debian.org>
and subject line Bug#685039: fixed in developers-reference 3.4.10
has caused the Debian Bug report #685039,
regarding developers-reference: please document what is needed to reintroduce a package
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 owner@bugs.debian.org
immediately.)


-- 
685039: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685039
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: developers-reference
Severity: wishlist
Tags: patch

How to reintroduce packages isn't fully obvious to everybody and there
some details that rely on services or information some folks don't know
about. I have written a section for devref with the information I know
about. Please apply the attached rough patch to document this process.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise

Index: common.ent
===================================================================
--- common.ent	(revision 9307)
+++ common.ent	(working copy)
@@ -28,6 +28,7 @@
 <!ENTITY www-debian-org "www.debian.org">
 <!ENTITY ftp-debian-org "ftp.debian.org">
 <!ENTITY release-debian-org "release.debian.org">
+<!ENTITY snap-debian-org "snapshot.debian.org">
 <!ENTITY lists-host "lists.debian.org">
 <!ENTITY archive-host "archive.debian.org">
 <!ENTITY keyserver-host "keyring.debian.org">
Index: pkgs.dbk
===================================================================
--- pkgs.dbk	(revision 9307)
+++ pkgs.dbk	(working copy)
@@ -1238,7 +1238,7 @@
 </section>
 
 <section id="archive-manip">
-<title>Moving, removing, renaming, adopting, and orphaning packages</title>
+<title>Moving, removing, reintroducing, renaming, adopting, and orphaning packages</title>
 <para>
 Some archive manipulation operations are not automated in the Debian upload
 process.  These procedures should be manually followed by maintainers.  This
@@ -1385,6 +1385,48 @@
 
 </section>
 
+<section id="reintroducing-pkgs">
+<title>Reintroducing packages</title>
+<para>
+Packages are often removed due to release-critical bugs, absent maintainers,
+too few users or poor quality in general. There are some things you should be
+aware of when reintroducing removed packages.
+</para>
+<para>
+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
+<ulink url="http://&ftp-master-host;/removals.html";>removals</ulink>.
+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.
+</para>
+<para>
+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
+(<xref linkend="newpackage"/>).
+</para>
+<para>
+You should base your work on the latest packaging available that is suitable.
+That might be the latest version from <literal>unstable</literal>, which will
+still be present in the <ulink url="&snap-debian-org;">snapshot archive</ulink>.
+Or the version control system used by the previous maintainer might contain
+newer packaging. 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.
+</para>
+<para>
+Package removals usually 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
+<literal>+rm</literal> and still apply. Any that no longer apply should be
+marked as fixed in the correct version if that is known.
+</para>
+</section>
+
 <section id="s5.9.3">
 <title>Replacing or renaming packages</title>
 <para>

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
--- Begin Message --- 
Source: developers-reference
Source-Version: 3.4.10

We believe that the bug you reported is fixed in the latest version of
developers-reference, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 685039@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
David Prévot <taffit@debian.org> (supplier of updated developers-reference package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 16 May 2013 18:35:23 -0400
Source: developers-reference
Binary: developers-reference developers-reference-de developers-reference-fr developers-reference-ja
Architecture: source all
Version: 3.4.10
Distribution: unstable
Urgency: low
Maintainer: Developers Reference Maintainers <debian-policy@lists.debian.org>
Changed-By: David Prévot <taffit@debian.org>
Description: 
 developers-reference - guidelines and information for Debian developers
 developers-reference-de - guidelines and information for Debian developers, in German
 developers-reference-fr - guidelines and information for Debian developers, in French
 developers-reference-ja - guidelines and information for Debian developers, in Japanese
Closes: 652044 685039 685646 708290
Changes: 
 developers-reference (3.4.10) unstable; urgency=low
 .
   * Team upload.
 .
   [ Raphaël Hertzog ]
   * Add recommendations to re-introduce packages. Thanks to Paul Wise for the
     patch. Closes: #685039
   * Drop paragraph about vanilla debian/rules files which mainly points to a
     no-longer working link.
 .
   [ Hideki Yamane ]
   * Introduce epub support. Closes: #652044
 .
   [ Thijs Kinkhorst ]
   * Update versioning advice for uploads to stable/testing. Closes: #685646
   * Advise to use codename-security instead of stable-security.
     Closes: #708290
 .
   [ Translation updates ]
   * French by David Prévot.
   * Japanese by victory.
   * German by Chris Leick.
 .
   [ David Prévot ]
   * debian/control:
     - Update Standards-Version to 3.9.4 (no change required).
     - Use canonical URL for Vcs-Svn.
Checksums-Sha1: 
 aae9f21a6b4f50d29b82738c807a18345c3e2d7e 2266 developers-reference_3.4.10.dsc
 4f6a6586394a6f6be8b0c7c956a52bf681ab93bb 449312 developers-reference_3.4.10.tar.xz
 d4265ac72f05049c118e11a46686b54eefcbadbe 854202 developers-reference_3.4.10_all.deb
 1d2afba7fc6dc1fa9e983056217a0c019ef89a9b 953644 developers-reference-de_3.4.10_all.deb
 d793ed4ba18bdfe8b5af7eabaf263ec43acc9bd6 931110 developers-reference-fr_3.4.10_all.deb
 248b4127c3739381d254810daa1b41da9c043516 1395780 developers-reference-ja_3.4.10_all.deb
Checksums-Sha256: 
 7dd1fa6bc36773df0f9ef9226dbf7a7f882f7082c511bf0658753e8dd049e744 2266 developers-reference_3.4.10.dsc
 542f2b173feddc0655a723ecd8479a68d4572f67c678f17f5b1b4315ad1fa378 449312 developers-reference_3.4.10.tar.xz
 b1b22d04f4fcf0b6e548cab80fe3ef83d3af49b2788b76b6f2449ddf912fe92f 854202 developers-reference_3.4.10_all.deb
 5edc121ed7d1010c51c529382cf38853c5de3c7c9c38042fc3b660db7861edf8 953644 developers-reference-de_3.4.10_all.deb
 dac37b1cc8e6b582e425044efe4940d7dfd69e51e8b8c7fb0737629878ba96f3 931110 developers-reference-fr_3.4.10_all.deb
 06a5cf5aff04eaa7f63f4fa4b1b844bb8588462b261b0b321b88e2e6bd5eda57 1395780 developers-reference-ja_3.4.10_all.deb
Files: 
 a70deb0ed35fec064065f2cecc7778df 2266 doc optional developers-reference_3.4.10.dsc
 785c87f4c535310314ecd62681ab319d 449312 doc optional developers-reference_3.4.10.tar.xz
 febe4afa584f6f8d5a4750b9bcf71c77 854202 doc optional developers-reference_3.4.10_all.deb
 9937cbf8a94d44dd29697bf4fec54add 953644 doc optional developers-reference-de_3.4.10_all.deb
 05d227bfa4d85bc5ced849253adf914f 931110 doc optional developers-reference-fr_3.4.10_all.deb
 0de68d9c26035c475c5db86838971d57 1395780 doc optional developers-reference-ja_3.4.10_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJRlWNcAAoJELgqIXr9/gnyGK0P/054pF/uMQpcc8iNCnc1rvaP
nxE7O9Q9NGAYYOwV9QnoKWohQmSAvpwXXuTHOESz+KvErmvf8Xaei8j2rbDJ9A94
CAJMkCMh8xsznK2VZwtA0kZwee1YaDPbetdq6YyN8MN3RmTXger5Qk6uNF5988CD
qDJoZmRN+E2nZn2EOQWGHJCFm5ZpSZoaVtsIloLmVOXwBs4OOd2YbmDWsp4ILV09
xfpAD66LdSZ3q9hp2O90/LywYtSRp/mEKdCMzRmkqmIyqbZVFbNwIgglxy5AEPgN
qgZVRgPy67YI5JkNNHxOdcw70vHQZeCqDwdZUjtvEHKwShd9dEfKdIYGr1Vr/jzc
NHpD6tdAn9/3l9YnWg/6bvjtFQeGV3LfDutU4gqMS0Cz3ivofKuP8Q8+VFEkgY1H
5BER2SW441nSyUA8PjCQ2HuN/D93WXCDcHqA56vwDdQRRJrConQKFYvt5EAy1Cm3
gWGEo3k4siPkyjg9Ou+MZtiALZm1FFkKZZE71MvUjkNGdlBFlfMr3dP0U8bT91gC
9CtfjvPcVCSIcwitS5eOzsSlVJsMbLZOGi6Y9odOI5x76aeGVgKzUx92vwwKAwf/
CK31ofbiw2ukz4WEZt80noXs/6fwiLZ9D/A118O3EFJnhv8o87bGeXHVQhKV0gmG
M45UlpGUQAH0oskbUaeo
=suG3
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: