Package Details: librewolf 1:137.0.2_1-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: 170
Popularity: 12.18
First Submitted: 2019-06-14 18:41 (UTC)
Last Updated: 2025-04-16 17:19 (UTC)

Dependencies (62)

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 .. 23 24 25 26 27 28 29 30 31 32 33 Next › Last »

JcNils commented on 2021-04-03 19:13 (UTC)

Hi, I am on Manjaro, and when I try to update or install it I get an error: could not find terminfo database.

env | grep TERM shows that the variable is there.

I wonder what is missing.

Full error:

Error running mach:

    ['build']

The error occurred in code that was called by the mach command. This is either
a bug in the called code itself or in the way that mach is calling it.
You can invoke |./mach busted| to check if this issue is already on file. If it
isn't, please use |./mach busted file build| to report it. If |./mach busted| is
misbehaving, you can also inspect the dependencies of bug 1543241.

If filing a bug, please include the full output of mach, including this error
message.

The details of the failure are as follows:

_curses.error: setupterm: could not find terminfo database

  File "/home/pc/.cache/yay/librewolf/src/firefox-87.0/python/mozbuild/mozbuild/build_commands.py", line 146, in build
    return driver.build(
  File "/home/pc/.cache/yay/librewolf/src/firefox-87.0/python/mozbuild/mozbuild/controller/building.py", line 1083, in build
    footer = BuildProgressFooter(self.log_manager.terminal, monitor)
  File "/home/pc/.cache/yay/librewolf/src/firefox-87.0/python/mozbuild/mozbuild/controller/building.py", line 651, in __init__
    Footer.__init__(self, terminal)
  File "/home/pc/.cache/yay/librewolf/src/firefox-87.0/python/mozterm/mozterm/widgets.py", line 12, in __init__
    self.term = terminal or Terminal()
  File "/home/pc/.cache/yay/librewolf/src/firefox-87.0/python/mozterm/mozterm/terminal.py", line 53, in Terminal
    return blessings.Terminal(**kwargs)
  File "/home/pc/.cache/yay/librewolf/src/firefox-87.0/third_party/python/blessings/blessings/__init__.py", line 97, in __init__
    setupterm(kind or environ.get('TERM', 'unknown'),
==> ERROR: A failure occurred in build().
    Aborting...
checking dependencies...

Packages (1) lld-11.1.0-1

0000000000 commented on 2021-03-30 19:27 (UTC)

should I just throw puter out the window?

https://imgur.com/4jcmzki

what do ty

lsf commented on 2021-03-27 00:27 (UTC) (edited on 2021-03-27 00:28 (UTC) by lsf)

np :)

btw: I've just discovered firedragon yesterday – looks great, and it's cool to see librewolf being adapted and customized! :)

dr460nf1r3 commented on 2021-03-27 00:00 (UTC)

You are totally right, it was an incorrectly cached patch. Sorry for the inconvenience.

lsf commented on 2021-03-26 18:10 (UTC)

@dr460nf1r3 can't reproduce that. If the checksums already fail, that indicates that your build system might use some cached files somewhere? (Only the unity-menubar.patch has changed (which isn't applied by default) but even that one applies cleanly for me when doing a fresh checkout of https://aur.archlinux.org/librewolf and running makepkg with the relevant line uncommented.)

Considering your logs show

Fetching origin
  -> Found megabar.patch
  -> Found remove_addons.patch
  -> Found context-menu.patch
  -> Found unity-menubar.patch
  -> Found mozilla-vpn-ad.patch

(and not downloading them) that might indeed be a possibility (as in: they're either cached somewhere or provided in a step that's not part of the logs, and something's going wrong at that point).

dr460nf1r3 commented on 2021-03-26 17:18 (UTC)

The PKGBUILD needs fixing, checksums dont match & a patch is failing to apply. Logs available here

haven commented on 2021-03-18 21:51 (UTC)

@lsf yes, thanks, did that, had to rebuild again, but at least I'm ready for the next time :)

lsf commented on 2021-03-18 18:38 (UTC)

You probably just need to remove the unity-menubar.patch – I'd assume that file is just left over from a previous build and has changed in the meantime, so the checksums don't match anymore. It will get re-downloaded when you run makepkg again.

Considering rebuilding from scratch: You probably won't be able to avoid it. It might be possible to somehow get it to re-use some parts of the previous build… but I doubt it's feasible / doable for a production build like this.

An alternative would be to just use the prebuilt package instead (https://aur.archlinux.org/packages/librewolf-bin/) if you don't need to build from source.

haven commented on 2021-03-18 18:27 (UTC)

I was trying to upgrade to 86.0.1-1 from 86, but I'm getting next error. I'm using Manjaro. I don't want to rebuild from scratch, since it takes at least an hour for me. I'm new to Linux, please advise.

==> Validating source_x86_64 files with sha256sums... firefox-86.0.1.source.tar.xz ... Passed librewolf.desktop ... Passed common ... Skipped settings ... Skipped megabar.patch ... Passed remove_addons.patch ... Passed context-menu.patch ... Passed unity-menubar.patch ... FAILED ==> ERROR: One or more files did not pass the validity check! Failed to build librewolf

lsf commented on 2021-03-12 13:53 (UTC)

Do you mean the patch for the global menubar?

If so, that patch is still included, but not automatically applied (as it caused issues on quite a few configurations). Those might not be an issue anymore (seems like they only occurred due to another unrelated issue that's fixed by now), but that's not tested yet. It can be applied by just uncommenting the line at https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=librewolf#n153.

« First ‹ Previous 1 .. 23 24 25 26 27 28 29 30 31 32 33 Next › Last »