Pamac bug report

Support Software & Applications
1

I don’t have a gitlab account, but this is obviously a bug in pamac.

Based on much feedback from users, when the community repo fails to sync because it no longer exists, pamac does not sync the multilib repo, then it tries to calculate the update anyway. Old versions of packages in multilib conflict with new versions of packages in core and extra. Pamac tries to solve this by removing conflicting packages, but many other packages depend on them. The update fails when pamac cannot resolve package conflicts. This shouldn’t happen because the update should fail as soon as a repo fails to sync.

I have seen so many posts about this in the forum, and the problem always boils down to the fact that they didn’t remove community from their pacman.conf. They completely miss the warning that community failed to sync and only ask about the warning that pamac failed to remove conflicting packages.

5 Likes
2

Would this not also happen with pacman?

… you can’t force people to read - it would be nice if they did, though - or would include the whole output in their query

It boils down to system maintenance - taking care of .pacnew files …

3

No, pacman correctly stops trying to update when a repo cannot sync.

4 Likes
4

Aha - then this is a bug indeed.

I have never been in that situation - I only use pacman - and yay when needed.
And I read the messages and notice .pacnew files and tend to them.

5

pamac source and bugtracker is on GitHub - manjaro/pamac: Graphical Package Manager for Manjaro Linux with Alpm, AUR, Appstream, Flatpak and Snap support

6

I have never encountered it either, and I do use pamac UI deliberately, but that maybe because apparently I read everything.

But yes based on my understanding of how pamac works I think @ben75 has a point.

3 Likes