[ARM Unstable Update] 2024-05-14 - Toolchain, Python 3.12, LxQT 2.0, Gnome 46.1

@spikerguy @linux-aarhus Wasn’t this already addressed? :thinking: :point_up:

@Delor3an91 Either way, if you change something that’s different than default, then you keep the change and ignore the pacnew.

By the way, please do not crosspost the same thing to multiple topics. Once is enough.

This is not the same - as the issue addressed.

As you are looking at the .pacnew that is correct - 'stable* is the default - also on arm.

pacman-mirrors verifies the architecture and prefix the branch with arm- on first run if running on aarch64.

The reason for the pacnew file - pacman-mirrors has been updated - it has a new Static configuration option.

I believe so.

While we are used to see - on x86 - this content

# Standard host addresses
127.0.0.1  localhost
::1        localhost ip6-localhost ip6-loopback
ff02::1    ip6-allnodes
ff02::2    ip6-allrouters
# This host address
127.0.1.1  manjaro

As I originally used Arch Linux - I never gave it a thought - I always configured the file by hand.

:man_shrugging:

I have never seen it on Manjaro Arm - whether that is an oversight - I don’t know - what I do know is that the system work without - possibly a systemd thingy :slight_smile:

GT King Pro - KDE-Plasma Unstable Branch upgraded successfully to KDE Plasma 6.1.4.

2 Likes

My pi5 upgrade went smooth here also with today’s upgrade on unstable.

I do not use wpa_supplicant but if you have a pi4, pi5 or pinebook pro you might want to have a copy of wpa_supplicant-2_2.10-8 handy to revert back to just in case you have issues after upgrade.

https://archlinuxarm.org/forum/viewtopic.php?f=15&t=17007

1 Like

can we install Manjaro then move to Alarm’s repos, update packages faster 1 or 2 weeks.

you will break your setup cause we do not use arch linux arm’s kernel and their update will be ahead of ours so it can break pkgs which are binded to a different version of its dependencies.

Don’t try, it may work for some update but crash badly on some updates.

1 Like

I have just now upgraded from testing to unstable on my Pinebook Pro.
Unfortunately wifi does not connect any more.
In the log network manager complains about no secrets.
The connection, and other that I tried were working fine before the update.

Any tip would be appreciated.

Look at my post #23 above.

Thanks. That was a good hint. I missed that it was relevant for the Pinebook Pro.

unstable has version 2.11 of wpa_supplicant installed and this caused the issue on the PBP

This is what worked for me:

  • the problem is to get the downgraded version 2.10 of wpa_supplicant on your PBP as the wifi is not working.
  • from Pinetab2 days I knew that it is quite easy to tether the network from an iPhone (or Android). To use the iPhone for network, enable the Personal Hotspot in the iPhone settings. Connect the iPhone with a USB-C cable to the PBP. Trust the PBP on the iPhone. This should do it.
  • With network restored, download the 2.10 version from the stable branch of a manjaro.org mirror, e.g. https://manjaro.mirrors.uk2.net/arm-stable/core/aarch64/
  • once downloaded you can use sudo pacman -U wpa_supplicant-2_2.10-8-aarch64.pkg.tar.xz in the files folder to downgrade the version.
  • reboot and for me it worked

Wpa_supplicant is still buggy mess on RPI5. Even with the wpa_supplicant-2:2.11-2 update.

Will you or someone else with a rpi or pine device that has been having issues do a test for me and test with the new package firmware-raspberrypi 20240810-1 I pushed to unstable this mourning. You will also have to test this with the latest wpa_supplicant

I usually monitor arch-arm new packages and rebuild some packages when they do but looks like both of us has let this one slip through the cracks. RPi has updated things several times since my last update. Looking at the commits I believe this one may be part of the problem:

https://github.com/RPi-Distro/firmware-nonfree/pull/46

1 Like

That firmware update fixed it. I’m wondering why they didn’t catch it.

No improvement on the Pinebook, but as I understand the changes were for the Raspberry Pi?

You may be right. Double checking looks like maybe only the pinephone-pro might use the package. Not sure though I did not add the line in the package.

https://gitlab.manjaro.org/manjaro-arm/packages/community/firmware-raspberrypi/-/blob/master/PKGBUILD?ref_type=heads#L58

They have most of their packages get checked automatically for updates. Guess this one is not on the list. They updated today. See the last post by graysky here. In case you are wondering another user on RPi5B is you. :wink:

https://archlinuxarm.org/forum/viewtopic.php?f=15&t=17007

1 Like

[aarch64] possibly not yet updated packages or not yet synchronised in the mirror servers.:

WARNING: '/usr/lib/perl5/5.38' contains data from at least 4 packages which will NOT be used by the installed perl interpreter.
 -> Run the following command to get a list of affected packages: pacman -Qqo '/usr/lib/perl5/5.38'
$ pacman -Qqo '/usr/lib/perl5/5.38'
perl-error
perl-io-tty
perl-mailtools
perl-timedate

I also had similar issues yesterday but with the latest today all is good here.

[ray@jellyfin ~]$ pacman -Qqo '/usr/lib/perl5/5.38'
error: No package owns /usr/lib/perl5/5.38```
1 Like

GT King Pro - KDE-Plasma Unstable Branch, upgraded to KDE Plasma 6.1.5-1 and other packages successfully today.

Orange-pi5-plus-KDE-Plasma upgraded successfully.

1 Like

confirmed