Branch switching: back to stable from testing; a lot of "newer than extra"

Support
1

Hi, on 26 August (two days ago) I switched from stable to testing branch, but today I changed my mind, because I cannot always (lack of time) update the system with higher frequency.

On 26 August, when switching to testing branch I applied the update which went fine; today I back to stable and I applied the update ([Stable Update] 2020-08-28 - Kernels, Systemd, PAM, PAMBASE, KDE-git, Deepin, Pamac, Nvidia 450.66, LibreOffice 7.0), and as expected I only got the upgrade of systemd from 246.2-2 to 246.3-2

Whereas the 26 August on testing branch I applied the update ([Testing Update] 2020-08-26 - Firefox 80, CoreCTRL, Xorg-Server, AMDVLK, Python, Haskell), now on stable branch again, a lot of packages on my system are newer, so pacman -Syyu gave me these warnings; but everything is still ok, I didn’t faced any errors nor malfunctions.

sudo pacman -Syyu:

Summary

:: Synchronizing package databases…
core 168,8 KiB 1639 KiB/s 00:00 [###################################################] 100%
extra 2013,1 KiB 8,66 MiB/s 00:00 [###################################################] 100%
community 6,1 MiB 9,12 MiB/s 00:01 [###################################################] 100%
multilib 194,9 KiB 11,2 MiB/s 00:00 [###################################################] 100%
herecura 67,6 KiB 1024 KiB/s 00:00 [###################################################] 100%
:: Starting full system upgrade…
warning: apr-util: local (1.6.1-8) is newer than extra (1.6.1-7)
warning: cups-filters: local (1.28.0-1) is newer than extra (1.27.5-1)
warning: firefox: local (80.0-1) is newer than extra (79.0-1)
warning: firefox-i18n-en-us: local (80.0-1) is newer than extra (79.0-1)
warning: firefox-i18n-it: local (80.0-1) is newer than extra (79.0-1)
warning: jasper: local (2.0.19-1) is newer than extra (2.0.17-1)
warning: libmediainfo: local (20.08-1) is newer than community (20.03-1)
warning: libqmi: local (1.26.4-1) is newer than extra (1.26.2-1)
warning: libreoffice-still: local (6.4.6-2) is newer than extra (6.4.6-1)
warning: libsynctex: local (2020.54586-5) is newer than extra (2020.54586-4)
warning: libuv: local (1.39.0-1) is newer than extra (1.38.1-1)
warning: libx11: local (1.6.12-1) is newer than extra (1.6.11-1)
warning: linux-firmware: local (20200824.r1697.74bd44f-1) is newer than core (20200817.r1695.7a30af1-1)
warning: manjaro-hello: local (0.6.5-12) is newer than extra (0.6.5-11)
warning: manjaro-release: local (20.1-0.1) is newer than core (20.1-0)
warning: mediainfo: local (20.08-1) is newer than community (20.03-1)
warning: nano: local (5.2-1) is newer than core (5.1-1)
warning: pamac-cli: local (9.5.8-2) is newer than extra (9.5.8-1)
warning: pamac-common: local (9.5.8-2) is newer than extra (9.5.8-1)
warning: pamac-gtk: local (9.5.8-2) is newer than extra (9.5.8-1)
warning: pipewire: local (0.3.10-1) is newer than extra (0.3.8-2)
warning: poppler: local (20.08.0-1) is newer than extra (0.90.1-1)
warning: poppler-glib: local (20.08.0-1) is newer than extra (0.90.1-1)
warning: poppler-qt5: local (20.08.0-1) is newer than extra (0.90.1-1)
warning: python-keyring: local (21.3.1-1) is newer than community (21.3.0-1)
warning: steam-manjaro: local (1.0.0.66-1) is newer than multilib (1.0.0.64-1)
warning: talloc: local (2.3.1-3) is newer than extra (2.3.1-2)
warning: telegram-desktop: local (2.3.2-1) is newer than community (2.3.0-2)
warning: tracker: local (2.3.5-1) is newer than extra (2.3.4-2)
warning: vim: local (8.2.1522-1) is newer than extra (8.2.1490-0.1)
warning: vim-runtime: local (8.2.1522-1) is newer than extra (8.2.1490-0.1)
warning: vmaf: local (1.5.3-1) is newer than community (1.5.2-1)
warning: xorg-server: local (1.20.9-1) is newer than extra (1.20.8-4)
warning: xorg-server-common: local (1.20.9-1) is newer than extra (1.20.8-4)
warning: xterm: local (359-1) is newer than extra (358-1)
upgraded systemd-libs (246.2-2 -> 246.3-2)
upgraded systemd (246.2-2 -> 246.3-2)
upgraded systemd-sysvcompat (246.2-2 -> 246.3-2)

Can I stay peaceful or I risk to see my sysem borked/ruined in some way?
I guess that these warnings will disappear when the stable branch will be synched with the same packages (or updated) which are on testing branch?

2

Hi!
It’s just informative that you have more newer packages than the branch, once those packages reach the stable branch and have been updated, you’ll not see any warnings

1 Like
3

Thank you for the confirmation :+1:

4

if you want only stable version for all packages (best) use 2 “u” pacman -Syyuu

1 Like
5

Good to know, thank you; however I’m fine with the current packages, since I didn’t had/have any issue (I meticulously checked the journal log) :slight_smile:

6

yes, but no issue “for the moment” :wink: we need to test all applications to find out
There’s always a big risk to mix 2 branches - usually it’s a tragedy.

7

Since 9 February 2019 (the first time when I installed Manjaro) for the sake of lucky I never faced a tragedy :slight_smile:
And however for me is ok and “funny” (also thanks to the Arch Wiki) attempts to resolve, report bugs/issues and try to rely on suggestions of expert users here on the forum :+1:

8

sometimes we have versions in dependencies
a example:

pacman -Qi systemd
...
Depends On      : acl  libacl.so=1-64  bash  cryptsetup  libcryptsetup.so=12-64  dbus  iptables  kbd  kmod  libkmod.so=2-64  hwids  libcap
                  libcap.so=2-64  libgcrypt  libxcrypt  libcrypt.so=2-64  systemd-libs  libidn2  libidn2.so=0-64  lz4  pam  libelf  libseccomp
                  libseccomp.so=2-64  util-linux  libblkid.so=1-64  libmount.so=1-64  xz  pcre2  audit  libaudit.so=1-64  libp11-kit  libp11-kit.so=0-64
                  openssl

if you have a stable systemd BUT libcryptsetup.so is a testing package (cryptsetup) with a higher version (13-64) … :fearful: systemd is break

you’re just lucky :wink:

if versions in dependencies pacman don’t want update, but if version is not written pacman make update and no warranty

1 Like
9

This was priceless

I don’t know HOW I am getting newer (aka testing/unstable) versions of packages, I don’t recall ever explicitly switching to a branch other than stable, but the most recent anomaly involved pamac packages.

Is it safe to always use this variant as my default update command, instead of sudo pacman -Syyu ?

Moreover, would there be any problems introduced by always updating the mirrors first before calling the above (in a dedicated shell alias), e.g., sudo pacman-mirrors -f; sudo pacman -Syyuu ?

10

yy is useful only when we change mirror
uu is for downgrade (useful only if we have problem or for pass testing to stable)
pacman-mirror : we use it only if we travel or for change branch

sometime, rarely, as pamac here, manjaro maintainer can downgrade a package, you use uu only if you want prev version