Failed retrieving file 'community.db'

Support
1

hi i am having the same issue and i am on stable release tree if any one have solve it please let me know

error:
failed retrieving file ‘community.db’ from ftp.snt.utwente.nl : The requested URL returned error: 404
failed retrieving file ‘community.db’ from ct.mirror.garr.it : The requested URL returned error: 404
error: failed retrieving file ‘community.db’ from mirrors.gigenet.com : The requested URL returned error: 404
error: failed retrieving file ‘community.db’ from ridgewireless.mm.fcix.net : The requested URL returned error: 404
error: failed retrieving file ‘community.db’ from mirror.xeonbd.com : The requested URL returned error: 404

thanks again for any help
regards omar

2

See here: Community Repository Error - #2 by linux-aarhus

2 Likes
3

Please edit your post and format the output properly.

Please also see:

2 Likes
5

The community repo doesn’t exist anymore.

Edit it out of /etc/pacman.conf or just generally tend to any .pacnew files in a timely fashion.
This one you have had for quite some time …

1 Like
6

see right there - in the replies to your other, essentially duplicate post
please don’t ask the same question twice

1 Like
7

Please see:

2 Likes
8

The contents of the community.db were merged into extra.db two years ago, and this was announced on one of the Stable Updates threads. This meant that from that moment on, community.db was empty, even though it still existed (without any content) on the mirrors.

About two months ago, community.db was removed from the mirrors, following the decision of Arch upstream to do the same with their own previously merged community.db. This too was announced on a Stable Updates thread.

As the quick & dirty solution to your problem, you should remove the following three lines from /etc/pacman.conf… :point_down:

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

However, the fact that you are running into this problem now suggests that you have not been maintaining your system. The change regarding community.db was reflected in a .pacnew file, and you are now running into this problem because you have not been merging your .pacnew files.

.pacnew files must not be ignored, nor must they be blindly copied over your existing configuration files. They are sample configuration files reflecting technical changes upstream, and they are meant to be merged with your existing configuration files.

You probably have loads of .pacnew files on your system by now. You can check this with the command… :point_down:

pacdiff -o

If you do not have that command at your disposal, then you must first install the package pacman-contrib.

Lastly, Manjaro is not a set-and-forget distribution. As a (curated) rolling-release distribution, it requires being kept up-to-date, as well as periodic hands-on maintenance, as explained in the essay below… :point_down:

Further reading regarding the community.db issue… :point_down:

Edit:

I had not seen this yet. I am going to close and unlist the other thread, given that it serves no purpose anymore and that the formatting of the terminal output is just plain horrible and makes it unreadable.

@a2apple, only one thread per issue, and one issue per thread. Please see the Forum Rules.

2 Likes
9

You can do this simply with the following commands in the terminal.

sudo cp /etc/pacman.conf /etc/pacman.conf.original
sudo cp /etc/pacman.conf.pacnew /etc/pacman.conf
sudo pacman-mirrors --fasttrack
sudo pacman -Syu
10

@admdb just copyng over pacnews over is a recipe for disaster. Do not teach obviously very inexperienced users to do that, because next time they will do it with .passwd for example!

2 Likes
11

That wipes out any changes made by the user.

.pacnew files should be merged properly, and this is an easy one which is good for cutting your teeth on.

3 Likes
17

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