Bug#801165: devscripts: [uscan] Option --force-repack helpful for testing Files-Excluded and repacksuffix

[Osamu Aoki]

Hi,

It took me a little bit of effort to understand your wish.

On Tue, Oct 06, 2015 at 08:41:03PM -0700, Eric Shattow wrote:
> Severity: wishlist

> uscan --force-repack would be helpful for testing Files-Excluded and
> repacksuffix.

If we invoke uscan without using --no-symlink, uscan always call
mk-origtargz with --symlink option.  If mk-origtargz finds files
matching Files-Excluded, mk-origtargz behaves as --copy (See its
manlage).

If the repack without having a matiching Files-Excluded is objective to
see if repacksuffix works or not, just use --repack as the argument of
uscan, it passes it to mk-origtarg.

There is no need to option such as --force-repack as I see this
situation.
 
> The way to test an repacksuffix=ds1 containing debian/watch for example-1.0/
> is:
> 
> rm example*tar.gz
> uscan --force-download example-1.0
> 
> This gives us example-1.0.tar.gz and example_1.0+ds1.orig.tar.gz
> 
> rm example_1.0+ds1.orig.tar.gz
> uscan --force-download example-1.0
> 
> What happens now that example_1.0+ds1.orig.tar.gz is missing?

Since you still have example-1.0.tar.gz, uscan stop there and do
nothing
 
> We have to delete example-1.0.tar.gz or there's no easy way to force the
> repack. This is not good if the example-1.0.tar.gz is large or we want to test
> this function offline.
 ^^^^^^^^^^^^^^^^^^^^^^

I see.  

I think we do not need any new command.  Use mk-origtargz directly if
you wish to do test as you described.

But I also understand, the current state of uscan is not optimal.
--no-download option should enable your wish to test repack, signature
check, ...  This is what I am working on ... #740366 #747412

Osamu