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

[Pirate Praveen]

On Wed, Oct 9, 2019 at 07:08, Nicolas Mora <nicolas at babelouest.org> 
wrote:
> Le 19-10-09 à 02 h 47, Pirate Praveen a écrit :
>> 
>> 
>>  Well, if you had not pushed to js-team, squashing makes sense as it 
>> require force push. It is not recommended to force push to team repo 
>> after it is published. In this case since we have not uploaded it, 
>> you can squash and force push if you like. But never force push once 
>> a package is uploaded.
>> 
> I can't push-force, gitlab won't allow me to:
> 
> remote: GitLab: You are not allowed to force push code to a protected
> branch on this project.
> To salsa.debian.org:js-team/node-i18next.git
> 

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.

> 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.

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-javascript-devel/attachments/20191009/a256d09a/attachment.html>