Pacman changes and updates

I have been using Manjaro Gnome almost a year and love it. I have noticed recently updates are less. (Although everything is quite stable and works awesome).
As an example gcc version is 12.2.1 . there was a change in Arch news related packages from community is being moved to extra.
https://archlinux.org/news/git-migration-completed/
and pacman has different setup on Arch.
And also I noticed my mirrorlist is smaller and
I also use Arch on my desktop and it has gcc version is 13.1.1 (as an example)
I am aware Manjaro is Arch based but has its own specific setup
Do I need to do something
My mirror list looks like this ;

## Manjaro Linux default mirrorlist
## Generated on 2023-05-27 14:04
##
## Please use 'pacman-mirrors -f [NUMBER] [NUMBER]' to modify mirrorlist
## (Use 0 for all mirrors)
##

## Country : Sweden
Server = https://ftp.lysator.liu.se/pub/manjaro/stable/$repo/$arch

## Country : Finland
Server = https://manjaro.kyberorg.fi/stable/$repo/$arch

## Country : Netherlands
Server = https://manjaro.mirror.wearetriple.com/stable/$repo/$arch

## Country : Poland
Server = https://repo.skni.umcs.pl/manjaro/stable/$repo/$arch

## Country : United_States
Server = https://coresite.mm.fcix.net/manjaro/stable/$repo/$arch

## Country : Hungary
Server = https://quantum-mirror.hu/mirrors/pub/manjaro/stable/$repo/$arch

## Country : United_States
Server = https://opencolo.mm.fcix.net/manjaro/stable/$repo/$arch

## Country : United_States
Server = https://mirrors.sonic.net/manjaro/stable/$repo/$arch

My pacman.conf is

#
# /etc/pacman.conf
#
# See the pacman.conf(5) manpage for option and repository directives

#
# GENERAL OPTIONS
#
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir     = /
#DBPath      = /var/lib/pacman/
#CacheDir    = /var/cache/pacman/pkg/
#LogFile     = /var/log/pacman.log
#GPGDir      = /etc/pacman.d/gnupg/
#HookDir     = /etc/pacman.d/hooks/
HoldPkg      = pacman glibc manjaro-system
# If upgrades are available for these packages they will be asked for first
SyncFirst    = manjaro-system archlinux-keyring manjaro-keyring
#XferCommand = /usr/bin/curl -L -C - -f -o %o %u
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
Architecture = auto

#IgnorePkg   =
#IgnorePkg   =
#IgnoreGroup =

#NoUpgrade   =
#NoExtract   =

# Misc options
#UseSyslog
Color
#NoProgressBar
CheckSpace
#VerbosePkgLists
ParallelDownloads = 5
ILoveCandy

# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
SigLevel    = Required DatabaseOptional
LocalFileSigLevel = Optional
#RemoteFileSigLevel = Required

# NOTE: You must run `pacman-key --init` before first using pacman; the local
# keyring can then be populated with the keys of all official Manjaro Linux
# packagers with `pacman-key --populate archlinux manjaro`.

#
# REPOSITORIES
#   - can be defined here or included from another file
#   - pacman will search repositories in the order defined here
#   - local/custom mirrors can be added here or in separate files
#   - repositories listed first will take precedence when packages
#     have identical names, regardless of version number
#   - URLs will have $repo replaced by the name of the current repo
#   - URLs will have $arch replaced by the name of the architecture
#
# Repository entries are of the format:
#       [repo-name]
#       Server = ServerName
#       Include = IncludePath
#
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
#

[core]
Include = /etc/pacman.d/mirrorlist

[extra]
Include = /etc/pacman.d/mirrorlist

[community]
Include = /etc/pacman.d/mirrorlist

# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.

[multilib]
Include = /etc/pacman.d/mirrorlist

# An example of a custom package repository.  See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs

The related changes are only in the Manjaro unstable branch so far. See:

1 Like

Never mind : I am on rolling. your note is for unstable
So it looks I dont need to worry I guess.

Are you sure pacman version in Arch wiki shown as 6.0.2.7 and I did what you send and i got this
sudo pacman -Syu “pacman>=6.0.2-11”  :heavy_check_mark:

:: Synchronizing package databases…
core is up to date
extra is up to date
community is up to date
multilib is up to date
error: target not found: pacman>=6.0.2-11

Does not compute.

Both Arch and Manjaro are rolling release distros.

Please see:

Your profile says you’re using the Manjaro stable branch. pacman 6.0.2-11 is only available in the unstable branch.

1 Like

I just got the standart Manjaro . I tought stable/rolling are same on Manjaro. When I look at the settings About section it shows rolling. I am happy with this for now. Just wanted to make sure I am not missing anything.

image

‘rolling’ is a style of distro … or rather package/update deployment.
Whichever branch of manjaro you use it will be ‘rolling’.

1 Like

That comes from /etc/os-release.

BUILD_ID=

A string uniquely identifying the system image originally used as the installation base. In most cases, VERSION_ID or IMAGE_ID+IMAGE_VERSION are updated when the entire system image is replaced during an update. BUILD_ID may be used in distributions where the original installation image version is important: VERSION_ID would change during incremental system updates, but BUILD_ID would not. This field is optional.

Examples: “BUILD_ID="2013-03-20.3"”, “BUILD_ID=201303203”.

os-release

Rolling release don’t use numbered versions like point releases do.

1 Like

definitely on stable

pacman-mirrors -G                                            1 ✘  6s  
stable

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