[Pkg-javascript-devel] build node-i18next with webpack instead or rollup?

[Nicolas Mora]

Le 2019-10-09 09:36, Pirate Praveen a écrit :
> 
> I guess one of the gitlab acl bugs/features as you have maintainer
> access there, if you wish you can make master branch as unprotected
> and force push. But I think lets leave it as it is.
> 
I tried to find out how to change it but so far no luck, isthere's a 
level higher than 'maintainer' but lower than 'admin' in the gltlab 
group js-team?

>> For the next time, must the git commits be all squashed for an
>> upload in the js team?
> 
> That would be nice, we will have clean git histories.
> 
Will do then, thanks

> I'm trying to build your package, but it seems your pristine-tar
> branch is not correct.
> 
> $ origtargz W: Unable to locate package node-i18next
> 
> I had to do the following steps,
> 
> $ pristine-tar checkout ../node-i18next-17.0.18.tar.gz pristine-tar:
> successfully generated ../node-i18next-17.0.18.tar.gz $ mv
> ../node-i18next-17.0.18.tar.gz ../node-i18next_17.0.18.orig.tar.gz
> 
> Check the file names, you imported the wong tarball I think. Please
> use pristine-tar commit to add correct orig.tar

I pushed changes in the pristine-tar branch. Then I tried to build from 
a fresh clone with no luck so far:

$ gbp clone git at salsa.debian.org:js-team/node-i18next.git
$ gbp buildpackage --git-builder=sbuild -A
gbp:error: upstream/17.0.18 is not a valid treeish

I have to run pristine-tar checkout first, is it normal?