Pamac and AUR update

Support AUR
1

I’m a bit confused.

If I enter this in the terminal:

sudo pamac update --aur --devel

The output is (after prompting for password):
Warning: Building packages as dynamic user Warning: Setting build directory to /var/cache/pamac Preparing... Synchronizing package databases... Failed to synchronize AUR database Warning: plymouth: local (24.004.60-6) is newer than extra (22.02.122-18) Nothing to do. Transaction successfully finished.

But, if I open the pamac ui and run Refresh databases it seems to complete with no errors or warnings. (AUR is enabled.)

(Also, do I need to fix this warning?)
Warning: plymouth: local (24.004.60-6) is newer than extra (22.02.122-18)

2

Mantra mode:
Do not use sudo with pamac.

5 Likes
3

Manjaro Wiki - Using the Pamac CLI

Warning

Using sudo with pamac can have undesirable effects, especially when building packages. if in doubt, don’t use sudo. Pamac will ask for escalated rights if needed.

To refresh databases:

pamac update --aur --force-refresh

Warning: plymouth: local (24.004.60-6) is newer than extra (22.02.122-18)

System likely has plymouth-git from AUR that is newer than version available on Stable and Testing branches - plymouth - Branch compare for Manjaro

2 Likes
4

No. The message says plymouth and 24.004.60-6 isn’t a pkgver from a proper -git pkgbuild, playmouth-git have 24.004.60.r88.ga0e8b6cf-1 also pkgrel typically reset to 1 when building

This have been reported before Pamac and pacman disagree - #17 by Narsil (there is suggested that pamac access AUR, but plymounth isn’t there, is in Arch repo)

Likely plymouth 24.004.60-6 have been pushed to stable and then pulled

Can be fixed by downgrading to the currently available version with pacman -Syuu
better fix this otherwise you’ll miss updates or rebuilds until it catch up the version

4 Likes
5

Nicely picked up. I had also made the assumption in another thread that Plymouth from the AUR might have been installed. Now I know better.

I also just tried test building the plymouth-git package on my Testing branch system - the build failed due to missing Arch logos:

INFO: autodetecting backend as ninja
INFO: calculating backend command to run: /usr/bin/ninja -C /var/tmp/pamac-build-scotty/plymouth-git/src/build
Error reading file "/usr/share/pixmaps/archlinux-logo-text-dark.svg": Error opening file /usr/share/pixmaps/archlinux-logo-text-dark.svg: No such file or directory
==> ERROR: A failure occurred in build().
    Aborting...
6

So Manjaro users can’t install it out of the box

The pkgbuild convert /usr/share/pixmaps/archlinux-logo-text-dark.svg which is part of filesystem package

Anyway if you want to build you need to comment the line that start with rsvg-convert in build() and the one with install -Dm644 $srcdir/archlinux-logo-text-dark.png in package(), however I don’t know if it really need the png

1 Like
7

Indeed. The Manjaro filesystem package includes a Manjaro logo. :wink:

❯ pacman -Qo /usr/share/pixmaps/archlinux-logo-text-dark.svg
error: No package owns /usr/share/pixmaps/archlinux-logo-text-dark.svg
❯ pacman -Qo /usr/share/pixmaps/manjaro-logo-text-dark.png
/usr/share/pixmaps/manjaro-logo-text-dark.png is owned by filesystem 2024.11.25-2
2 Likes
8

Manjaro unstable branch contains the current plymouth package.

This version is by far better than the one in stable branch - at least for showing a nice LUKS decryption entry.

So switch to unstable branch instead of building from AUR (which is not recommended when on stable branch).

9

Sigh, I have managed very little other than to confuse the issue (at least for me) further.

I now have 2 Manjaro installs. One sees each update of a package from AUR, but throws the “plymouth local is newer” message.

The other the one (initially mentioned in this post). After running “pacman -Syuu” does not throw the plymouth message, but refuses to see any update in the AUR packages.

I have no idea when or how I got these two installs messed up.

10

pacman -Syuu to allow downgrade of packages is similar to pamac update --no-aur --allow-downgrade

11

pacman does not deal with AUR.
Not at all.

perhaps there is no problem to be found? :slightly_smiling_face:

the “local is newer than …” could come from switching branches to testing or unstable and then back to stable …

I don’t see a problem …

3 Likes
12

The problem is, I know there has been a update to the AUR package, since it has been applied to the other machine.

But, this machine, insists there is no AUR update.

13

Why do you think there is / should be one?

14

Which package? If you don’t remember then check /var/log/pacman.log

15

On the machine that has updated, the date on this one is 1/4/25:

upgraded freecad-git (1.1.0.39750.g7b548bee7f-1 -> 1.1.0.39757.ga974e413fa-

On the machine that hasn’t, the date on this one is 12/27/24:

upgraded freecad-git (1.1.0.39745.g6bb424b5d1-1 -> 1.1.0.39747.g7083362acb-1)

16 
pamac build freecad-git
17

Ok, that worked…but why did none of the update attempts pick it up?

18

Using sudo with pamac can have undesirable affects
and pacman does not support AUR packages

freecad is also available from Manjaro extra repository and as an Appimage

2 Likes
19

I see freecad mentioned – pacman -Ss freecad shows the following result from querying the official repository:

extra/freecad 1.0.0-1
    Feature based parametric 3D CAD modeler

I’ll drop this here for consideration;

After each system update it is generally considered good practice to rebuild any packages that you may have installed from the AUR.

pamac build <packagename>

Further to this, it is also recommended to always update from the official repositories before updating or rebuilding packages from the AUR.

Example:

sudo pacman -Syu
pamac update --aur

Or, as a combo:

sudo pacman -Syu && pamac update --aur

And lastly, the AUR is officially unsupported by Manjaro (or Arch); if you absolutely must use these packages, consider switching to the Unstable branch (which is generally closer to Arch Stable):

Regards.

1 Like