On 2004-03-18 Stephen Gran <[EMAIL PROTECTED]> wrote: > This one time, at band camp, Colin Watson said: > > There's ~, but you can't use that until sarge has been released. > > > > In the absence of that, something like 0.69-really-0.70-rc-1 (or what > > you suggest) is a common workaround. It's not too bad to change the > > tarball name.
> OK, if it's not a big deal to change the tarball name, then I will just > go ahead and do that. I was thinking it made for more complication > than it apparently does - the thing I'm worried about is uploading when > 0.70 comes out, and I am uploading a new tarball. If both are named > 0.70 (wuith only the revision changing from -0rc1 to -1), I thought the > pool managing scripts would complain. I think you are misparsing Colin. The pool managing scripts will definitely complain if you upload a new foish-bar_0.70.orig.tar.gz. You /cannot/ replace a foish-bar_0.70.orig.tar.gz in the archive without changing the name. You need to do this: wget ftp://upsteam.org/foish-bar-0.70-rc-1.tar.gz mv foish-bar-0.70-rc-1.tar.gz foish-bar_0.69-really-0.70-rc-1.orig.tar.gz tar xzf foish-bar_0.69-really-0.70-rc-1.orig.tar.gz cd foish-bar-0.70-rc-1 # The directory name in the tarball does not matter at all, you can # still use the original tarball generate debian/ etc. cu andreas
