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

[Xavier]

Le 11/08/2019 à 16:15, Xavier a écrit :
> Le 11/08/2019 à 12:08, Pirate Praveen a écrit :
>> On 11/08/19 3:30 pm, Xavier wrote:
>>> 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 ?
>>>
>>
>> In principle, but in practice gbp import-orig does not work with
>> multiple tarballs. See #934200 gbp import-dsc always worked.
> 
> Done. Could you test add-node-component from salsa repository ? If it's
> OK for you, I will release with auto_build feature in unstable

Fix: I'll release it without auto_build feature (not useful for now)