flatpak-node-generator fails with sha1 integrity check

[kfiven]

flatpak-builder version

1.2.0

Linux distribution and version

Ubuntu 20.04

Affected flatpak-builder tool

node/flatpak-node-generator.py

flatpak-builder tool cli args

--no-requests-cache --no-xdg-layout

Source repository URL

https://raw.githubusercontent.com/cinnyapp/cinny/v2.2.0/package-lock.json

Flatpak-builder manifest URL

https://raw.githubusercontent.com/flathub/in.cinny.Cinny/master/in.cinny.Cinny.yml

Description

I have updated my dependency (@matrix-org/olm) and it has sha1 integrity hash now. Now builder seems to be failing when processing that dependency to generate node sources.

Logs: https://github.com/flathub/in.cinny.Cinny/actions/runs/3073712103/jobs/4966018497#step:12:3399

[gasinvein]

It seems like it breaks because the @matrix-org/olm package comes from gitlab registry.

@refi64 I suppose we'll need to support custom registries after all.

[ajbura]

It was working until we updated that dep https://github.com/flathub/in.cinny.Cinny/actions/runs/3040072469/jobs/4895703549#step:12:2543

[gasinvein]

I think it was working because @matrix-org/olm was pinned to an exact tarball url, not to a registry version.

[ajbura]

ah.. that could be it.

[kfiven]

It's still failing on that dependency https://github.com/kfiven/in.cinny.Cinny/actions/runs/3117155528/jobs/5055610309#step:12:886

[gasinvein]

@kfiven Didn't you forget to update your flatpak-builder-tools git submodule?

[kfiven]

https://github.com/kfiven/in.cinny.Cinny/tree/test-builder @gasinvein I did.

[gasinvein]

Hmm. My guess it's because you're downloading the package-lock.json file alone (thus the generator doesn't see the .npmrc). Try recursively cloning the whole cinnyapp/cinny-desktop git repo instead.

[kfiven]

I also tried https://github.com/kfiven/in.cinny.Cinny/actions/runs/3117132385/jobs/5055566981#step:12:49 downloading .npmrc file along with lock file but still failed. (Could it be that .npmrc has extra info in addition to registry?)

[gasinvein]

@kfiven Just clone the whole repo. It's much easier than cherry-picking files and re-creating correct structure of them. Here, you can pick changes from my fork.

[kfiven]

Cloning the whole repo worked. Thanks!