-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[node] flatpak-node-generator.py failed to deal with deps with direct git reference #182
Comments
Some interesting logs:
|
So after further investigation, a more elaborated reason is, the git-hosted module has a |
First you should use git source instead of tar.gz, as it has submodules. You may need add env |
If I
Then it will
|
No I'm not. And sorry I pasted the wrong log. Edited |
Seems no way to fix, you may need add source manually. |
That, however, is probably a bug of flatpak-builder. |
Maybe not this, as directly using standardnote/web's git source get the same error. |
That's interesting... It doesn't even clone the vendor/extensions/extensions-manager in vendor/extensions/extensions-manager! |
@catsout Thanks for pointing me to the right direction. standardnotes/app#516 fixes the corrupted submodules for this case. On the other hand, looking forward to your PR being merged ;) |
So, there is another case of git-based dependencies not covered.
|
I found that the Maybe it can't be simply plugged-in by adding one item in GIT_SCHEMES? |
@proletarius101 Well, try adding entry |
It doesn't just work, but so close. What it does// package-lock.json
// From
"duo_web_sdk": {
"version": "git+ssh://[email protected]/duosecurity/duo_web_sdk.git#410a9186cc34663c4913b17d6528067cd3331f1d",
"from": "duo_web_sdk@git+https://github.com/duosecurity/duo_web_sdk.git"
},
// To
"duo_web_sdk": {
"version": "git+file:/******/flatpak-node/git-packages/duo_web_sdk-410a9186cc34663c4913b17d6528067cd3331f1d#410a9186cc34663c4913b17d6528067cd3331f1d",
"from": "git+file:/******/flatpak-node/git-packages/duo_web_sdk-410a9186cc34663c4913b17d6528067cd3331f1d#410a9186cc34663c4913b17d6528067cd3331f1d"
},
What it doesn'tIt should have changed this as well // package.json
"duo_web_sdk": "git+https://github.com/duosecurity/duo_web_sdk.git", |
I'm hitting this same issue attempting to package Element from source, which uses a couple of direct Git references.
|
@jwillikers Well, this particular package isn't a git one, so I doubt it's the same issue. |
It's defined in the package.json using a direct Git reference: "matrix-react-sdk": "github:matrix-org/matrix-react-sdk#develop", However, it appears that matrix-web doesn't use Git references in their tagged releases, so hopefully I can sidestep the problem for now. |
@jwillikers So where did the error you posted came from, from a tagged release or from main branch tip? |
@gasinvein The error I posted above is from the tip of the default branch, |
@jwillikers Why does it point to registry.yarnpkg.com, then? There is only one |
@gasinvein Well, from what I can tell, the |
@jwillikers Can you please link to the manifest you're trying to build? It's hard to tell what's wrong without knowing what's going on. |
Did you miss the --xdg-layout flag? |
Nope, I just regenerated the file just now using
@gasinvein I'll go ahead an open a draft PR and link it here. Using the |
From what I can tell, the flatpak-builder-tools node tooling supports a subset of the ways npm can resolve a dependency. Looking at a recent test case, the following should work: {
"name": "@flatpak-node-generator-tests/minimal-git",
"version": "1.0.0",
"dependencies": {
"nop": "https://[email protected]/supershabam/nop.git"
}
} |
What is a dependency with direct git reference?
https://github.com/standardnotes/desktop/blob/3fbb58adf16a564d6773aae6cce273325f9eeba8/package.json#L12
What did I do?
The results
A complete log could be found at https://flathub.org/builds/#/builders/35/builds/4478
What I can suggest
crypto-web
is a dependency ofgithub:standardnotes/decrypt#master
. I think it's failed to be included in the cache.Related PR
flathub/flathub#2086
The text was updated successfully, but these errors were encountered: