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

Bug#467102: 5.9.3: when renaming a package, new name should also PROVIDE old name



tag 467102 + patch
thanks

Heya,

LI Daobing <lidaobing@gmail.com> wrote:

> in the first paragraph of Debian Developer's Reference 5.9.3[1]. I think the 
> new name should also provide the obsolete name, it should be changed to [2].
[...]
> [2]
> When you make a mistake naming your package, you should follow a two-step 
> process to rename it. First, set your debian/control file to replace, 
> conflict with and provide the obsolete name of the package (see the Debian 
> Policy Manual for details). // snip

Here's a complete patch for this issue. Please review:

Index: pkgs.dbk
===================================================================
--- pkgs.dbk	(revision 5223)
+++ pkgs.dbk	(working copy)
@@ -1339,14 +1339,20 @@
 <section id="s5.9.3">
 <title>Replacing or renaming packages</title>
 <para>
-When you make a mistake naming your package, you should follow a two-step
-process to rename it.  First, set your <filename>debian/control</filename> file
-to replace and conflict with the obsolete name of the package (see the <ulink
-url="&url-debian-policy;">Debian Policy Manual</ulink> for
-details).  Once you've uploaded the package and the package has moved into the
-archive, file a bug against <literal>ftp.debian.org</literal> asking to remove
-the package with the obsolete name.  Do not forget to properly reassign the
-package's bugs at the same time.
+When the upstream maintainers for one of your packages chose to
+rename their software (or you made a mistake naming your package),
+you should follow a two-step process to rename it. In the first
+step, change the <filename>debian/control</filename> file to
+reflect the new name and to replace, provide and conflict with the
+obsolete package name (see the <ulink url="&url-debian-policy;">
+Debian Policy Manual</ulink> for details).  Please note that you
+should only add a <literal>Provides</literal> relation if all
+packages depending on the obsolete package name continue to work
+after the renaming. Once you've uploaded the package and the package
+has moved into the archive, file a bug against <literal>
+ftp.debian.org</literal> asking to remove the package with the
+obsolete name (see <xref linkend="removing-pkgs"/>).  Do not forget
+to properly reassign the package's bugs at the same time.
 </para>
 <para>
 At other times, you may make a mistake in constructing your package and wish to

Marc
-- 
BOFH #409:
The vulcan-death-grip ping has been applied.

Attachment: pgp8CAokUqeLV.pgp
Description: PGP signature


Reply to: