sorry false alarm. Just realized that something undid my changes to the build scripts in /usr/share/devtools/makepkg.conf.d without generating pacnew's or pacsave's -.-
With v4 optimizations it…
@anonfunc llvm/clang 19 seems to finally fix the firefox build, at least I could now build it in a clean chroot with v4 optimizations.
yes, as rebuilds aren't working at the moment, you should comment out the alhp mirrors until the issue is solved. (or not update until the issue is fixed and the rebuilds are done, but from a…
Just to add, Server = https://alhp.krautflare.de/$repo/os/$arch/ was working troublefree for the last months.
Arch wants to offer v3 for quite some time now, they even started preparing stuff in the background but didn't pull through because of build times: https://gitlab.archlinux.org/archlinux/devtools/…
I think that is ok. I don't expect that Arch developers will change their package for third party repositories
and then update with
pacman -Syu --assume-installed tinysparql
That looks cleaner, but I also have no way to test that atm.
wouldn't that leave the system with an…
for the record, those are the files that conflict:
tinysparql: /usr/lib/girepository-1.0/Tracker-3.0.typelib exists in filesystem (owned by tracker3)
tinysparql: /usr/lib/libtracker-sparql-3…
running sudo pacman -Syu --assume-installed tinysparql
the update applies but it breaks gtk during the update:
(14/19) Probing GTK3 input method modules...
/usr/bin/gtk-query-immodules-3…
I understand that.
What about starting alhp rebuilds with .2 for V2 and for bugfix rebuilds use .12 - meaning the first digit indicates the rebuild, the second still indicates the version? I…
This would still require setting all repos tho, so the benefit would be very minimal.
Yes, but it would "fix" that:
The only drawback would be that if that package is later…
I guess he wants to say, instead of setting .1 for each rebuild, set .2 for V2, .3 for v3 and .4 for v4. That way, the highest feature level will always be the one that gets used, no matter if…
Personally, I have very good experience with Zram and the zram-generator…
at least Arch also sees the problem of their ultra late llvm/clang updates: https://gitlab.archlinux.org/archlinux/packaging/packages/llvm/-/issues/3
thanks, the mega rebuild seems to have finished well - failed down to 866