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

Accepted cvs-buildpackage 4.00 (all source)



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sun,  1 Sep 2002 23:38:55 -0500
Source: cvs-buildpackage
Binary: cvs-buildpackage
Architecture: source all
Version: 4.00
Distribution: unstable
Urgency: low
Maintainer: Manoj Srivastava <srivasta@debian.org>
Changed-By: Manoj Srivastava <srivasta@debian.org>
Description: 
 cvs-buildpackage - Debian package scripts for CVS source trees.
Closes: 153834 154365 155444 156653 157022 157024 157025 157027 157028 157032
Changes: 
 cvs-buildpackage (4.00) unstable; urgency=low
 .
   * NOTE: The option -B to specify a buld command has changed to -C, in
     order not to shadow the -B option of dpkg-buildpackage. This break
     with backward compatibility is the reason for the version bump.
                                                              closes: Bug#155444
   * use which instead of command -v
   * Allow a hook script to be specified in the configuration file.
                                                  closes: Bug#157027, Bug#157028
   * Fixed a wrongly placed diagnositc output.                closes: Bug#156653
   * Removed -jsource-dist:yesterday -jsource-dist:today merge options when
     using cvs-upgrade to incorporate new upstream changes.  These
     commands, however, do not work in general for a CVS source that has
     had its "source-dist" branch updated by cvs-upgrade.  The reason for
     this is that cvs-upgrade, by default, uses the "-d" flag when it
     imports the new upstream source.  Therefore, all of the files are
     tagged with their modification time as the time of import.  If the
     files in the upstream tar file have been modified within the last 24
     hours then everything works fine.  If, on the other hand, the files
     were modified more than a day ago, which is more often the case when
     using the pristine upstream tar, then "source-dist:yesterday" and
     "source-dist:today" evaluate to the same version numbers, and thus the
     branch merge commands listed above miss the changes made in the
     upstream source. Many thanks to Brian Mays for pointing this out.
                                                             closes: Bug#154365
   * Fixed typo This -> Thus                                 closes: Bug#157022
   * Allow one to specify how to acquire the original tar ball in case it
     does not exist in the workdir. Or to complain loudly, and abort, or
     take any other action you wish.  closes: Bug#157024, Bug#153834, Bug#157025
   * export  non_epoch_version upstream_version debian_version cvstag
     package cvs_upstream_tag, so that they shall be available to the hook
     scripts.                                                 closes: Bug#157032
Files: 
 cc46d3f8728d447806d5722c8919ee48 486 devel optional cvs-buildpackage_4.00.dsc
 24490abceb0017babcd81618814fba5a 45857 devel optional cvs-buildpackage_4.00.tar.gz
 b1e98013ae30366cf8b676bf775f8927 57928 devel optional cvs-buildpackage_4.00_all.deb

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

iD8DBQE9cuwNIbrau78kQkwRAun1AKDqnht+oHcWlrDgpZXPcHM5Glk08wCgjmE4
SizYehEh/Xv3/ATSjMtSUyE=
=29dH
-----END PGP SIGNATURE-----


Accepted:
cvs-buildpackage_4.00.dsc
  to pool/main/c/cvs-buildpackage/cvs-buildpackage_4.00.dsc
cvs-buildpackage_4.00.tar.gz
  to pool/main/c/cvs-buildpackage/cvs-buildpackage_4.00.tar.gz
cvs-buildpackage_4.00_all.deb
  to pool/main/c/cvs-buildpackage/cvs-buildpackage_4.00_all.deb



Reply to: