Pamac upgrade fails due to one AUR package

For a while pamac upgrade fails, because one AUR package (dropbox) has a compilation error. How could I still update the other packages until the error is solved?

Also a somehow related question: how could I update a single package (and its dependencies)?

You dont, unless you are trying for a partial-upgrade which is the same thing as broken.

On the other hand … pamac defaults to upgrading the AUR as well as regular packages, which should not be necessary unless you really mucked up the system with it heavily relying on core components provided from the AUR.

So, a normal system upgrade using pacman would not include that and should be safe…

sudo pacman -Syu

Though … your dropbox compilation(?) error is likely fixable as well.

1 Like

I hope the dropbox issue will be fixable, though I tried to solve the issue maybe the 5th time in the last month. None seemed to work, and the error message is short, and now makes no sense to me. (PGP error, but dropbox’s key is imported)

Somewhere it makes sense what you wrote, but the fragility of this system is frightening. In my case I am confident that dropbox won’t break anything else.

Where should I look for the meaning the switches after the pamac command you wrote? It is written in many sites, what the combination should be used, but nothing more. It is not in the manual (man pamac), not in Manjaro wiki, and found little info by searching for it. I have a guess, what u and y is standing for, but it is unsettling feeling that I do not know where to look for such information.

It is not true … well sort of true …

I think you do not realize pamac and pacman are 2 different things.

man pacman


       -S, --sync
           Synchronize packages. Packages are installed directly from the
           remote repositories, including all dependencies required to run the
           packages. For example, pacman -S qt will download and install qt
           and all the packages it depends on. If a package name exists in
           more than one repository, the repository can be explicitly
           specified to clarify the package to install: pacman -S testing/qt.
           You can also specify version requirements: pacman -S "bash>=3.2".
           Quotes are needed, otherwise the shell interprets ">" as
           redirection to a file.

           In addition to packages, groups can be specified as well. For
           example, if gnome is a defined package group, then pacman -S gnome
           will provide a prompt allowing you to select which packages to
           install from a numbered list. The package selection is specified
           using a space- and/or comma-separated list of package numbers.
           Sequential packages may be selected by specifying the first and
           last package numbers separated by a hyphen (-). Excluding packages
           is achieved by prefixing a number or range of numbers with a caret


       -y, --refresh
           Download a fresh copy of the master package database from the
           server(s) defined in pacman.conf(5). This should typically be used
           each time you use --sysupgrade or -u. Passing two --refresh or -y
           flags will force a refresh of all package databases, even if they
           appear to be up-to-date.


       -u, --sysupgrade
           Upgrades all packages that are out-of-date. Each
           currently-installed package will be examined and upgraded if a
           newer package exists. A report of all packages to upgrade will be
           presented, and the operation will not proceed without user
           confirmation. Dependencies are automatically resolved at this level
           and will be installed/upgraded if necessary.

           Pass this option twice to enable package downgrades; in this case,
           pacman will select sync packages whose versions do not match with
           the local versions. This can be useful when the user switches from
           a testing repository to a stable one.

           Additional targets can also be specified manually, so that -Su foo
           will do a system upgrade and install/upgrade the "foo" package in
           the same operation.


You can unselect all and then select the one program you want to upgrade.

You can also just unselect the AUR program you don’t want to upgrade and then upgrade the rest and come back to the AUR program after. It is as simple as clicking the green check mark.

I’ve never used the GUI before. I will check it out. Thanks!

That could be the case… It is so easy to misread one, if the other name appeared just before.
When I moved to Manjaro, I read somewhere that I should not use pacman directly, but through pamac. Maybe that’s why I have not noticed the difference. Sorry.

The Manjaro wiki contains an overview for beginners on how to use pacman in the terminal. pacman is the package manager from upstream Arch Linux.

:link: Pacman Overview - Manjaro

Furthermore, the Manjaro wiki contains an overview of pamac (also called Add/Remove software). pamac is the default package manager of Manjaro. pamac can be used in two ways: as a graphical user interface (Pamac GUI) or as a command line interface (Pamac CLI).

:link: Pamac - Manjaro