Re: What to do when new version available upstream...

>> "CW" == Chris Waters <[EMAIL PROTECTED]> 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 thi

Re: What to do when new version available upstream...

Hi, >>"Chris" == Chris Waters <[EMAIL PROTECTED]> writes: Chris> The only tricky bit I've found with the whole cvs-buildpackage Chris> system is that you have to commit test builds and hand export Chris> them for testing purposes if you don't want to constantly Chris> overwrite tags in the cvs

Re: dpkg-source: cannot represent change

Turbo Fredriksson wrote: > Adrian Bridgett <[EMAIL PROTECTED]> wrote: > > On Mon, Mar 01, 1999 at 01:59:25PM +0100, Turbo Fredriksson wrote: > > > Anything I can do to override this? It's on purpose, so that I don't > > > have to include the whole pike/0.6 tree (the 'pike_0.6.110.orig.tar.gz' > > >

Re: dpkg-source: cannot represent change

Adrian Bridgett <[EMAIL PROTECTED]> wrote: > On Mon, Mar 01, 1999 at 01:59:25PM +0100, Turbo Fredriksson wrote: > > Anything I can do to override this? It's on purpose, so that I don't > > have to include the whole pike/0.6 tree (the 'pike_0.6.110.orig.tar.gz' > > tarball)... > > -rm pike/0