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

1999-03-06 Thread Josip Rodin
On Sat, Mar 06, 1999 at 09:41:35AM +, Jules Bean wrote: > > > > I usually extract the new one (or apply a patch if that is the method), > > > > gunzip -dc old_version.diff.gz > somefile, then edit that 'somefile' and > > > > replace all instances of progdirectory-1.2.0 with progdirectory-1.2.1.

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

1999-03-06 Thread Jules Bean
On 6 Mar 1999, John Lapeyre wrote: > Jules Bean <[EMAIL PROTECTED]> writes: > > > > > On Wed, Feb 24, 1999 at 11:57:02AM -0800, Sudhakar Chandrasekharan wrote: > > > > 1. tar zxvf upstream_src.tgz > > > > 2. Apply the .diff that was generated when I produced 0.26.2 (and get > > > > rid > > > >

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

1999-03-06 Thread John Lapeyre
Jules Bean <[EMAIL PROTECTED]> writes: > > On Wed, Feb 24, 1999 at 11:57:02AM -0800, Sudhakar Chandrasekharan wrote: > > > 1. tar zxvf upstream_src.tgz > > > 2. Apply the .diff that was generated when I produced 0.26.2 (and get rid > > > of the files like changelog, control etc.) > > > > I usual

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

1999-03-03 Thread Roderick Schertler
On Mon, 01 Mar 1999 14:20:26 -0800, Chris Waters <[EMAIL PROTECTED]> said: > > The only tricky bit I've found with the whole cvs-buildpackage system > is that you have to commit test builds and hand export them for testing > purposes if you don't want to constantly overwrite tags in the cvs > repos

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

1999-03-02 Thread Martin Bialasinski
>> "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...

1999-03-02 Thread Manoj Srivastava
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: What to do when new version available upstream...

1999-03-01 Thread Chris Waters
Stephane Bortzmeyer wrote: > "Using CVS together with Debian GNU/Linux packages" > suggests another solution, > based on CVS. It seems very nice (I use CVS for other projects) but I > did not use it for Debian yet (any experiences/war stories?). I can repor

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

1999-03-01 Thread Jules Bean
On Mon, 1 Mar 1999, Josip Rodin wrote: > On Mon, Mar 01, 1999 at 08:55:57AM +, Jules Bean wrote: > > > I usually extract the new one (or apply a patch if that is the method), > > > gunzip -dc old_version.diff.gz > somefile, then edit that 'somefile' and > > > replace all instances of progdirec

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

1999-03-01 Thread Manoj Srivastava
Hi, cvs-inject is merely a front end to cvs (specifically: cvs import -ko ; cvs export; cvs add debian; cvs commit ) cvs-upgrade is merely cvs import. This is the recommended way of using CVS, AFAIK, and the problems with deleted files (Attic files, etc), and problems w

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

1999-03-01 Thread Josip Rodin
On Mon, Mar 01, 1999 at 08:55:57AM +, Jules Bean wrote: > > I usually extract the new one (or apply a patch if that is the method), > > gunzip -dc old_version.diff.gz > somefile, then edit that 'somefile' and > > replace all instances of progdirectory-1.2.0 with progdirectory-1.2.1. > > Then ap

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

1999-03-01 Thread Marcelo E. Magallon
Hi Stephane, On Mon, Mar 01, 1999 at 04:05:43PM +0100, Stephane Bortzmeyer wrote: > "Using CVS together with Debian GNU/Linux packages" > suggests another solution, based > on CVS. It seems very nice (I use CVS for other projects) but I did not > use it for

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

1999-03-01 Thread Stephane Bortzmeyer
On Saturday 27 February 1999, at 18 h 14, the keyboard of Josip Rodin <[EMAIL PROTECTED]> wrote: > I usually extract the new one (or apply a patch if that is the method), > gunzip -dc old_version.diff.gz > somefile, then edit that 'somefile' and > replace all instances of progdirectory-1.2.0 with

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

1999-03-01 Thread Jules Bean
On Sat, 27 Feb 1999, Josip Rodin wrote: > On Wed, Feb 24, 1999 at 11:57:02AM -0800, Sudhakar Chandrasekharan wrote: > > 1. tar zxvf upstream_src.tgz > > 2. Apply the .diff that was generated when I produced 0.26.2 (and get rid > > of the files like changelog, control etc.) > > I usually extract t

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

1999-02-27 Thread Josip Rodin
On Wed, Feb 24, 1999 at 11:57:02AM -0800, Sudhakar Chandrasekharan wrote: > 1. tar zxvf upstream_src.tgz > 2. Apply the .diff that was generated when I produced 0.26.2 (and get rid > of the files like changelog, control etc.) I usually extract the new one (or apply a patch if that is the method),

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

1999-02-24 Thread Shaleh
On 24-Feb-99 Sudhakar Chandrasekharan wrote: > What do I typically do when there is a new version available upstream? I > previously packaged the aspell spell checker version 0.26.2. The new > upstream version is 0.27. > > Do I - > > 1. tar zxvf upstream_src.tgz > 2. Apply the .diff that was

What to do when new version available upstream...

1999-02-24 Thread Sudhakar Chandrasekharan
What do I typically do when there is a new version available upstream? I previously packaged the aspell spell checker version 0.26.2. The new upstream version is 0.27. Do I - 1. tar zxvf upstream_src.tgz 2. Apply the .diff that was generated when I produced 0.26.2 (and get rid of the files li