rpms/mlt/devel .cvsignore, 1.4, 1.5 mlt.spec, 1.4, 1.5 sources,
1.4, 1.5
Michael Schwendt
mschwendt at gmail.com
Fri Dec 11 11:57:29 CET 2009
On Fri, 11 Dec 2009 11:33:34 +0100, Zarko wrote:
> Strange...
>
> I do not know why log is empty, and why cvs-import.sh erase the old
> changelog entry. I'm little confused.
> I only follow this link
> http://rpmfusion.org/Contributors#head-ecd81860c9b7e5192904b03bd0ab6f07980b81a6when
> import my packages.
It's in the nature of cvs-import.sh automation. The script creates a fresh
working-copy by checking out the current package. Then it assumes that the
files you want it to import are modifications of the working-copy
(removing lines is a valid operation, too). It cannot compare any
revisions of the files, because you only provide your changes in a
src.rpm.
Better is to not use cvs-import.sh for _updates_. Modify files in your cvs
working-copy of the package. Plain cvs commit will compare revisions, warn
about out-of-date working-copies, and try to _merge_ additions instead of
overwriting/reverting newer revisions in cvs.
More information about the rpmfusion-developers
mailing list