From 933cc23b634dc089f3ee6dfde76b4b6bf432be7d Mon Sep 17 00:00:00 2001 From: he Date: Tue, 10 Jun 2008 22:27:52 +0000 Subject: [PATCH] Clarify instructions for replacing/renaming binary packages, pointing out that using Provides is sometimes advisable. Closes: #467102 git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@5229 313b444b-1b9f-4f58-a734-7bb04f332e8d --- debian/changelog | 3 +++ pkgs.dbk | 22 ++++++++++++++-------- 2 files changed, 17 insertions(+), 8 deletions(-) diff --git a/debian/changelog b/debian/changelog index 8f4ffa2..437adca 100644 --- a/debian/changelog +++ b/debian/changelog @@ -37,6 +37,9 @@ developers-reference (3.4.0) UNRELEASED; urgency=low need to inform the maintainers you reassign the bug to. Also hint to using cloned bugs to avoid re-reporting. Heavily based on patch by Marc Haber - thanks for the work! Closes: #484806 + * Clarify instructions for replacing/renaming binary packages, + pointing out that using Provides is sometimes advisable. Closes: + #467102 -- Marc 'HE' Brockschmidt Sun, 01 Jun 2008 16:26:33 +0200 diff --git a/pkgs.dbk b/pkgs.dbk index 05ebf11..1e0b29d 100644 --- a/pkgs.dbk +++ b/pkgs.dbk @@ -1339,14 +1339,20 @@ occur too often anyway.
Replacing or renaming packages -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 and conflict with the obsolete name of the package (see the Debian Policy Manual for -details). Once you've uploaded the 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. 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 debian/control file to +reflect the new name and to replace, provide and conflict with the +obsolete package name (see the +Debian Policy Manual for details). Please note that you +should only add a Provides 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 +ftp.debian.org asking to remove the package with the +obsolete name (see ). Do not forget +to properly reassign the package's bugs at the same time. At other times, you may make a mistake in constructing your package and wish to -- 2.30.2