However we can notice an increase recently of this specific issue, many users seems to have been impacted.
Maybe worth having some Manjaro team members think of a possible cause of this issue, if multiple people at around the same time have the same issue, something is going on.
//EDIT: maybe something to look at, two weeks ago multiple mirrors seemed to have had a rollback of many packages suddenly, after investigating I found that they have their repo databases with different packages version than what they contain… so this may be something to investigate. Currently one mirror still has this issue, the manjaro.re mirror. Maybe more mirrors still have the issue but for now I switch to the Global mirror to stop being bothered by the issue.
I didn’t say pamac was corrupting any packages, I said pamac was corrupting the database. (See the error message.) It seems to be a problem with the signatures. Turning off signature checking solves the problem, but that is not really the solution we want.
The thing is - there is no signatures for the databases.
I have been troubleshooting this issue some time ago and as I recall it the issue manifest when curl receives a 200 OK when downloading a database which in reality is a html document e.g. a custom error 404 document.
I recall this change being old, and don’t recall a recent pacman.conf.pacnew, I may be wrong though and may not remember well (I check .pacnew at every update).
I use mirrors from the US and it’s been a week or so but I had an issue with pamac where I couldn’t update so I switched the mirrors to worldwide and updated with no issues.After a reboot I changed the mirrors back to the US and have had no issues since.My pacman.conf has the SigLevel = Required DatabaseOptional as that was a change a few months ago.
I had similar problems. I am running RebornOS with pamac 10.3.0-1. Turned out I didn’t manually run, Refresh databases from the hamburger menu in pamac, so I kept seeing the same error in pamac.
sudo pacman -Syyu was working, but pamac wasn’t until I manually ran Refresh databases.