CVS-CO-UPGRADE(1)

NAME
cvs-co-upgrade - utility for handling deleted and new files during upgrades

SYNOPSIS
cvs-co-upgrade [options] <package name> <old upstream version> <new upstream version>

DESCRIPTION
This manual page explains the Debian cvs-co-upgrade utility, which creates cvs commands to handle file deleted and added between two upstream source package versions. It is used to help upgrade the main trunk (or the checked out version) of a Debian source package (and probably any two tar files, for that matter). The program creates a list of cvs commands to that should be applied to the checked out source to take care of new or deleted files in the new upstream source.

It expects the package name, the older upstream version number, and the new upstream version on the command line. It also expects to find properly conditioned upstream sources (for both the previous and the new upstream version), in .orig.tar.gz format, in the cvs-buildpackage work directory Please note that the cvs-buildpackage work directory referred to here is the scratch directory where this program works, not the directory that the human uses to work in.

Given the command cvs-co-upgrade foo 0.1.0 0.2.2 It looks for foo_0.1.0.orig.tar.gz and foo_0.2.2_orig.tar.gz, builds a listing of files on each tarball, diff's them, and outputs the list of cvs commands that should be applied in the checked out source. One may then try cvs-co-upgrade foo 0.1.0 0.2.2 | sh -s to apply the changes required.

cvs-co-upgrade reads the same config file /etc/cvsdeb.conf as the the other cvs-* utilities do. People may use of the dry-run option to inspect the steps this utility takes.

OPTIONS

-h  Print out a usage message.

-M<module>
    The name of the CVS module. This argument overrides the settings in the environment variable CVSDEB_MODULE. There is no corresponding config file variable.

-x<prefix>
    The name of the default CVS prefix. This argument overrides the settings in the environment variable CVSDEB_PREFIX, which in turn overrides the setting in the configuration file, conf_prefix.

-R<root directory>
    Root of the original sources archive. We expect to find the <package name>_<version>.orig.tar.gz file under <root directory>/package name>/ unless the cvs-buildpackage work directory has been set, or we want to export the original sources from the vendor branch of the CVS tree. If the cvs-buildpackage work directory is set anywhere, (command line, configuration file, environment variable), the root directory value is ignored, since we only need the root directory to set defaults for the work directory. This argument overrides the settings in the environment variable CVSDEB_ROOTDIR, and the configuration file variable conf_rootdir. Please note that the cvs-buildpackage work directory referred to here is the scratch directory where this program works, not the directory that the human uses to work in.

-W<work directory>
    The working directory, into which the sources will be exported out of CVS and which should contain the original <package name>_<version>.orig.tar.gz Please note that it is not essential to have the original sources, as this script will check out the vendor branch version tagged as upstream_version_<version> (without the Debian revision). Setting this variable overrides the settings for the root directory. This argument also overrides the settings in the environment variable CVSDEB_WORKDIR, and in the configuration file variable conf_workdir.

-d<number>
    Turn on debugging output. This lists the version numbers, the work and root directories, as well as the CVS tag used to export the sources. This overrides the DEBUG variable in the configuration file.

-n  The no exec (or dry-run) option, causing cvs-co-upgrade to print out all actions that would be taken without actually executing them.

-v  Make the utility more verbose.

FILES
Apart from the runtime options, cvs-co-upgrade also looks for site-wide defaults in the file /etc/cvsdeb.conf. After that, it looks for and reads ~/.cvsdeb.conf The default configuration allows there to be a site-wide override for the root or the cvs-buildpackage working directories on the site, but the cvsdeb.conf files are actually Bourne shell snippets, and any legal shell directives may be included in there. Note: Caution is urged with this file, since you can totally change the way that the script behaves by suitable editing this file.

SEE ALSO
cvs-buildpackage(1), cvs-inject(1), cvsdeb.conf(5), cvs(1).

AUTHOR
This manual page was written Manoj Srivastava <srivasta@debian.org>, for the Debian GNU/Linux system.