I get the same error but for octopi:
unable to satisfy dependency ‘pacman<5.3’ required by octopi
For those users who cannot live without pamac, there is an AUR package with the old libalpm12:
https://aur.archlinux.org/packages/libalpm12/
edit:
Same with packagekit and pacutils, both built by @oberon
seems that pacman 6 needs rebuild of yay and octopi 0.11.0-2 with alpm-octopi-utils 1.0.2-3
I like Octopi more than Pamac.
But do we need some rebuilds for the Octopi? What is the root of the idea that Octopi is ready for pacman 6?
There are still commits for pacman 6 support: Commits · aarnt/octopi · GitHub
but lastest release was
#### [v0.11.0 ]
* on Jan 11
It looks like that we have to remove Octopi for now to install pacman 6
Because AUR Helpers not ready for pacman 6 yet
I got both pacman 6.0 and pamac working. Looks like pamac was rebuilt today to give support for pacman 6.0. Thanks @philm for that!
This is what I did to get them working back again:
- Uninstalled pamac and dependencies (including layouts-switcher and manjaro-hello)
- Updated with pacman. At this point I got pacman upgraded. Yay!
- Installed pamac-cli 10.1.3-1 and dependencies. You get some warnings regarding your configuration and how to enable the desktop integration.
That should be it. Enjoy! 
I ignored updates of “pacman”, “pacutils”, “pamac-cli”, “pamac-common”, “pamac-gtk” and “yay”. Do the others updates. Later I will see this…
the Pamac problems seems to be fixed now
1 Like
I also ignored (and then removed) pamac and all its dependencies in order to update. I merged the pacman.pacnew and uncommented the new parallel download function, and the download speed increase is palpable. Paru AUR-helper works with pacman 6, but I’m unable to re-install pamac at this time due to dependency conflicts.
EDIT: After pacman-mirrors refresh and then new update, I am able to re-install pamac, so all is well.
Yep, I think so. Even updating directly from pamac without workarounds should work right now.
Should I remove “packagekit” and “packagekit-qt”?
error: failed to prepare transaction (could not satisfy dependencies)
:: installing pacman (6.0.0-1) breaks the “pacman<5.3” dependency required by packagekit
When trying to update today’s updates from unstable repo, I got (freely translated):
error: couldn't commit transaction (can't resolve dependency)
:: pacman installation (6.0.0-1) will break dependency 'pacman<5.3' required by packagekit
I guess packagekit update that would require pacman 6 dependency is not yet synced in unstable repo? Or maybe is this some kind of omission?
1 Like
After refresh, the pacman conflict is gone. Thank you 
.
1 Like
No more package pamac-common?
wine broke for me with todays update, anyone else had the same?
It’s been replaced by libpamac.
1 Like
Got help from @Strit Multilib got disabled in pacman.conf during the update from pacman 6 from pacman 5 but fixed it now again thanks
1 Like
Updating manjaro -system today, I get (partial sample of log:)
Upgrading manjaro-system (20210523-1 -> 20210612-1)...
==> Security fix: recreating gnupg keys for pacman
All systems before 21.0.6 release shipped common private keys for pacman!
This might take a while to complete ...gpg: /etc/pacman.d/gnupg/trustdb.gpg: trustdb created
gpg: no ultimately trusted keys found
gpg: starting migration from earlier GnuPG versions
gpg: porting secret keys from '/etc/pacman.d/gnupg/secring.gpg' to gpg-agent
gpg: migration succeeded
==> Generating pacman master key. This may take some time.
gpg: Generating pacman keyring master key...
gpg: key A4B28660A9E43C29 marked as ultimately trusted
gpg: directory '/etc/pacman.d/gnupg/openpgp-revocs.d' created
gpg: revocation certificate stored as '/etc/pacman.d/gnupg/openpgp-revocs.d/635ED7E4AB9EC962B0095E6CA4B28660A9E43C29.rev'
gpg: Done
==> Updating trust database...
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
==> Appending keys from archlinux.gpg...
==> Appending keys from manjaro.gpg...
==> Locally signing trusted keys in keyring...
gpg: checking the trustdb
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
Is this okay or do I have an issue here?
Just a heads up:
==> Security fix: recreating gnupg keys for pacman
All systems before 21.0.6 release shipped common private keys for pacman!
This might take a while to complete ...gpg: /etc/pacman.d/gnupg/trustdb.gpg: trust-db erzeugt
see
3 Likes