Testing branch is behind stable and stable-staging

I just switched from stable to testing from stable and got this warning:

sudo pacman -Syyu
[sudo] password for ben: 
:: Synchronizing package databases...
 core                                  171.8 KiB  80.5 KiB/s 00:02 [#####################################] 100%
 extra                                1901.9 KiB   808 KiB/s 00:02 [#####################################] 100%
 community                               6.7 MiB  2.62 MiB/s 00:03 [#####################################] 100%
 multilib                              177.2 KiB  87.0 KiB/s 00:02 [#####################################] 100%
:: Starting full system upgrade...
warning: alsa-card-profiles: local (1:0.3.37-1) is newer than extra (1:0.3.36-1)
warning: btrfs-progs: local (5.14.1-1) is newer than core (5.14-1)
warning: haveged: local (1.9.14-2) is newer than extra (1.9.14-1)
warning: pipewire: local (1:0.3.37-1) is newer than extra (1:0.3.36-1)
warning: pipewire-media-session: local (1:0.3.37-1) is newer than extra (1:0.3.36-1)
resolving dependencies...
looking for conflicting packages...

Packages (2) manjaro-release-21.1.5-1  mhwd-nvidia-470.74-1

Looking at the branch-compare, it appears stable-staging is far more updated than testing. Did you forget to snap some of the updates to testing before stable-staging and stable?

This happened the past months too, I never got a response about that. Probably they pushed updates to the wrong branch.

I noted that too - probably a human error - in my case - on unstable branch - it was clearly a humant error.

Which reminds me - never use the pacman downgrade option unless you know what you are doing.

2 Likes

As of today’s testing update, we are ahead of staging and stable again.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.