Package Details: librewolf 133.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: GPL, MPL, LGPL
Submitter: lsf
Maintainer: lsf
Last Packager: lsf
Votes: 144
Popularity: 4.35
First Submitted: 2019-06-14 18:41 (UTC)
Last Updated: 2024-12-15 09:44 (UTC)

Dependencies (58)

Sources (3)

Latest Comments

« First ‹ Previous 1 .. 17 18 19 20 21 22 23 24 25 26 27 28 Next › Last »

je-vv commented on 2021-05-14 01:03 (UTC)

Thanks !

lsf commented on 2021-05-14 00:55 (UTC)

Understood – I'll keep 'em ;)

(I honestly just didn't assume they were needed anymore in the future, but you make a good case – and as long as people are aware of the need to look out for .pacnew files, I see no harm in it :)

je-vv commented on 2021-05-14 00:25 (UTC)

Hi @lsf, pelase do not remove:

backup=('usr/lib/librewolf/librewolf.cfg'
        'usr/lib/librewolf/distribution/policies.json')

See, it's not the same when you just want overwrite some values, which is what including ~/.librewolf/librewolf.overrides.cfg at the end of /usr/lib/librewolf/librewolf.cfg is meant for, than for commenting out some configs from /usr/lib/librewolf/librewolf.cfg, to get the FF default behavior instead.

For example to get safe browsing back, as it works on FF, the best is just comment out the librewolf configs, instead of specifying URLs, and several string values and the like.

I hope you don't remove those backup lines ever, :)

Thanks a lot !

lsf commented on 2021-04-28 13:48 (UTC)

Hm.. good point.

Never had this problem (with this package, at least), so I'd just naively assumed AUR helpers (like paru, in my case) checked for changes to checksums in the .SRCINFO and re-downloaded files accordingly.

To make all this less error prone, it would make sense to follow your hint, I guess, and do it the 

"${pkgver}-${pkgrel}_patch_filename.patch::https://gitlab.com/whatever/patch_filename.patch"
# …
  patch -p1 -i ../${pkgver}-${pkgrel}_patch_filename.patch

way in the next release – thanks!

lahwaacz commented on 2021-04-28 13:38 (UTC)

@lsf Caching sources is a makepkg feature. The names of the patches in this PKGBUILD are not unique and do not even depend on $pkgver, which causes these failures. See the warning in https://wiki.archlinux.org/index.php/PKGBUILD#source

lsf commented on 2021-04-28 13:29 (UTC)

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

robert1234 commented on 2021-04-28 13:01 (UTC) (edited on 2021-04-28 13:02 (UTC) by robert1234)

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

lsf commented on 2021-04-05 20:35 (UTC)

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

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

FabioLolix commented on 2021-04-05 20:18 (UTC)

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

lsf commented on 2021-04-05 20:16 (UTC)

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.

« First ‹ Previous 1 .. 17 18 19 20 21 22 23 24 25 26 27 28 Next › Last »