[Pkg-javascript-devel] Bug#934456: Bug#934456: further automation ideas for add-node-component

Xavier yadd at debian.org
Sun Aug 11 11:00:56 BST 2019


Le 11/08/2019 à 10:52, Pirate Praveen a écrit :
> package: pkg-js-tools
> 
> version: 0.8.14
> 
> severity: wishlist
> 
> 
> I hope we can add -u (uscan), -s (source), -i (import) options for uscan
> -dd, dpkg-source -b . and (quilt pop -a && rm -rf .pc) gbp import-dsc
> --pristine-tar + pristine-tar commit
> 
> -s should assume -d, and -i should assume -s.

Then:
 * -d (download) launches uscan -dd
 * -s (source) launches uscan + dpkg-source -b . and (quilt pop -a &&
      rm -rf .pc)
 * -i (import) uscan + dpkg-source + git tag -d upstream/<version>
      if exists + gbp import-dsc ...
 OR (I prefer this way):
 * -d launches uscan
 * -i launches uscan + git tag -d upstream/<version> if exists +
      gbp import-orig ../newtar.org.tar.gz

Also:
 * -f launches also a "git push origin -d upstream/<version>" to clean
      upstream repo if needed (fix upstream tag)

dpkg-source does not read debian/gbp.conf, then some unwanted files may
be imported (upstream .gitignore,...). Also "dpkg-source + gbp
import-dsc" needs to clean repo, a "git reset --hard" will not work for
new files, then if repo is not clean, gbp will fail

Agree ?



More information about the Pkg-javascript-devel mailing list