| 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: | 146 |
| Popularity: | 4.80 |
| First Submitted: | 2019-06-14 18:41 (UTC) |
| Last Updated: | 2024-12-15 09:44 (UTC) |
Might've actually just been adding !lto to options – for reasons unknown (to me at least, didn't yet do any proper research into why ;), that now seems to be required for quite a few packages using rust/cargo. Or might've not been the reason (as it worked in my chroot) – who knows.
For now though I just hope things will work again for you with 96.0-1 – if not, don't hesitate to comment again! :)
@lsf Apologies and thanks for setting me straight!
Did you also run in a fresh chroot? I wonder if there's some base rust dependency that's implicit and missing...
Anyway, this is a quite fresh environment (only installed Arch the other day; built a decent number of other AUR packages with rust in the chroot since). Building via aurutils -cT. The pacman-custom.conf is just the official repos plus my own local with aur artefacts - nothing that is overriding there either.
Will return to this shortly.
Please don't mark the package out of date for an issue like this – that's not what the function is for, and I got a notification of your regular comment just fine :)
I cannot reproduce this on my end (and as far as I can see none of the "relevant" dependencies seem to have changed / been updated in the repos).
Is there anything 'unusual' with your environment / chroot? (maybe a separately installed package; maybe you're on manjaro; maybe the mirrorlist in it is out of date so it couldn't be properly updated?) If all else failed, I'd try to cleanly set the chroot up anew and check if you still have the issue then.
This won't build in a chroot for me, seems to be something missing for rust:
Related issues:
https://github.com/rust-lang/rust/issues/43264
https://github.com/rust-lang/rust/issues/74657
https://bugs.llvm.org/show_bug.cgi?id=47872
I haven't resolved it yet. So far I tried substituting rust for rustup and setting various toolchains and removing ac_add_options --enable-lto.
Tail of build log: https://gist.github.com/3nprob/4a420a9ee6ae956dd8641de6be32c55f
pip check: There is a discussion and a patch: https://bugs.gentoo.org/show_bug.cgi?id=828604
Same issue her due to "pip check"!
@ginnokami I've had that issue a little while ago too; my solution was just building it in a chroot but I know not everyone knows how to do that
Is anyone else having an issue compiling due to pip check having missing/updated/ dependencies? Running pip check will list some "missing or too updated packages" though all the actual programs run fine, and reinstalling the packages doesn't make the issue go away.
Exception: According to "pip check", the current Python environment has package-compatibility issues.pip check
qmk 1.0.0 requires qmk-dotty-dict, which is not installed.
dotty-dict 1.3.0 requires setuptools-scm, which is not installed.
electrum 4.1.5 has requirement dnspython<2.1,>=2.0, but you have dnspython 2.1.0.
electrum 4.1.5 has requirement qdarkstyle<2.9, but you have qdarkstyle 3.0.2.I think because of the wayland 1.20 update, projects have to update their code for new wayland release
Currently this patch is required for compiling FF95 :)
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).