Arch Linux User Repository

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

It looks like Manjaro caches some of the downloaded source files somewhere – I don't know where it does that (or if you've used another AUR helper which does it / maybe even just used makepkg directly somewhere?). Basically you have to make sure that no leftover files from a previous build (like the .patch files for example) are left so the updated files will be downloaded and used instead of the cached ones – which leads to them not passing the checksum validation here (and which would subsequently lead to a failing build later on, probably).

Librewolf fails to build on Manjaro Xfce. If anyone can help or fix this, that would be greatly appreciated.

Building librewolf...
==> Making package: librewolf 88.0-1 (Wed 28 Apr 2021 08:57:01 AM EDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found firefox-88.0.source.tar.xz
  -> Found librewolf.desktop
  -> Updating common git repo...
Fetching origin
  -> Updating settings git repo...
Fetching origin
From https://gitlab.com/librewolf-community/settings
   1b9cc88..e89e5cc  master                      -> master
 * [new branch]      override_cfg                -> override_cfg
 + 29042da...f0d0697 refs/merge-requests/11/merge -> refs/merge-requests/11/merge  (forced update)
 * [new ref]         refs/merge-requests/12/head -> refs/merge-requests/12/head
 * [new ref]         refs/merge-requests/12/merge -> refs/merge-requests/12/merge
 * [new ref]         refs/merge-requests/13/head -> refs/merge-requests/13/head
 * [new ref]         refs/merge-requests/13/merge -> refs/merge-requests/13/merge
   1b9cc88..e89e5cc  refs/merge-requests/2/merge -> refs/merge-requests/2/merge
   1b9cc88..e89e5cc  refs/merge-requests/7/merge -> refs/merge-requests/7/merge
  -> Found megabar.patch
  -> Found remove_addons.patch
  -> Found context-menu.patch
  -> Found unity-menubar.patch
  -> Found mozilla-vpn-ad.patch
==> Validating source files with sha256sums...
    firefox-88.0.source.tar.xz ... Passed
    librewolf.desktop ... Passed
    common ... Skipped
    settings ... Skipped
    megabar.patch ... FAILED
    remove_addons.patch ... FAILED
    context-menu.patch ... Passed
    unity-menubar.patch ... FAILED
    mozilla-vpn-ad.patch ... Passed
==> ERROR: One or more files did not pass the validity check!
Failed to build librewolf

So basically just having source= and an additional source_aarch64=?

I did not know this was possible – thanks for pointing that out! :)

It is not needed and that are only 2 patch files, you can use source_aarch64=() for that 2 only

Considering this is used to not download additional files that are not required for non-aarch64 builds, it seems like a reasonable approach to me.

You are using source_aarch64=() and source_x86_64=() which are not needed since you are downloading source code not pre-compiled binaries

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: More than 1 GPU detected via PCI, cannot deduce vendor (t=0.426795) [GFX1-]: More than 1 GPU detected via PCI, cannot deduce vendor
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: More than 1 GPU detected via PCI, cannot deduce vendor (t=0.426795) |[1][GFX1-]: PCI candidate 0x10de/0x1b80 (t=0.42681) [GFX1-]: PCI candidate 0x10de/0x1b80
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: More than 1 GPU detected via PCI, cannot deduce vendor (t=0.426795) |[1][GFX1-]: PCI candidate 0x10de/0x1b80 (t=0.42681) |[2][GFX1-]: PCI candidate 0x10de/0x1380 (t=0.426815) [GFX1-]: PCI candidate 0x10de/0x1380
console.warn: SearchSettings: "get: No settings file exists, new profile?" (new Error("", "(unknown module)"))

###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost

Firefox exited with code -135 during profile initialization
==> ERROR: A failure occurred in build().
    Aborting...
error making: librewolf

This package will not build on my 'dual vendor' gpu systems.

@lsf It is weird!

It worked fine when I installed Librewolf the first time. I guess I might have messed things when I installed some other package.

My TERM is xterm-256color. I am using the default fish from Manjaro installation.

ncurses exists, reinstalling it doesn't seem to fix the terminfo database

infocmp -D returns /bin/fish

Thank you very much for pointing me in the right direction, I will investigate it further.

While writing this I realized that the first time I installed Librewolf was not from the terminal, but from the add/remove software. And the first time I tried to update there was an error, but removing the package and installing from there made it work. So I am trying that again.

Right now everything seems to be building fine.

But I still need to figure out why ncurses database doesn't work if I am using yay -S Librewolf from terminal.

@JcNils that's quite an odd error ^^

Most of the terminfo files are provided by ncurses, which is required by so many packages that I'd just assume it's installed already, so my only idea would be that you've set an "unusual" $TERM for which no appropriate terminfo is installed (or $TERM is set by your terminal emulator by something unusual) and the appropriate terminfo is not installed as well (for some terminal emulators separate packages are available, eg. kitty-terminfo, termite-terminfo etc.)

That's something I'd look into first and see where that leads you :)

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