#Trying to update system with pamac, fails.
$ pamac update
[sudo] password for rabcor:
Preparing...
Synchronizing package databases...
unable to lock database
Failed to synchronize databases
Nothing to do.
Transaction successfully finished.
#Trying to update system with pacman, succeeds
$ pacman -Syu
:: Synchronising package databases...
core 165,9 KiB 178 KiB/s 00:01 [###################################################] 100%
extra 1849,4 KiB 3,11 MiB/s 00:01 [###################################################] 100%
community 7,1 MiB 6,15 MiB/s 00:01 [###################################################] 100%
multilib 180,6 KiB 2,32 MiB/s 00:00 [###################################################] 100%
home_justkidding_arch_Arch 30,4 KiB 48,3 KiB/s 00:01 [###################################################] 100%
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
#Trying to update system with pamac again, it still fails to update database but because pacman already did it it can now update
$ pamac update
Preparing...
Synchronizing package databases...
unable to lock database
Failed to synchronize databases
Resolving dependencies...
Checking inter-conflicts...
Why does manjaro not just stick with pacman out of the box?
And is there any downside if I use pacman instead of pamac for installing/updating packages or the system?
That’s not related to pamac, your pacman database is locked as something else is using it.
Obviously this isn’t the case, if it was pacman couldn’t update either (even if there was a duplicate instance of pacman running in the background somewhere that was using it and i forgot about it, that would stop pacman from updating just as surely as pamac, this can only really be a pamac issue)
Hell, let me show you:
$ ls /var/lib/pacman/
local sync
$ pamac update
Preparing...
Synchronizing package databases...
unable to lock database
Failed to synchronize databases
Nothing to do.
Transaction successfully finished.
As you can see db.lock doesn’t exit, but pamac still fails to update the database. (And like I explained, if it did it would have stopped pacman too, not just pamac)
By we I meant manjaro users, manjaro wiki seems to want users to use pamac rather than pacman most of the time, but you have answered my question to satisfaction.
I don’t want flatpak or snap, and I use yay for AUR.
As for why Pamac fails, I don’t care enough to actually troubleshoot it since I prefer pacman in the first place (which is why it’s posted in non-technical)
For me, the main appeal of pamac is its more user-friendly syntax. Coming from Ubuntu or Fedora, pamac install, pamac build, pamac update, etc. is much easier than pacman -Ejloo289sao;ig (obviously jk, but still, it’s not convenient to have to hold down shift to type -S, why, just why?)
Apologies for the rant.
Ah, /var/tmp/pamac/dbs/ had a db.lock, thanks for solving that mystery.
As for using what I like, I actually use all of these. pamac only really gets used to do system updates though (because i get tray notifications about system updates from it, and the instinct is to click on 'em)
But WhiteCzar’s explanation for the appeal in pamac is pretty cool too. I can see where he’s coming from.
Well, I guess it’s logical, but don’t you think it’s a bit inconvenient? Maybe it’s just me, but I’d prefer to use as little capital letters as possible in a terminal. Isn’t that why all the system folders in Linux use all-lowercase?
You’re free to use whichever you’d like.
(which is why it’s posted in non-technical)