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)

Sources (3)

Latest Comments

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

lsf commented on 2021-02-09 23:31 (UTC)

Thanks for spotting that – I must've forgotten to commit the updated file.

Should be fixed now over here as well!

Jayman commented on 2021-02-09 23:12 (UTC)

When I try to build this package, I get an error:

[jayman@Jason-Desktop-Linux librewolf]$ makepkg
==> Making package: librewolf 85.0.1-1 (Tue 09 Feb 2021 05:58:38 PM EST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found firefox-85.0.1.source.tar.xz
  -> Found librewolf.desktop
  -> Updating common git repo...
Fetching origin
  -> Updating settings git repo...
Fetching origin
  -> Found megabar.patch
  -> Found remove_addons.patch
  -> Found unity-menubar.patch
==> Validating source_x86_64 files with sha256sums...
    firefox-85.0.1.source.tar.xz ... Passed
    librewolf.desktop ... Passed
    common ... Skipped
    settings ... Skipped
    megabar.patch ... Passed
    remove_addons.patch ... Passed
    unity-menubar.patch ... FAILED
==> ERROR: One or more files did not pass the validity check!
[jayman@Jason-Desktop-Linux librewolf]$

Here's how I avoided the error:

$ git clone git@gitlab.com:librewolf-community/browser/linux.git
$ cd linux
$ makepkg

lsf commented on 2021-02-07 13:02 (UTC)

Hm, wouldn't the https://addons.mozilla.org/en-US/firefox/addon/plasma-integration/ extension be sufficient for this? (I have no real idea – just asking to understand it better :)

If the patches would indeed be required: seems it could be relatively painless to include them as well (or at least to include them optionally), assuming they don't break things on non-KDE systems (or have privacy implications).

Would you care to open an issue for this on https://gitlab.com/librewolf-community/browser/linux/ ? That would make it easier to track it and to discuss it with the rest of the team :)

ZorinArch commented on 2021-02-07 12:56 (UTC)

Hi lsf, can you add opensuse patches https://build.opensuse.org/package/show/mozilla:Factory/MozillaFirefox for better KDE integration. Thanks

lsf commented on 2021-02-01 21:34 (UTC)

I'd recommend double-checking if the menubar-patch is truly not applied, ie. checking if lines 145-148 look like this:

# Debian patch to enable global menubar
# disabled until it's updated upstream
# also disabled for the default build, as it seems to cause issues in some configurations
# patch -p1 -i ../unity-menubar.patch

Maybe something got mixed up when you updated your modified PKGBUILD ^^

(the unity-menubar.patch is the only thing that patches parts of those files causing your errors, also it being commented out is one distinct change between this version and the previous one)

lsf commented on 2021-02-01 20:40 (UTC) (edited on 2021-02-01 20:43 (UTC) by lsf)

Have you modified the PKGBUILD in any way?

I've only had that issue (or at least one that looks like it) when building with the not yet updated unity-menubar.patch applied (which is why it's currently commented out).

Here's the log: https://gitlab.com/librewolf-community/browser/linux/-/jobs/990519675

It might've been a coincidence, though.

Without it, things built fine: https://gitlab.com/librewolf-community/browser/linux/-/jobs/997630646

/edit

Thanks for the hint with the LDFLAGS, btw. – hadn't caused any issues yet (for me), but I wasn't aware of that.

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