i know(sort of, phew). wouldn’t have updated if i noticed it earlier. hence why the early warning to the other folks here.
lil clarification, I’ve seen some package updates coming right from arch testing, while others only when promoted to arch stable while updating in Manjaro unstable branch. would be great if you can tell the process.
not raising unnecessary alarm, noticed it happening for months now, only this one was odd
mmm, sorry but it seems manjaro unstable is quiet behind arch stable today and hardly any of the pending packages are coming through. is something down, perhaps for maintenance or something
Manjaro has a kde unstable repo, if you are willing to accept the fact it won’t have any type of curation. Otherwise, just wait a bit longer for those who are perusing that repo to iron out some bugs.
That is as true as it gets, but there are always adjustments and tweaks, like overlays, for example. Manjaro isn’t Arch, so it isn’t just a matter of pulling from Arch.
i’m sorry keeping this a rally. i’m aware of overlays and syncs, the packages that i’m seeing delayed are of sync variety (to my understanding), which are supposedly synced with with arch every hour to manjaro repos. i’m only worried about delays because of the mantra that to keep unstable branch boxes trouble free is to keep them updated often and nothing else.
hwdata replaces hwids, but systemd is still linked with hwids dependency.
For now, I cannot update my system. (and if I could, I would not want to break systemd…)
Current version of systemd is flagged out of date and next version is in Arch testing.
I’ll wait for it to go through Arch stable then Manjaro unstable.
:: Début de la mise à jour complète du système…
:: Remplacer hwids par core/hwdata ? [O/n] o
résolution des dépendances…
avertissement : impossible de résoudre « hwids », une dépendance de « systemd »
avertissement : impossible de résoudre « hwids », une dépendance de « systemd »
:: Le paquet suivant ne peut être mis à jour à cause de dépendances insolubles :
systemd
:: Voulez-vous ignorer le paquet ci-dessus pour cette mise à jour ? [o/N] o
recherche des conflits entre paquets…
erreur : la préparation de la transaction a échoué (la satisfaction des dépendances a échoué)
:: la suppression de hwids casse la dépendance « hwids » requise par systemd
I know that is not about Python 3.10 but actual unstable kernel 5.16 and 5.15.14 has regression with amdgpu and is not the firmware. I reported too in kernel.org.
The memclk stuck at 100%.
Tested too with the latest firmware, so is the kernel.
The people of kernel.org closed the bug because says that is freedesktop/amd/drm.
Anyway. the update kernel 5.16.1 and 5.15.15 solves the bug, i don’t understand how, because the changelog of kernel.org no show nothing related with amdgpu or drm amd.
The following message is now in the wikipost of the Jan 17 testing announcement,
as well as in the Jan 02 stable announcement.
There’s no wikipost in this Unstable announcement, so here’s the message:
Python packages from PIP and AUR - how to upgrade them - detailed instructions:
Read this post.