On Fri, Oct 9, 2015 at 5:40 PM, Osamu Aoki <os...@debian.org> wrote: > Hi, > > It took me a little bit of effort to understand your wish. > > 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.
$ rm example_1.0+ds1.orig.tar.gz $ uscan --repack example-1.0 $ uscan --force-download --repack example-1.0 No. This does not work because uscan stops when it finds example-1.0.tar.gz > > There is no need to option such as --force-repack as I see this > situation. Yes, I agree with you. But how to do --repack? > I think we do not need any new command. Use mk-origtargz directly if > you wish to do test as you described. Using mk-origtargz directly makes more possible errors. The intent is to test how does uscan do mk-origtargz. If the user makes a guess, then it could be wrong, and it is more work to do anyways. The uscan should make this easy to verify. > > 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 Both --no-download and --force-download I think should test repack, signature check, ... I will test when changes are ready. > > Osamu Thank you. Eric