Manoj Srivastava <[EMAIL PROTECTED]> schrieb: > reassign 290531 cvs > thanks > > > From what you said, the only cvs-buildpackage command > you had was cvs-update, which is a glorified way of saying > cvs import -m'blah' tetex-base source-dist some-tag-that-we-use
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? Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
