Community Repository Error

[nikgnomic]

@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 automation in this case is not possible for whatever reason, then so be it – that’s exactly my point). And if it would be possible to automate it, well, even then, of course, it is totally up to the Manjaro maintainers to choose not to implement such a solution

Manjaro maintainers will not intervene on a system maintenance issue
“your system under your control”
but they do provide tools and information to help users maintain their systems

System Maintenance - Manjaro Wiki
This article contains tips and best practices for keeping your system in optimal condition.

Manjaro forum has many warnings and information about merging pacnew files.
First post in update announcements may have a warning if a .pacnew may cause a critical issue (but package manager failing to synchronise with a defunct repo is not critical and simple to fix)

2nd post Known issues and solutions in update announcements has a general warning

@philm

Please RTFT (Read This Fine Thread) first before reporting the same issues over and over again!

Note: Do not forget to review your .pacnew files:

• System Maintenance - Manjaro
• Check and manage pacnew files

There are also many previous forum posts over the last 2 years where users have spotted a package manager syncing to defunct community repository. And other posts were new users asked about managing other .pacnew files