Re: ignoring upstream debian directory while using uscan

2004-11-01 Thread Frank Küster
David Everly [EMAIL PROTECTED] schrieb: On Sat, Oct 30, 2004 at 09:40:20AM -0600, David Everly wrote: For comment, here is what I've done. First the line in debian/watch: http://ftp.indexdata.dk/pub/zebra/idzebra-(.*)\.tar\.gz \ debian ./debian/custom-uupdate Hmm...I see now that this

Re: ignoring upstream debian directory while using uscan

2004-11-01 Thread David Everly
On Mon, Nov 01, 2004 at 11:09:43AM +0100, Frank K?ster wrote: David Everly [EMAIL PROTECTED] schrieb: On Sat, Oct 30, 2004 at 09:40:20AM -0600, David Everly wrote: For comment, here is what I've done. First the line in debian/watch:

Re: ignoring upstream debian directory while using uscan

2004-11-01 Thread Frank Küster
David Everly [EMAIL PROTECTED] schrieb: On Sat, Oct 30, 2004 at 09:40:20AM -0600, David Everly wrote: For comment, here is what I've done. First the line in debian/watch: http://ftp.indexdata.dk/pub/zebra/idzebra-(.*)\.tar\.gz \ debian ./debian/custom-uupdate Hmm...I see now that this

Re: ignoring upstream debian directory while using uscan

2004-11-01 Thread David Everly
On Mon, Nov 01, 2004 at 11:09:43AM +0100, Frank K?ster wrote: David Everly [EMAIL PROTECTED] schrieb: On Sat, Oct 30, 2004 at 09:40:20AM -0600, David Everly wrote: For comment, here is what I've done. First the line in debian/watch:

Re: ignoring upstream debian directory

2004-10-30 Thread David Everly
On Fri, Oct 29, 2004 at 06:26:32AM -0600, David Everly wrote: On Thu, Oct 28, 2004 at 02:35:07PM -0400, Justin Pryzby wrote: You could have uscan call an alternate script which does the repackaging. Yes, that is one option I was considering, since I wanted to have a debian/watch file and

Re: ignoring upstream debian directory

2004-10-30 Thread David Everly
On Fri, Oct 29, 2004 at 06:26:32AM -0600, David Everly wrote: On Thu, Oct 28, 2004 at 02:35:07PM -0400, Justin Pryzby wrote: You could have uscan call an alternate script which does the repackaging. Yes, that is one option I was considering, since I wanted to have a debian/watch file and

Re: ignoring upstream debian directory while using uscan

2004-10-30 Thread David Everly
On Sat, Oct 30, 2004 at 09:40:20AM -0600, David Everly wrote: For comment, here is what I've done. First the line in debian/watch: http://ftp.indexdata.dk/pub/zebra/idzebra-(.*)\.tar\.gz \ debian ./debian/custom-uupdate Hmm...I see now that this is not possible since, even though

Re: ignoring upstream debian directory

2004-10-29 Thread David Everly
On Thu, Oct 28, 2004 at 02:35:07PM -0400, Justin Pryzby wrote: On Thu, Oct 28, 2004 at 07:21:23PM +0200, Santiago Vila wrote: On Thu, 28 Oct 2004, David Everly wrote: Is there some mechanism or alternative for using uupdate so that any upstream debian directory can be removed before

Re: ignoring upstream debian directory

2004-10-29 Thread David Everly
On Thu, Oct 28, 2004 at 02:35:07PM -0400, Justin Pryzby wrote: On Thu, Oct 28, 2004 at 07:21:23PM +0200, Santiago Vila wrote: On Thu, 28 Oct 2004, David Everly wrote: Is there some mechanism or alternative for using uupdate so that any upstream debian directory can be removed before

Re: ignoring upstream debian directory

2004-10-28 Thread Santiago Vila
On Thu, 28 Oct 2004, David Everly wrote: Is there some mechanism or alternative for using uupdate so that any upstream debian directory can be removed before patching? Don't know about uupdate, but you are allowed to repackage the .orig.tar.gz to exclude the upstream debian directory if it

Re: ignoring upstream debian directory

2004-10-28 Thread Henrique de Moraes Holschuh
On Thu, 28 Oct 2004, David Everly wrote: Is there some mechanism or alternative for using uupdate so that any upstream debian directory can be removed before patching? Repack the upstream tarball sans the bogus debian/ dir, or use one of the unpack-tarball-on-build-tree/-and-patch packaging

Re: ignoring upstream debian directory

2004-10-28 Thread Justin Pryzby
On Thu, Oct 28, 2004 at 07:21:23PM +0200, Santiago Vila wrote: On Thu, 28 Oct 2004, David Everly wrote: Is there some mechanism or alternative for using uupdate so that any upstream debian directory can be removed before patching? Don't know about uupdate, but you are allowed to

Re: ignoring upstream debian directory

2004-10-28 Thread Frank Küster
Santiago Vila [EMAIL PROTECTED] schrieb: On Thu, 28 Oct 2004, David Everly wrote: Is there some mechanism or alternative for using uupdate so that any upstream debian directory can be removed before patching? Don't know about uupdate, but you are allowed to repackage the .orig.tar.gz to

Re: ignoring upstream debian directory

2004-10-28 Thread Henrique de Moraes Holschuh
On Thu, 28 Oct 2004, Frank Küster wrote: Henrique de Moraes Holschuh [EMAIL PROTECTED] schrieb: Repack the upstream tarball sans the bogus debian/ dir, or use one of the unpack-tarball-on-build-tree/-and-patch packaging styles... Why not just replace the upstream debian dir with your

Re: ignoring upstream debian directory

2004-10-28 Thread Henrique de Moraes Holschuh
On Thu, 28 Oct 2004, Frank Küster wrote: I see no reason for repackaging in this case. It is much better to just delete the upstream debian directory in the unpacked sources and copy As I said, diff/patch cannot delete files in a debian package. -- One disk to rule them all, One disk to

Re: ignoring upstream debian directory

2004-10-28 Thread martin f krafft
also sprach Henrique de Moraes Holschuh [EMAIL PROTECTED] [2004.10.28.2218 +0200]: Patch cannot delete files. It can: -E or --remove-empty-files Remove output files that are empty after the patches have been applied. Normally this option is unnecessary,

Re: ignoring upstream debian directory

2004-10-28 Thread Mike Hommey
On Thu, Oct 28, 2004 at 10:56:01PM +0200, martin f krafft wrote: also sprach Henrique de Moraes Holschuh [EMAIL PROTECTED] [2004.10.28.2218 +0200]: Patch cannot delete files. It can: The other problem is that if upstream adds a *new* file in the debian/ directory, it won't be deleted by

ignoring upstream debian directory

2004-10-28 Thread David Everly
Hi, Is there some mechanism or alternative for using uupdate so that any upstream debian directory can be removed before patching? Thanks, Dave. -- Encrypted Mail Preferred: Key ID: 8527B9AF Key Fingerprint: E1B6 40B6 B73F 695E 0D3B 644E 6427 DD74 8527 B9AF Information:

Re: ignoring upstream debian directory

2004-10-28 Thread Santiago Vila
On Thu, 28 Oct 2004, David Everly wrote: Is there some mechanism or alternative for using uupdate so that any upstream debian directory can be removed before patching? Don't know about uupdate, but you are allowed to repackage the .orig.tar.gz to exclude the upstream debian directory if it

Re: ignoring upstream debian directory

2004-10-28 Thread Henrique de Moraes Holschuh
On Thu, 28 Oct 2004, David Everly wrote: Is there some mechanism or alternative for using uupdate so that any upstream debian directory can be removed before patching? Repack the upstream tarball sans the bogus debian/ dir, or use one of the unpack-tarball-on-build-tree/-and-patch packaging

Re: ignoring upstream debian directory

2004-10-28 Thread Justin Pryzby
On Thu, Oct 28, 2004 at 07:21:23PM +0200, Santiago Vila wrote: On Thu, 28 Oct 2004, David Everly wrote: Is there some mechanism or alternative for using uupdate so that any upstream debian directory can be removed before patching? Don't know about uupdate, but you are allowed to

Re: ignoring upstream debian directory

2004-10-28 Thread Frank Küster
Henrique de Moraes Holschuh [EMAIL PROTECTED] schrieb: On Thu, 28 Oct 2004, David Everly wrote: Is there some mechanism or alternative for using uupdate so that any upstream debian directory can be removed before patching? Repack the upstream tarball sans the bogus debian/ dir, or use one of

Re: ignoring upstream debian directory

2004-10-28 Thread Frank Küster
Santiago Vila [EMAIL PROTECTED] schrieb: On Thu, 28 Oct 2004, David Everly wrote: Is there some mechanism or alternative for using uupdate so that any upstream debian directory can be removed before patching? Don't know about uupdate, but you are allowed to repackage the .orig.tar.gz to

Re: ignoring upstream debian directory

2004-10-28 Thread Henrique de Moraes Holschuh
On Thu, 28 Oct 2004, Frank Küster wrote: Henrique de Moraes Holschuh [EMAIL PROTECTED] schrieb: Repack the upstream tarball sans the bogus debian/ dir, or use one of the unpack-tarball-on-build-tree/-and-patch packaging styles... Why not just replace the upstream debian dir with your

Re: ignoring upstream debian directory

2004-10-28 Thread Henrique de Moraes Holschuh
On Thu, 28 Oct 2004, Frank Küster wrote: I see no reason for repackaging in this case. It is much better to just delete the upstream debian directory in the unpacked sources and copy As I said, diff/patch cannot delete files in a debian package. -- One disk to rule them all, One disk to

Re: ignoring upstream debian directory

2004-10-28 Thread martin f krafft
also sprach Henrique de Moraes Holschuh [EMAIL PROTECTED] [2004.10.28.2218 +0200]: Patch cannot delete files. It can: -E or --remove-empty-files Remove output files that are empty after the patches have been applied. Normally this option is unnecessary,

Re: ignoring upstream debian directory

2004-10-28 Thread Mike Hommey
On Thu, Oct 28, 2004 at 10:56:01PM +0200, martin f krafft wrote: also sprach Henrique de Moraes Holschuh [EMAIL PROTECTED] [2004.10.28.2218 +0200]: Patch cannot delete files. It can: The other problem is that if upstream adds a *new* file in the debian/ directory, it won't be deleted by