Why is the community repo missing?

Support
1

Rifled the wiki and the forums before posting. Please forgive me if my search skills failed me. The story: I noticed that the [community] package database has disappeared from the results I get when I enter . For example, this is the result when I enter <Sudo pacman -Syyu>:

[casuist@gilbert-hx90 ~]$ sudo pacman -Syyu
[sudo] password for casuist:
:: Synchronizing package databases…
core 144.7 KiB 362 KiB/s 00:00 [######################] 100%
extra 8.6 MiB 8.29 MiB/s 00:01 [######################] 100%
multilib 143.5 KiB 2.22 MiB/s 00:00 [######################] 100%
:: Starting full system upgrade…
there is nothing to do
[casuist@gilbert-hx90 ~]$

Formerly, and on my other three machines that run Manjaro, the community package database appears.

I tried refreshing my mirrorlist <user $ sudo pacman-mirrors -c Global> and downloading the databases and updating the system <user $ sudo pacman -Syu >. To no avail.

During one of my many search sessions, I discovered that my <pacman.conf> file was purged of any mention of “community”:

#
# /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
#UseDelta    = 0.7
Architecture = auto

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

#NoUpgrade   =
#NoExtract   =

# Misc options
#UseSyslog
#Color
#NoProgressBar
# We cannot check disk space from within a chroot environment
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.
#

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

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

[extra]
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

This language is missing for some reason:

#[community-testing]
#Include = /etc/pacman.d/mirrorlist

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

I have no clue how it ever got purged, or, more likely, how I ever managed to purge it.

What would be the recommended solution? Edit the pacman.conf file? Or, is there a command I can run to re-add or recover the repository?

2

The [community] repo has been deprecated for some time and should be removed.

This would have been shown through a pacnew.

Specifically /etc/pacman.conf.pacnew

You may print all your pacnews with

pacdiff -o

For the purposes here, of this single question …

Yes you remove the entry. If you want to be extra careful you can comment it out.

Then

sudo pacman -Sc

(yes to removing unused repos)

Then sync+upgrade again

sudo pacman -Syu
1 Like
3

Very grateful. Please forgive me for my ignorance.

4

No worries.

For more information on how to handle pacnews you can use the search here as there have been more than a few threads discussing how to manage them.


The fast and correct way, including my own opinions, would be

Ensure meld is installed

sudo pacman -Syu meld

Set the DIFFPROG environment variable

echo "DIFFPROG=/usr/bin/meld" | sudo tee -a /etc/environment

Source the environment file to be sure

source /etc/environment

Run pacdiff

pacdiff -s

Use ‘v’ to view, compare, edit, and merge new code.

(note the same file will be presented again after merge/save/close … if satisfied with the marge you can then ‘r’ for remove. Or just ‘s’ to skip … retaining the file for next pacdiff check, such as after a reboot)

The focus is to preserve configurations while adding in the new standards.

2 Likes
5

Always read Announcements posts. This happened back in May 2023 (Arch / Manjaro unstable) / July 2023 (Manjaro stable).

That was an Arch repo, not a Manjaro repo. Do not mix repos from different distros.

In 2023 after years of prior work the distribution migrated their back-end services to git and in the same run also switched to a new repository layout. In the new layout extra would contain all packages that were previously in community and the testing repositories were split from testing to core-testing and extra-testing , community-testing was removed entirely.

– Official repositories - ArchWiki

Note that I edited your topic title as it was erroneous and misleading.

1 Like
6

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