Search Criteria
Package Details: threema-desktop 1.2.46-2
Package Actions
| Git Clone URL: | https://aur.archlinux.org/threema-desktop.git (read-only, click to copy) |
|---|---|
| Package Base: | threema-desktop |
| Description: | Threema Desktop (Threema Web in Electron). |
| Upstream URL: | https://github.com/threema-ch/threema-web-electron |
| Licenses: | AGPL |
| Submitter: | dbrgn |
| Maintainer: | dbrgn |
| Last Packager: | dbrgn |
| Votes: | 17 |
| Popularity: | 0.056494 |
| First Submitted: | 2021-10-27 10:38 (UTC) |
| Last Updated: | 2024-11-22 00:17 (UTC) |
Dependencies (4)
- electron32 (electron32-binAUR)
- git (git-gitAUR, git-glAUR) (make)
- nodejs-lts-iron (make)
- npm (corepackerAUR, python-nodejs-wheelAUR) (make)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 Next › Last »
dbrgn commented on 2022-12-08 15:35 (UTC)
@solnce: I think I know what the reason is... I suspect an incompatibility with the latest NodeJS. Can you try installing nodejs-lts-gallium (which will replace nodejs) and test if the build succeeds?
solnce commented on 2022-12-08 13:45 (UTC)
@dbrgn: I noticed that, too.
Yes, plain Arch Linux, installed by myself, no derivative anywhere.
Yes, everything is up to date.
Yes, I am also on
electron-20.3.8-1, from thecommunityrepo.I am absolutely at a loss here, too.
dbrgn commented on 2022-12-08 12:26 (UTC)
solnce: The two logs you posted are different from the errors you got before. Instead of a patch applying, you get a compilation error:
Sorry, I cannot reproduce your issues. On all my computers, building works just fine. Is your system up to date (including the
electronpackage)? You're using Arch, and not some derivative distro, right? At what version is yourelectronpackage? (On my system it's 20.3.8-1)solnce commented on 2022-12-07 09:39 (UTC)
Same with
1.2.25-2.https://pastebin.com/EmBn4ntE
solnce commented on 2022-12-07 09:20 (UTC)
The latest version still won't work. Log here.
https://pastebin.com/GqwNtivp
buzo commented on 2022-11-23 20:17 (UTC) (edited on 2022-11-23 20:17 (UTC) by buzo)
Build fails here, too:
solnce commented on 2022-11-18 14:53 (UTC) (edited on 2022-11-18 14:55 (UTC) by solnce)
@sylphio Interesting, but I cannot confirm this works. Here's how I applied everything.
That produces the following output.
Truncated because this goes on forever.
In short: this does not work for at the moment.
sylphio commented on 2022-11-10 22:23 (UTC)
I faced the same error as @solnce:
I do not believe
BUILDDIRto be the cause, since it is unset in mymakepkg.conf. I found the source of this error elsewhere:0001-Remove-browser-warning.patch(applied inprepare()) removes fromwelcome.tsthe part thatpatch-user-agent.patchtries to change; therefore, the patch does not apply andbuild()fails.My quick and inelegant solution is to patch the patch.
The file
patch-user-agent-patch.patchis placed in the top directory (same as PKGBUILD) and contains the following. It simply removes the part ofpatch-user-agent.patchthat applies towelcome.ts.There is probably a more elegant way to solve this problem, but at least it let me build successfully. Perhaps
0001-Remove-browser-warning.patchcould apply the changes above topatch-user-agent.patch. Hopefully this will help someone else.Jino commented on 2022-09-27 10:15 (UTC)
@dbrgn @solnce, thank you for further investigating that issue. I can confirm that with latest update the error persists on my machine. Unfortunately, I am not experienced with the configurations in makepkg.conf. Thus, I didn't try @solnces approach. If you need me for further investigation I would try to get deeper into that topic. Otherwise I think, due to my limited understanding, my contributions wouldn't help here too much.
dbrgn commented on 2022-09-23 23:14 (UTC)
@solnce: Thanks for that hint! I can confirm that this triggers the error. I'm also not yet sure what causes the patching failure, but at least now I have a way to reproduce. I'm very busy at the moment, but will try to find time to investigate this (no guarantees though). If someone else finds the root cause, help is welcome. As a temporary workaround, don't build on ramdisk.
« First ‹ Previous 1 2 3 4 5 6 Next › Last »