[ARM Unstable Update] 2023-05-16 - Python 3.11, Gnome 44, Plasma, KDE Frameworks and more

Archlinux ARM pushed 4192 packages as massive update to their repos. This includes python 3.11, Gnome 44, latest Plasma and KDE Frameworks and more. This will take a while until we stabilized this. Feel free to post issues you may have here.

List of python packages needed a rebuild: [python] rebuild for 3.11 (#1) · Issues · manjaro-arm / issues / Packages · GitLab

Additional Info

:information_source: You will need to rebuild any AUR Python packages that install files to site-packages or link to libpython3.10.so. :information_source:

Print a list of of packages that have files in /usr/lib/python3.10/ :

pacman -Qoq /usr/lib/python3.10/

Rebuild them all at once:*

pamac build $(pacman -Qoq /usr/lib/python3.10)

* Note that if any fail to build, you’ll have to rebuild what’s remaining one or a few at a time.

Use rebuild-detector to see if anything else needs to be rebuilt:

checkrebuild
Info about AUR packages

:warning: AUR (Arch User Repository) packages are neither supported by Arch nor Manjaro. Posts about them in Announcement topics are off-topic and will be flagged, moved or removed without warning.

3 Likes

I have pushed these packages built with the new python to the unstable branch when the mirrors sync.

The kodi-rpi packages also has a version upgrade along with python rebuild.

The rpi-eeprom package also has yesterday’s version upgrade along with python rebuild. They promoted the beta to stable.

[ray@jellyfin ~]$ sudo rpi-eeprom-update 
BOOTLOADER: up to date
   CURRENT: Thu May 11 06:26:03 AM UTC 2023 (1683786363)
    LATEST: Thu May 11 06:26:03 AM UTC 2023 (1683786363)
   RELEASE: stable (/lib/firmware/raspberrypi/bootloader/stable)
            Use raspi-config to change the release.

  VL805_FW: Using bootloader EEPROM
     VL805: up to date
   CURRENT: 000138c0
    LATEST: 000138c0

New packages:

handbrake 1.6.1-3
handbrake-cli 1.6.1-3
kodi-rpi 20.1-6
kodi-rpi-dev 20.1-6
kodi-rpi-eventclients 20.1-6
kodi-rpi-git 21.x.62999.2269ed2a92-4
kodi-rpi-git-dev 21.x.62999.2269ed2a92-4
kodi-rpi-git-eventclients 21.x.62999.2269ed2a92-4
kodi-rpi-git-tools-texturepacker 21.x.62999.2269ed2a92-4
kodi-rpi-tools-texturepacker 20.1-6
rpi-eeprom 20230515-1

pacman -Qoq /usr/lib/python3.10/
btrfs-progs
glusterfs
mugshot
pacman-mirrors
python-npyscreen
python-wcwidth
python-wxpython

1 Like

Could you synchronize with arch for the equivalent packages :

raspberrypi-bootloader 20230512-1
raspberrypi-firmware 20230516-1 (userland)
firmware-raspberrypi 20230125-1

I can add
pibootctl 0.6-2 community 698,1 Ko

Our equivalents were pretty much up to date. There does not seem to be any python depends in the packages.

Arch-arm updates their raspberrypi-bootloader every time a new kernel hits. I only update when the .dat / .elf or bootcode.bin changes. The rest of the files is provided by the kernel when it compiles.

https://github.com/raspberrypi/firmware/tree/master/boot

I only update the raspberrypi-firmware if some one has an issue or a new pi device is added. Some other devs here also uses our package as some other devices use bcrm firmware.

There was a recent update with our raspberrypi-userland package and I just pushed it to the unstable branch when the mirrors sync.

raspberrypi-userland-aarch64-git r843.cc1ca18-1

pacman -Qoq /usr/lib/python3.10/

Add to the list:

arcus
libsavitar
packagekit
python-pynest2d
uranium

It was updated

I added a list of Manjaro packages which may be affected by python update and need a rebuild.

There are packages in that list like pacman-mirrors and portfolio-file-manager that have already been rebuilt. Doesn’t seem very accurate.

I noted that also here: [python] rebuild for 3.11 (#1) · Issues · manjaro-arm / issues / Packages · GitLab

1 Like

I’ve updated the OP to include the issue instead of the snippet.

@Darksky did you rebuild those or just pointed them out?

So far I had to build packagekit here locally. For sure it is an arch-arm package.

I have not rebuilt:

arcus
libsavitar
packagekit # built locally only because of new kernel install hanging
python-pynest2d
uranium

I have rebuilt:these and pushed to the repo.

handbrake 1.6.1-3
handbrake-cli 1.6.1-3
kodi-rpi 20.1-6
kodi-rpi-dev 20.1-6
kodi-rpi-eventclients 20.1-6
kodi-rpi-git 21.x.62999.2269ed2a92-4
kodi-rpi-git-dev 21.x.62999.2269ed2a92-4
kodi-rpi-git-eventclients 21.x.62999.2269ed2a92-4
kodi-rpi-git-tools-texturepacker 21.x.62999.2269ed2a92-4
kodi-rpi-tools-texturepacker 20.1-6
rpi-eeprom 20230515-1

got raspberrypi-userland-aarch64-git-r843.cc1ca18-1, did not match?

That is the right one. I had the old version above. I corrected it. Thanks

https://gitlab.manjaro.org/manjaro-arm/packages/community/raspberrypi-userland-aarch64-git/-/commit/8001867609fd94559ce13255c3946270a14159a0

massive update but no gcc, or no benefit for ‘AARCH64’?

@Rip2 Have a little patience with gcc 13; it will come when arch-arm is ready.

There has been another version update today with kodi-rpi-git. It is a fix for those that use a 64 bit kernel with a 32 bit userspace. It has nothing to do with the new python upgrade and most likely does not affect us since we are all 64bit. I am posting here so no one will be confused with my earlier post above with a different version.

https://github.com/jc-kynesim/rpi-ffmpeg/commit/6859fc2a8791c0fcc25851b77fed15a691ceb332

kodi-rpi-git 21.x.63013.f02e604e5e-1
kodi-rpi-git-dev 21.x.63013.f02e604e5e-1
kodi-rpi-git-eventclients 21.x.63013.f02e604e5e-1
kodi-rpi-git-tools-texturepacker 21.x.63013.f02e604e5e-1

Hi @philm,

Was NOT able to complete the system upgrade. Error:

 harfbuzz-icu-7.3.0-1-aarch64                 7.5 KiB  26.0 KiB/s 00:00 [########################################] 100%
 plasma-wayland-session-5.27.5-1-aarch64      6.2 KiB  21.2 KiB/s 00:00 [########################################] 100%
 systemd-sysvcompat-253.4-1-aarch64           6.0 KiB  14.2 KiB/s 00:00 [########################################] 100%
 pipewire-alsa-1:0.3.70-2-aarch64             4.7 KiB  16.1 KiB/s 00:00 [########################################] 100%
 Total (324/324)                            918.2 MiB  3.70 MiB/s 04:08 [########################################] 100%
(324/324) checking keys in keyring                                      [########################################] 100%
(324/324) checking package integrity                                    [########################################] 100%
(324/324) loading package files                                         [########################################] 100%
(324/324) checking for file conflicts                                   [########################################] 100%
error: failed to commit transaction (conflicting files)
konsole: /etc/xdg/konsolerc exists in filesystem
Errors occurred, no packages were upgraded.

Would appreciate tips and assistance on how to resolve the Error:

> error: failed to commit transaction (conflicting files)
> konsole: /etc/xdg/konsolerc exists in filesystem
> Errors occurred, no packages were upgraded.

Edit: For your info, mesa-23.0.y and Firefox seems to have some conflict. Is have bad visual artifacts.

Same issue mesa-23.0.y with Firefox on Ubuntu Lunar. With mesa-23.1.0 resolved the Visual Artifacts issue on Firefox.

Edit 1: Found a solution to resolve the System Upgrade Error:

> error: failed to commit transaction (conflicting files)
> konsole: /etc/xdg/konsolerc exists in filesystem
> Errors occurred, no packages were upgraded.

from here: [ARM Testing Update] 2023-05-04 - Kernels, Firmware, Firefox, Thunderbird, KDE Gear, Phosh, Pipewire - #17 by marcuse1w.

Thanks @marcuse1w

[jfl@jfl-mnjro ~]$ cd /etc/xdg
[jfl@jfl-mnjro xdg]$ sudo mv konsolerc konsolerc-old

After move the “konsolerc” to “konsolerc-old”, “sudo pacman -Syu” proceeded to complete the System Upgrade.

(12/26) Updating linux-aml module dependencies...
(13/26) Updating linux-aml initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux-aml.preset: 'default'
  -> -k 6.1.29-1-MANJARO-ARM-AML -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: '6.1.29-1-MANJARO-ARM-AML'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [plymouth]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-linux.img'
==> Image generation successful
(14/26) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux-aml.preset: 'default'
  -> -k 6.1.29-1-MANJARO-ARM-AML -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: '6.1.29-1-MANJARO-ARM-AML'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [plymouth]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: '/boot/initramfs-linux.img'
==> Image generation successful
(15/26) Updating the appstream cache...
✔ Metadata cache was updated successfully.
(16/26) Updating uInitrd...
Image Name:   uInitrd Image
Created:      Fri May 19 13:19:48 2023
Image Type:   AArch64 Linux RAMDisk Image (uncompressed)
Data Size:    8642801 Bytes = 8440.24 KiB = 8.24 MiB
Load Address: 00000000
Entry Point:  00000000
(17/26) Updating uImage...
Image Name:   uImage
Created:      Fri May 19 13:19:54 2023
Image Type:   AArch64 Linux Kernel Image (uncompressed)
Data Size:    28088832 Bytes = 27430.50 KiB = 26.79 MiB
Load Address: 01080000
Entry Point:  01080000
(18/26) Reloading system bus configuration...
(19/26) Warn about old perl modules
(20/26) Updating fontconfig cache...
(21/26) Compiling GSettings XML schema files...
(22/26) Updating icon theme caches...
(23/26) Changing NetworkManager Connectivity-Ping to manjaro.org
(24/26) Configuring pacman-mirrors ...
::INFO Downloading mirrors from Manjaro
::INFO => Mirror pool: https://repo.manjaro.org/mirrors.json
::INFO => Mirror status: https://repo.manjaro.org/status.json
hint: use `pacman-mirrors` to generate and update your pacman mirrorlist.
(25/26) Updating the info directory file...
(26/26) Updating the desktop file MIME type cache...
[jfl@jfl-mnjro ~]$

Edit 2: Reboot successfully

Beelink GT King Pro - Manaro-Arm-KDE-linux-aml-6.1.29-1 Rebooted Successfully after System Update to latest Arm-Unstable-Updae-2023-05-16. But some applicatios does NOT seem to launch. Screenshot “Spectacle” does NOT launch.

[jfl@jfl-mnjro ~]$ spectacle
spectacle: error while loading shared libraries: libavcodec.so.60: cannot open shared object file: No such file or directory
[jfl@jfl-mnjro ~]$

[jfl@jfl-mnjro ~]$ chromium --incognito
/usr/lib/chromium/chromium: error while loading shared libraries: libavcodec.so.60: cannot open shared object file: No such file or directory

Spectacle and Chromium would NOT launch. This could be due to the fact that I have installed “ffmpeg-m2m and mpv-hwdec”. Flameshot also does NOT work.

Suggestions and solution on how to get Chromium and Spectacle to work with “ffmpeg-m2m and mpv-hwdec” installed are most welcome.

Beelink GT King Pro Manjaro-Arm-Gnome-linux-aml successfully switch from Arm-Testing to Arm-Unstable to test out Gnome-44.1.

sudo pacman-mirrors -aS unstable && sudo pacman -Syu

Instead of using sudo pacman-mirrors -aS unstable && sudo pacman -Syyu.

Is there a difference when switching from Testing to Unstable just using “sudo pacman -Syu”?