On Sat, Jan 15, 2005 at 06:27:38PM +0100, Frank Küster wrote:
>
>I looked closer at
>http://people.debian.org/~frank/cvs-upgrade_2.99.9.lg, and searched for
>trfonts.map, one of the files that got to the trunk wrongly:
>
>cvs import: Importing /cvs/tetex/tetex-base/metapost/config
>U tetex-base/metapost/config/mfmp.ini
>U tetex-base/metapost/config/mfmp.mp
>U tetex-base/metapost/config/mpost.mp
>U tetex-base/metapost/config/mpost.ini
>cvs import: Importing /cvs/tetex/tetex-base/metapost/support
>N tetex-base/metapost/support/trchars.adj
>N tetex-base/metapost/support/trfonts.map
>
>It seems as if the file added to the upstream tarball since the last
>version get onto the trunk?
>
>I am not completely convinced that the bug is not in cvs-upgrade. In
>older versions, there was a script cvs-co-upgrade (today it's still in
>/usr/share/doc) that generated a list of "cvs add <file>" and "cvs
>remove <file>" commands, to be applied to a checked out working copy.
>
>This script is no longer recommended - doesn't that mean that
>cvs-upgrade now does something like this on itself?

What does the output of cvs-upgrade look like in this situation? I
must admit, I've never used cvs-buildpackage to know exactly how it
works....

-- 
Steve McIntyre, Cambridge, UK.                                [EMAIL PROTECTED]
  Armed with "Valor": "Centurion" represents quality of Discipline,
  Honor, Integrity and Loyalty. Now you don't have to be a Caesar to
  concord the digital world while feeling safe and proud.

Attachment: signature.asc
Description: Digital signature

Reply via email to