| 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: | 16.78 |
| First Submitted: | 2019-06-14 18:41 (UTC) |
| Last Updated: | 2025-04-06 11:35 (UTC) |
Since the build takes such a long time you might consider changing mkdir mozbuild in the prepare function to mkdir -p mozbuild which would not give a error if you are attempting to rebuild on error or something.
Another solution would be to include the mkdir in a if block like:
if [[ ! -d mozbuild ]]; then mkdir mozbuild fi
just an idea :-)
Is there a way to save the geometry on exit like firefox?
@lsf: doing a clean build fixed it for me, I had the same problem on a previous version so just assumed the shasums weren't updated.
@peryngveohlin666: works on my end. you might want to check if you still have some files from a previous build lying around (in the folder you're running makepkg, or in the caches of yay/paru/etc.).
==> Validating source_x86_64 files with sha256sums... firefox-86.0.source.tar.xz ... Passed librewolf.desktop ... Passed common ... Skipped settings ... Skipped megabar.patch ... FAILED remove_addons.patch ... Passed context-menu.patch ... Passed unity-menubar.patch ... Passed ==> ERROR: One or more files did not pass the validity check!
Thank you, it works.
It was this glibc update.
Hello,
I have 2.32-5 version of glibc
I have no musl installed (and didn't know its existence or what it is). I can install it.
Here's the output of the librewolf-bin error:
$ librewolf /usr/lib/librewolf/librewolf: /usr/lib/libc.so.6: version `GLIBC_2.33' not found (required by /usr/lib/librewolf/librewolf)
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).