Control: tags -1 pending
On Tue, Dec 22, 2020 at 1:20 pm, Akshay S Dinesh <aks...@learnlearn.in>
wrote:
gbp:error: upstream/1.22.10+_cs18.39.16 is not a valid treeish
indeed your fork only has 33 tags, whereas js-team/node-yarnpkg has
37.
Please pull those tags and push them to your fork, then force
restart the CI pipeline.
This would help us to see if your proposed fix works.
Pushing tags indeed helped extract sources. But build fails due to
incompatibilities with upstream files
As to upgrading tar-fs, it is possible that some other dependency we
updated here and there requires it.
Upstream are currently using 1.16.3:
https://github.com/yarnpkg/yarn/blob/master/yarn.lock#L7137
whereas we were already using version 2
If we want to upgrade tar-fs we need to upgrade its sources and then
import them in upstream and master branches:
https://wiki.debian.org/Javascript/GroupSourcesTutorial
I think Praveen locked the dependency on tar-fs to version 1.x in
https://salsa.debian.org/js-team/node-yarnpkg/-/commit/8f44f7d238f4330b89d3b62c2cc369bb909459a6
I'm unsure if that's because upstream yarn mentions 1.x tar-fs as
dependency or because there are other dependencies to 1.x tar-fs.
The API of tar-fs doesn't change between 1.x and 2.x, but the
dependencies do. And the dependencies we have in debian make it such
that 1.x doesn't work.
I tried following GroupSourcesTutorial and gbp manual. It is becoming
very confusing for me with many version numbers and tags floating
around. So I'll have to leave this here for possibly Praveen to pick
up.
To update a component, you have to update debian/watch and run uscan,
then gbp import orig --pristine-tar.
-
https://registry.npmjs.org/tar-fs/-/tar-fs-(1(?:.[\d\.]+)?)@ARCHIVE_EXT@
checksum
+
https://registry.npmjs.org/tar-fs/-/tar-fs-(2(?:.[\d\.]+)?)@ARCHIVE_EXT@
checksum
But it seems ctype=nodejs is not working as expected (it is supposed to
download versions matching with package.json but that does not seem to
be working).
I can install packages now. Uploading the fixed version.