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
Update to 2.3.3 #17
Update to 2.3.3 #17
Conversation
Started test build 56360 |
Build 56360 failed |
bot, build net.cozic.joplin_desktop |
Queued test build for net.cozic.joplin_desktop. |
Started test build 56388 |
Build 56388 was cancelled |
Started test build 56390 |
@nedrichards |
Build 56390 failed |
Started test build 56416 |
@barthalion |
Build 56416 failed |
Try adding |
Started test build 56533 |
Build 56533 failed |
This reverts commit 0056985.
Started test build 56536 |
Build 56536 was cancelled |
Started test build 56538 |
Build 56538 failed |
Post the
I don't know if there's a way to disable the Another reason why upstream should consider switching to tarballs instead of git is this issue. /ping @laurent22 |
Started test build 56540 |
Started test build 56541 |
Build 56540 was cancelled |
Build 56541 was cancelled |
@tinywrkb, I'm not familiar with these problems. What's causing an issue in Joplin repo? |
npm find a package with git url: |
Started test build 56542 |
Build 56542 failed |
|
Started test build 56545 |
Build 56545 failed |
@laurent22 as @catsout pointed out, there are some difficulties of building in offline mode when there are node modules with git sources. To work around them, some changes are needed to be made to the Flatpak packaging helpers, |
Started test build 56598 |
Seems like it's the same issue as laurent22/joplin#4478 |
Build 56598 successful
|
No description provided.