@lahwaacz
Hm, didn't have that issue, compiling in a "clean" docker environment.
I've just updated the package to 79.0-1 – if you still experience the issue with that one, I'll try to look into it :)
Git Clone URL: | https://aur.archlinux.org/librewolf.git (read-only, click to copy) |
---|---|
Package Base: | librewolf |
Description: | Community-maintained fork of Firefox, focused on privacy, security and freedom. |
Upstream URL: | https://librewolf.net/ |
Keywords: | browser web |
Licenses: | MPL-2.0 |
Submitter: | lsf |
Maintainer: | lsf |
Last Packager: | lsf |
Votes: | 172 |
Popularity: | 18.01 |
First Submitted: | 2019-06-14 18:41 (UTC) |
Last Updated: | 2025-03-27 22:42 (UTC) |
@lahwaacz
Hm, didn't have that issue, compiling in a "clean" docker environment.
I've just updated the package to 79.0-1 – if you still experience the issue with that one, I'll try to look into it :)
I got a couple of errors when building in a clean chroot:
error: options `-C embed-bitcode=no` and `-C lto` are incompatible
error: could not compile `gkrust`.
To learn more, run the command again with --verbose.
make[4]: *** [/build/librewolf/src/firefox-78.0.2/config/makefiles/rust.mk:294: force-cargo-library-build] Error 101
make[3]: *** [/build/librewolf/src/firefox-78.0.2/config/recurse.mk:74: toolkit/library/rust/target] Error 2
make[2]: *** [/build/librewolf/src/firefox-78.0.2/config/recurse.mk:34: compile] Error 2
make[1]: *** [/build/librewolf/src/firefox-78.0.2/config/rules.mk:390: default] Error 2
make: *** [client.mk:125: build] Error 2
LibreWolf.gitlab.io 404's, I think the addres is librewolf-community.gitlab.io
remote: Enumerating objects: 12, done.
remote: Counting objects: 100% (12/12), done.
remote: Compressing objects: 100% (8/8), done.
remote: Total 12 (delta 2), reused 0 (delta 0)
Unpacking objects: 100% (12/12), done.
==> Validating source files with sha256sums...
firefox-69.0.2.source.tar.xz ... Passed
librewolf.desktop ... FAILED
librewolf.cfg.patch ... Passed
no-relinking.patch ... Passed
common ... Skipped
settings ... Skipped
==> ERROR: One or more files did not pass the validity check!
Pinned Comments
lsf commented on 2025-01-01 21:28 (UTC)
Please refrain from abusing the flagging of a package as out of date for build issues. This is not what it is supposed to be used for.
I automatically get notified of comments to this package. I do not need to be notified of whatever build problems occur (whether they are an individual's problems or the actual package's problems) twice, and not via flagging it out of date.
Issues with this package can also be reported at https://codeberg.org/librewolf/issues/issues (as it is also maintained there, at https://codeberg.org/librewolf/arch, too).