Package Details: librewolf 127.0-1

Git Clone URL: (read-only, click to copy)
Package Base: librewolf
Description: Community-maintained fork of Firefox, focused on privacy, security and freedom.
Upstream URL:
Keywords: browser web
Licenses: GPL, MPL, LGPL
Submitter: lsf
Maintainer: lsf
Last Packager: lsf
Votes: 125
Popularity: 3.81
First Submitted: 2019-06-14 18:41 (UTC)
Last Updated: 2024-06-18 06:44 (UTC)

Dependencies (58)

Sources (3)

Latest Comments

1 2 3 4 5 6 .. 26 Next › Last »

aljustiet commented on 2024-06-21 09:27 (UTC) (edited on 2024-06-21 09:28 (UTC) by aljustiet)

Why am I receiving this error?

Cusith commented on 2024-06-19 16:38 (UTC)

With regards to rust issues the official thunderbird package switched to rustup with this in the PKGBUILD:

# packed_simd no longer builds with 1.78.0
rustup toolchain update --profile minimal 1.77.2
rustup default 1.77.2

ccorn commented on 2024-05-14 20:17 (UTC)

Building in a clean chroot, I have encountered a rust-simd issue (again, but with a different error message). My workaround (again): ac_add_options --disable-rust-simd.

blufinney commented on 2024-05-07 18:54 (UTC)

Is this building for others in a clean chroot as of Archlinux fully updated today?

It's likely a newb issue, but in the past the newb issue was that I didn't fully update etc.

What about this error, does this affect the build?

Cloning into 'librewolf'...
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint:   git config --global init.defaultBranch <name>
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:   git branch -m <name>

Integral commented on 2024-04-29 20:58 (UTC)

"export MOZ_APP_REMOTINGNAME=${_pkgname}" should be changed to "export MOZ_APP_REMOTINGNAME=${pkgname}", otherwise when running under Wayland it will fallback to the default Wayland icon.

xiota commented on 2024-04-29 19:55 (UTC)

@alexmurkoff It's okay. Everyone starts somewhere. Have fun building more packages.

alexmurkoff commented on 2024-04-29 18:23 (UTC)

@xiota Yeah, that worked! Thanks for helping me with this stuff, I'm kinda new here (if you couldn't tell) Sorry for misunderstanding though, I should've done my research first.

xiota commented on 2024-04-29 16:42 (UTC) (edited on 2024-04-29 16:46 (UTC) by xiota)

$ sudo pacman -S base-devel

$ sudo \rm -rf librewolf

$ git clone

$ cd librewolf

$ extra-x86_64-build

alexmurkoff commented on 2024-04-29 15:29 (UTC)

@Bitals Huh.. Sorry, I guess that was just a misconception of mine. I'm not going to go into semantics, I just kind of misunderstood the purpose of yay, which i apologize for.

@xiota I've seen the wiki page you've linked, what exact method are you implying i should be able to build librewolf with? I tried the Convenience way that is mentioned on the wiki, but it would appear that it can't find the .install file, which shouldn't be the case. I tried as a regular user, as sudo and as root, all yield the result below. The full log:

# pkgctl build
==> Updating pacman database cache
:: Synchronizing package databases...
 core downloading...
 extra downloading...
 multilib downloading...
==> Building librewolf
==> WARNING: invalid architecture, not building for: aarch64
  ->   repo: extra
  ->   arch: x86_64
  -> worker: alex-0
==> Building librewolf for [extra] (x86_64)
:: Synchronizing package databases...
 core downloading...
 extra downloading...
:: Starting full system upgrade...
 there is nothing to do
==> Building in chroot for [extra] (x86_64)...
==> Synchronizing chroot copy [/var/lib/archbuild/extra-x86_64/root] -> [alex-0]...done
==> ERROR: install file (librewolf.install) does not exist or is not a regular file.
==> ERROR: Could not download sources.

Bitals commented on 2024-04-29 12:13 (UTC)

@alexmurkoff building in a clean chroot does not add any new libraries to your system the way e.g. flatpak does. Just read the linked article to understand it.

Also, yay is not a package manager, it's an AUR helper. And AUR is not a package repository, it's a build script repository. Helpers work in most cases most of the time, but sometimes you just need manual intervention. That's just how it is by definition.