Package Details: librewolf 1:137.0.0_3-1

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: 15.79
First Submitted: 2019-06-14 18:41 (UTC)
Last Updated: 2025-04-06 11:35 (UTC)

Sources (3)

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).

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 33 Next › Last »

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:
hint:   git config --global init.defaultBranch <name>
hint:
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint:
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.

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 https://aur.archlinux.org/librewolf.git

$ 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.

xiota commented on 2024-04-29 09:03 (UTC) (edited on 2024-04-29 09:06 (UTC) by xiota)

@lsf Firefox-based browsers need python-setuptools added to makedeps because of Python 3.12 upgrade. (pkgrel does not need to be bumped because there is no need to rebuild.)

@alexmurkoff This package has been successfully built in a clean chroot. If there are new errors when building in a clean chroot, packaging changes are more likely to be needed. Otherwise, the problem may be caused by AUR helper or system config.

The install file is not missing.

alexmurkoff commented on 2024-04-29 08:43 (UTC)

no, but why would i even use yay in this case if i still would have to manually do everything? i'm sorry if i sound dumb or something, but i thought the whole point of having package managers was to minimize the bloat on the system by having a single version of the same library for every package that depends on it. if i didn't care about that i would just download an appimage or a flatpak or something

however, i did try to build in a clean chroot. wiki mentions using pkgctl build, but it didn't work out for me (error: install file (librewolf.install) does not exist or is not a regular file.). this leads me to believe that i'd have to do this the old-fashioned, manual way. what's the point of having an AUR package then? i could just git clone the repo in that case.

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 33 Next › Last »