Re: What to do when new version available upstream...
>> "CW" == Chris Waters <firstname.lastname@example.org> writes:
CW> The only tricky bit I've found with the whole cvs-buildpackage
CW> system is that you have to commit test builds and hand export them
CW> for testing purposes if you don't want to constantly overwrite
CW> tags in the cvs repository.
Why this? You still can do a
fakeroot debian/rules binary
[ check the build ]
fakeroot debian/rules clean
in the exported version, can't you?
When you finished, commit the changes and run cvs-buildpackage. Or is
there some hidden problem with this? This is how I do it.