Upgrade to 22.04 from 21.12

Hello there,
as far as I understood, mabox is a rolling release, so that it should upgrade automatically – or am I wrong? At least my system stucks at 21.12. Do I have to upgrade kind of manually?
Thanks in advance
Carsten

1 Like

Those versions in rolling release model doesn’t mean to much - they used for ISO release.

Anyway, you should have 22.04 already after updating.
Just run:

yay

from terminal.

1 Like

Hi napcok,
executing “yay” results in some application updates, but not in an aupgrade of mabox. Here is the terminal output:

[sudo] Passwort für ceos: 
:: Paketdatenbanken werden synchronisiert …
 core ist aktuell
 extra                1879,7 KiB  4,83 MiB/s 00:00 [######################] 100%
 community               6,9 MiB  6,49 MiB/s 00:01 [######################] 100%
 multilib ist aktuell
:: Vollständige Systemaktualisierung wird gestartet …
Warnung: libcpuid: Lokale Version (0.5.1.r10.g7a580fd-1) ist neuer als community (0.5.1-2)
Warnung: paper-icon-theme-git: Lokale Version (832.aa3e8af7-1) ist neuer als community (746.04115106-1)
Warnung: python-pyqt5: Lokale Version (5.15.6-7.1) ist neuer als extra (5.15.6-7)
Abhängigkeiten werden aufgelöst …
Nach in Konflikt stehenden Paketen wird gesucht …

Pakete (5) firefox-99.0.1-1  firefox-i18n-de-99.0.1-1
           firefox-i18n-en-us-99.0.1-1  firefox-i18n-es-es-99.0.1-1
           firefox-i18n-pl-99.0.1-1

Gesamtgröße des Downloads:              64,52 MiB
Gesamtgröße der installierten Pakete:  233,69 MiB
Größendifferenz der Aktualisierung:     -0,19 MiB

:: Installation fortsetzen? [J/n] 
:: Pakete werden empfangen …
 firefox-99.0.1-1...    62,7 MiB  5,97 MiB/s 00:11 [######################] 100%
 firefox-i18n-pl-...   489,1 KiB  3,79 MiB/s 00:00 [######################] 100%
 firefox-i18n-de-...   485,8 KiB  3,74 MiB/s 00:00 [######################] 100%
 firefox-i18n-es-...   466,1 KiB  3,79 MiB/s 00:00 [######################] 100%
 firefox-i18n-en-...   424,5 KiB  3,67 MiB/s 00:00 [######################] 100%
 Gesamt (5/5)           64,5 MiB  5,80 MiB/s 00:11 [######################] 100%
(5/5) Schlüssel im Schlüsselbund werden geprüft    [######################] 100%
(5/5) Paket-Integrität wird überprüft              [######################] 100%
(5/5) Paket-Dateien werden geladen                 [######################] 100%
(5/5) Auf Dateikonflikte wird geprüft              [######################] 100%
(5/5) Verfügbarer Festplattenspeicher wird erm...  [######################] 100%
:: Pre-transaction-Hooks werden gestartet …
(1/1) Remove Firefox Distribution Settings
:: Paketänderungen werden verarbeitet …
(1/5) Aktualisiert wird firefox                    [######################] 100%
(2/5) Aktualisiert wird firefox-i18n-de            [######################] 100%
(3/5) Aktualisiert wird firefox-i18n-en-us         [######################] 100%
(4/5) Aktualisiert wird firefox-i18n-es-es         [######################] 100%
(5/5) Aktualisiert wird firefox-i18n-pl            [######################] 100%
:: Post-transaction-Hooks werden gestartet …
(1/4) Arming ConditionNeedsUpdate...
(2/4) Copy Firefox Distribution Settings
(3/4) Updating icon theme caches...
(4/4) Updating the desktop file MIME type cache...
:: Durchsuche Datenbanken für Updates...
:: Durchsuche AUR für Updates...
 -> libcpuid: local (0.5.1.r10.g7a580fd-1) is newer than community (0.5.1-2)
 -> paper-icon-theme-git: local (832.aa3e8af7-1) is newer than community (746.04115106-1)
 -> python-pyqt5: local (5.15.6-7.1) is newer than extra (5.15.6-7)
 -> python-pytz-deprecation-shim : lokal (0.1.0.post0-3) ist neuer als das AUR (0.1.0.post0-1)
 -> sardi-icons : lokal (21.10-03) ist neuer als das AUR (21.02-1)
 -> vertex-maia-icon-theme : lokal (20180118-1) ist neuer als das AUR (20160526-1)
 -> Fehlende AUR Pakete:  bashrc-mabox  cornora  linux512  linux512-virtualbox-host-modules  mabox-browser-settings  mabox-common  mabox-exo  mabox-gkrellm-themes  mabox-i18n-files  mabox-keyring  mabox-pcmanfm-actions  mabox-pipemenus  mabox-release  mabox-themes  mabox-themes-eithne  mabox-tools  mabox-wallpapers-2020  mb-jgtools  numix-circle-icon-theme  python2-pyxdg  vertex-maia-themes  yadsu
 -> Als nicht aktuell markierte AUR-Pakete:  cava
es gibt nichts zu tun

I`m not familiar enough to Linux to be able to see, what’s going wrong. Any idea would be highly appreciated :slight_smile:
Thanx
Carsten

1 Like

Looks like you don’t have Mabox repositories configured.
How this could happened?

Have you edited the /etc/pacman.conf file?

1 Like

Thank you for your quick response … No, I didn’t edit the file you mentioned. At least not as far as I know. in /etc there are three pacman.conf files:

  • pacman.conf
  • pacman-mirrors.conf
  • pacman-old.conf

pacman.conf:

#
# /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

# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg   =
#IgnoreGroup =

#NoUpgrade   =
#NoExtract   =

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

# 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

pacman-mirrors.conf

##
## /etc/pacman-mirrors.conf
##

## Branch Pacman should use (stable, testing, unstable)
Branch = stable

## Generation method
## 1) rank   - rank mirrors depending on their access time
## 2) random - randomly generate the output mirrorlist
# Method = rank

## Filename to use when ranking mirrors
## The file must be present in core repo
# TestFile = core.db.tar.gz

## Define protocols and priority
##   separated by comma 'https,http' or 'http,https'
## ATM available protocols are: http, https, ftp
## Not specifying a protocol will ban the protocol from being used
## If a mirror has more than one protocol defined only the first is written to the mirrorlist
## Empty means all in reversed alphabetic order
# Protocols =

## When set to False - all certificates are accepted.
## Use only if you fully trust all ssl-enabled mirrors.
# SSLVerify = True

pacman-old.conf

#
# /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 mabox-keyring
#XferCommand = /usr/bin/curl -C - -f %u > %o
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
#UseDelta    = 0.7
Architecture = auto

#IgnorePkg   =
#IgnorePkg   =
#IgnoreGroup =

#NoUpgrade   =
#NoExtract   =

# Misc options
#UseSyslog
Color
TotalDownload
# We cannot check disk space from within a chroot environment
CheckSpace
VerbosePkgLists

# 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.
#

# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.
[maboxlinux]
SigLevel = Optional TrustAll
Server = http://repo.maboxlinux.org/stable/$arch/


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

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

[community]
SigLevel = PackageRequired
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]
SigLevel = PackageRequired
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


1 Like

Your pacman.conf is the not the original provided by Mabox.
And was replaced probably by pacman.conf.pacnew during previous update - with your confirmation, it never happens automatically.
So remove it and replace with proper one.

sudo rm /etc/pacman.conf
sudo mv /etc/pacman-old.conf /etc/pacman.conf

Then get all updates, also from Mabox Linux repository:

yay
2 Likes

Thanks a lot – it works. I’m not shure, how and when I confirmed the replacement of the original conf-file… but probably you’re right and I overread something during an upgrade process…
Last question: After executing “yay” in the terminal ther was a warning, saying:

Warning: Configuration file /etc/pacman.conf, line 37: Directive "TotalDownload" in section "options" is not recognized.

Is there a blank space missing?

1 Like

…okay, obviuosly no blank space missing. But what is wrong in line 37?

1 Like

You can just comment it out with #.
I don’t remember what it means, but seems like it is not recognized by pacman anymore.

2 Likes