In the core-testing Arch Linux repository, there is pacman v 7 , which currently conflicts with libpamac. This update really causes problems in pamac or just needs to upgrade the required version ?
That is correct. We know that.
Manjaro unstable does not import Arch Testing - so what is the problem?
What do you mean?
Yes I know it’s not a problem , just I use test repositories and added pacman in exceptions
Do you need to make additional changes to libpamac or update it as soon as the new pacman version is released in the stable branch of Arch Linux?
Just my curiosity, no more.
I know there is some changes to pacman 7, database and the extra files in the package, and there is also changes to makepkg as a consequense. I just skimmed the release notes for pacman 7 so that is what I remember 
Those will require changes in pamac and I am fairly certain @guinux has it covered.
3 Likes
dont worry, doesnt look like it is close to release, and might very well spend some more time as it is in arch-testing
2 Likes
FYI, I’ve moved this discussion to a new topic.
Most users should not be using them at all–let alone on Manjaro . See the Arch Wiki: Official_repositories: Testing repositories
Also, you may not submit Arch bug reports if you are not using Arch. See Arch bug reporting guidelines.
Yes, just as Arch already completed their rebuilds, I will also do the same with related packages in the Manjaro repos when the time comes.
2 Likes
Yes, I know that, but I didn’t send out reports of bugs related to the use of other repositories, just asked out of curiosity. If you are really bothered, I will stop asking such questions.
Love new software ) I know this article. Not experienced problems with this in ~ 5 years. After all, I take it as a recommendation, not a dogma. In any case I manage to use the repositories from three different distributions and not break anything
All the best.
1 Like
likewise, i have my share of small number of packages (firefox, nss, libreoffice, darktable, etc.) that i dont mind testing as soon as it is available in arch-testing. atleast to date the way i see it, they will only bring themselves down in case they fail. and most of the time i can safely downgrade the sole package to get things working again.
however pacman ain’t one of them by a long shot. i messed-up real bad once and to this date only consider myself extremely lucky that i was able to recover from total non-functional pacman. with the main package manager gone, the whole installation is good as gone making anything got to do with package manipulation totally non-functional. it applies to all pacman dependencies and all dependencies of such crucial packages likewise. (in my case i was experimenting with icu in arch-testing for a bug fix to one of my other projects, which rendered pacman non-functional).
i know i might be patronizing here, nevertheless be very weary of this habit if you value your setup as much
2 Likes
I’m not bothered at all. Note that my response is also for others coming across this topic. 
That’s fine, just keep in mind doing so is not officially supported.
2 Likes
I’m now facing a similar issue on Manjaro Testing, where I get the following message when updating:
pacman-git-7.0.0.r6.g7bc5d55b-1.1 and pacman-6.1.0-7 are in conflict. Remove pacman? [y/N] ```You don’t have a similar issue. You have an AUR package that confilicts with the repo package. Just delete the AUR package.
1 Like
Pacman 7 is now in the Manjaro Unstable branch and Pamac related packages have been rebuilt on the new library.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.