[Unstable Update] 2021-12-13 - Python 3.10 Rebuilds

[koshikas]

thought manjaro unstable branch meant no curation, i’ve even found stuff in arch unstable here(like the bash update yesterday)

[clmbtti]

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.

[koshikas]

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.

[Falav]

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

[koshikas]

@Yochanan do we have a situation of repos not being synced “properly” (that is from arch to manjaro unstable) of late. just askin’

[Yochanan]

@Falav

hwdata replaces hwids, but systemd is still linked with hwids dependency.

Resolved with systemd 250.1-2 coming along shortly.

@koshikas

do we have a situation of repos not being synced “properly”

Yes, but not for long. I just woke up and am now playing catch-up.

[clmbtti]

@Yochanan arch devs are in a hurry there, hmm. They’ve flagged 250.1-2 in the same day they last updated it to core, while 250.2-2 is in testing.

[Nixsasl]

Hello,

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.

https://bugzilla.kernel.org/show_bug.cgi?id=215491

Edit 1:

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.

[j77h]

@philm

You will need to rebuild any AUR packages that install files to site-packages.

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.

[mr_glitch]

Hi
There is an issue while upgrading jack2 and jack2-dbus:

Preparing...
Synchronizing package databases...
Warning: removing jack2 breaks dependency 'jack2' required by jack2-dbus
Add jack2-dbus to remove
Warning: removing jack2 breaks dependency 'jack2=1.9.20' required by lib32-jack2
Add lib32-jack2 to remove
Error: Failed to prepare transaction:
could not satisfy dependencies:
- removing jack2-dbus breaks dependency 'jack2-dbus' required by cadence,
- if possible, remove cadence and retry
Resolving dependencies...
Checking inter-conflicts...
Error: Failed to prepare transaction:
could not satisfy dependencies:
- removing jack2-dbus breaks dependency 'jack2-dbus' required by cadence,
- if possible, remove cadence and retry

[Yochanan]

Remove cadence, update then reinstall it.

[mr_glitch]

After removing Cadence and update, when I’m trying to install Cadence back there is a warning:

Warning: removing pipewire-jack breaks dependency 'pipewire-jack' required by manjaro-pipewire
Add manjaro-pipewire to remove

I guess jack2 and jack2-dbus doesn’t like themselves with pipewire now

---

Edit:
I’ve noticed that while updating, 5.10 realtime kernel was removed and 5.15 kernels (normal and rt) were installed.

I’ve removed 5.15 kernels and installed 5.10 rt again, and while installing Cadence, Pamac want to remove 5.10 rt and install 5.15 rt.

[El_Brujo]

[Unstable Update] 2021-12-13 - Python 3.10 Rebuilds

Hey folks! The only thing I noticed at the moment is that I’m no longer able to manage bluetooth devices via Gnome Settings. I’m fully using Pipewire as media server. I haven’t had a chance to troubleshoot this yet but will do as soon as I can

[Unstable Update] 2021-12-13 - Python 3.10 Rebuilds

Going back to the issue above, it appears to happen only with kernel series 5.15 every time my system boots up from a restart. If I previously power off my system and then I boot it up again with kernel 5.15, then I will be able to manage Bluetooth devices from Gnome Settings. This odd behaviour was introduced for me after this major update, although it never happens with kernel series 5.10. No big deal, but still I think it’s worth reporting this in case someone else experiences the same in …

I confirm the above issue is no longer present for me as of the release of kernel 5.15.15, which makes me think that this regression with Intel Bluetooth was finally fixed upstream.

Before kernel 5.15.15:

Jan 05 23:20:39 manjaro-unstable kernel: Bluetooth: Core ver 2.22
Jan 05 23:20:39 manjaro-unstable kernel: NET: Registered PF_BLUETOOTH protocol family
Jan 05 23:20:39 manjaro-unstable kernel: Bluetooth: HCI device and connection manager initialized
Jan 05 23:20:39 manjaro-unstable kernel: Bluetooth: HCI socket layer initialized
Jan 05 23:20:39 manjaro-unstable kernel: Bluetooth: L2CAP socket layer initialized
Jan 05 23:20:39 manjaro-unstable kernel: Bluetooth: SCO socket layer initialized
Jan 05 23:20:40 manjaro-unstable kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jan 05 23:20:40 manjaro-unstable kernel: Bluetooth: BNEP filters: protocol multicast
Jan 05 23:20:40 manjaro-unstable kernel: Bluetooth: BNEP socket layer initialized
Jan 05 23:20:42 manjaro-unstable kernel: Bluetooth: hci0: command 0xfc05 tx timeout
Jan 05 23:20:42 manjaro-unstable kernel: Bluetooth: hci0: Reading Intel version command failed (-110)

After kernel 5.15.15, by only restarting my system:

Jan 20 10:33:46 manjaro-unstable kernel: Bluetooth: Core ver 2.22
Jan 20 10:33:46 manjaro-unstable kernel: NET: Registered PF_BLUETOOTH protocol family
Jan 20 10:33:46 manjaro-unstable kernel: Bluetooth: HCI device and connection manager initialized
Jan 20 10:33:46 manjaro-unstable kernel: Bluetooth: HCI socket layer initialized
Jan 20 10:33:46 manjaro-unstable kernel: Bluetooth: L2CAP socket layer initialized
Jan 20 10:33:46 manjaro-unstable kernel: Bluetooth: SCO socket layer initialized
Jan 20 10:33:46 manjaro-unstable kernel: Bluetooth: hci0: Legacy ROM 2.5 revision 1.0 build 3 week 17 2014
Jan 20 10:33:46 manjaro-unstable kernel: Bluetooth: hci0: Intel device is already patched. patch num: 32
Jan 20 10:33:46 manjaro-unstable kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jan 20 10:33:46 manjaro-unstable kernel: Bluetooth: BNEP filters: protocol multicast
Jan 20 10:33:46 manjaro-unstable kernel: Bluetooth: BNEP socket layer initialized
Jan 20 10:33:50 manjaro-unstable kernel: Bluetooth: RFCOMM TTY layer initialized
Jan 20 10:33:50 manjaro-unstable kernel: Bluetooth: RFCOMM socket layer initialized
Jan 20 10:33:50 manjaro-unstable kernel: Bluetooth: RFCOMM ver 1.11

Cheers!

[Yochanan]

@mr_glitch

I guess jack2 and jack2-dbus doesn’t like themselves with pipewire now

See FS#73427 - [pipewire-jack] conflicts with jack2 but doesn’t provides?

[Yochanan]

linux-firmware 20220119.0c6a7b3-2 requires kernel >=5.3 and package splitting

2022-01-21 - Andreas Radke

The linux-firmware package 20220119.0c6a7b3-2 implements kernel firmware compression. Linux kernel from 5.3 on support loading from xz compressed firmware.
CONFIG_FW_LOADER_COMPRESS kernel option must be enabled. All official Arch Linux kernel support this for a long time. [1]

The linux-firmware package has been split into smaller packages to further reduce required disk space. Some big firmware files of rarely used hardware have been split into separate packages.
This affects firmware for Mellanox Spectrum switches, Marvell devices, Qualcomm SoCs, Cavium LiquidIO server adapters, QLogic devices, Broadcom NetXtreme II 10Gb ethernet adapters.
Make sure to install additional firmware packages if needed. [2]

[1] FS#72899
[2] FS#72559 + svn commit

For users with kernels <5.3 installed, they will need to migrate to a 5.x kernel. The 4.x series is now dropped from the repos.

[pheiduck]

Any difference from linux-firmware-whence provided by Arch Linux?

[freggel.doe]

I’m really liking reduced size of linux-firmware.