https://bugs.kde.org/show_bug.cgi?id=456345
I was told it was not an upstream problem. :/ I did eventually figure it out: it didn't like that kwayland was a git package from a some time ago;…
Seems, you're right; this is some other problem but I have no idea what it is... I haven't touched anything between yesterday and today to make this happen besides updating though, so I'm really…
How would I downgrade everyhthing if the ALHP repos are considered newer versions?
Yes
Here's my pacman.conf:
I just realized that I mistyped that line... I was doing it by hand at the time and I feel really stupid now... Lol Sorry
[core-x86-64-v3]
Include =…
https://wiki.archlinux.org/title/Debuginfod https://debuginfod.archlinux.org/
The feature has "landed"
More information is provided in the arch-dev-public mailing list
@anonfunc Although, packages not using their real architecture names does put me at risk of making mistakes like this (mixing of architectures) if I'm not paying attention:
::…
I don't have problems upgrading anymore 👍
Originally though, I was moreso confused that ALHP packages were considered a "newer version upgrade" to pacman; I was under the impression that both…
@anonfunc Seems that way I was hesitant to update because I hadn't realized how massive the number of packages that were being rebuilt was Lol
In the meantine, I'm using shiny-mirrors from the AUR; it's written in Rust, so it's pretty reliable :p
Both Cloudfare and North America (since Cloudfare has been known to go down sometimes causing things like YouTube outages, I though it a good idea to keep a backup mirror)
##
## ALHP…
Also, I'm getting this error now (which is unrelated but also an issue):
neko-san@ARCH ~>doas pacman -Suy
doas (neko-san@ARCH) password:
error: extra-x86-64-v3: signature from "Archlinux CIE…
@anonfunc I did use it as described in the readme, I was only referencing the frontend as a means to visually display the issue - this is entirely pacman's doing.