This morning all my Manjaro machines have an error with regards to the Community repo as follows; error: failed retrieving file 'community.db' from manjaro.kurdy.org : The requested URL returned error: 404 error: failed retrieving file 'community.db' from mirror.easyname.at : The requested URL retu…

A long time ago all packages was moved from community to extra repo. You should edit your /etc/pacman.conf and remove the community repo reference. [image] Update - error: failed retrieving file 'community.db' Notices Long time ago the community packages was …

With all due respect, [image] tdussa: a breaking change should NEVER occur This wasn’t a breaking change until the user, the administrator, the person responsible for the computer, did not do proper maintenance, like is expected. Do you do maintenance on your car? If you don’t have one, you…

I totally agree with @tdussa . This is not a car, it does not require pieces replacement. It is a bad comparison, from my point of view. I don’t think that the comments from @tdussa are destructive, but constructive. I think that people should want to do things better each time, enhancing the debili…

[image] jlink: it does not require pieces replacement Not physical pieces, or parts, no. But maintenance, none the less.

[image] nikgnomic: A .pacnew file is created during an update if changes are required for a system configuration file that has been modified from default, instead of over-writing the file with default settings Merging .pacnew files is part of the update process that must be managed by user to e…

[image] tdussa: My question stands: In this particular case, what is the showstopper that does not allow for an automatic removal/commenting out the references to the community repo entries in the pacman config file? It is the policy and procedure that NO updates should ever touch system conf…

[image] jlink: I am now sure that I will search for a different linux distribution, focused to easy my work, and not to get stalled in the past. I really thought that this was not the target. Perhaps I was wrong. That’s fine. Rolling releases require active maintenance by system administrator…

[image] Algo: there are entries for a pacman.conf.pacnew from for example January, February and October 2024 among a long list of “running pacnew-checker.hook” messages and other pacnew files. pacnew-checker should alert user when a .pacnew file is created so user can either: compare files …

I’m not a beginner user, of course not (many years working in Linux, different distributions). The issue is not being a beginner, nor that there has been a one-off failure. The issue is the attitude that is shown to hear users and try to become better and better, which has been shown to me to be a …

[image] tdussa: So far, I haven’t seen a good argument why this particular change could not have been automated, just a lot of fingerpointing and telling me that I’m doing a bad job administrating my systems It probably could have, but there’s a system in place to prevent breakage. Maintenan…

[image] tdussa: People keep saying that it’s all my fault that I tripped over this because I failed to do proper sys maintenance, and I do not deny that, of course I could have avoided the issue. However, IMHO it is good system design to automate as much as possible (note that this means that if…

Community Repository Error

Support System Updates

scotty65 4 March 2025 08:48 31

That’s fine. Rolling releases require active maintenance by system administrators, and not every user wants to, or is able to, spend 5 or so minutes of their time each month doing that.