Pamac - 'extra' packages shown in AUR

HI,

I encounter today a strange up date on a device, some extra packages are on aur !

pacman up date details

[nls@h3 ~]$ sudo pacman -Syu
[sudo] password for nls: 
:: Synchronising package databases...
 core                                                                    150,3 KiB  2,19 MiB/s 00:00 [############################################################] 100%
 extra                                                                     8,7 MiB  34,7 MiB/s 00:00 [############################################################] 100%
 community                                                                29,0   B  2,83 KiB/s 00:00 [############################################################] 100%
 multilib                                                                143,8 KiB  14,0 MiB/s 00:00 [############################################################] 100%
:: Starting full system upgrade...
 there is nothing to do

[nls@h3 ~]$ sudo pamac update -a

Warning: Building packages as dynamic user
Warning: Setting build directory to /var/cache/pamac
Preparing...
Synchronizing package databases...
Cloning ckbcomp build files...
Running as unit: run-u123.service
fatal: not a git repository (or any parent up to mount point /var/cache/private)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Finished with result: exit-code
Main processes terminated with: code=exited/status=128
Service runtime: 7ms
CPU time consumed: 6ms
Memory peak: 608.0K
Memory swap peak: 0B
Running as unit: run-u124.service
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 9ms
CPU time consumed: 7ms
Memory peak: 524.0K
Memory swap peak: 0B
Running as unit: run-u125.service
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 327ms
CPU time consumed: 83ms
Memory peak: 1.5M
Memory swap peak: 0B
Generating ckbcomp information...
Running as unit: run-u126.service
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 1.126s
CPU time consumed: 1.237s
Memory peak: 1.1M
Memory swap peak: 0B
Checking ckbcomp dependencies...
Cloning pamac-tray-icon-plasma build files...
Running as unit: run-u127.service
fatal: not a git repository (or any parent up to mount point /var/cache/private)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Finished with result: exit-code
Main processes terminated with: code=exited/status=128
Service runtime: 6ms
CPU time consumed: 6ms
Memory peak: 612.0K
Memory swap peak: 0B
Running as unit: run-u128.service
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 15ms
CPU time consumed: 9ms
Memory peak: 608.0K
Memory swap peak: 0B
Running as unit: run-u129.service
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 313ms
CPU time consumed: 62ms
Memory peak: 1.5M
Memory swap peak: 0B
Generating pamac-tray-icon-plasma information...
Running as unit: run-u130.service
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 1.603s
CPU time consumed: 1.773s
Memory peak: 1.3M
Memory swap peak: 0B
Checking pamac-tray-icon-plasma dependencies...
Cloning electron25 build files...
Running as unit: run-u131.service
fatal: not a git repository (or any parent up to mount point /var/cache/private)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Finished with result: exit-code
Main processes terminated with: code=exited/status=128
Service runtime: 6ms
CPU time consumed: 6ms
Memory peak: 608.0K
Memory swap peak: 0B
Running as unit: run-u132.service
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 10ms
CPU time consumed: 7ms
Memory peak: 608.0K
Memory swap peak: 0B
Running as unit: run-u133.service
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 360ms
CPU time consumed: 77ms
Memory peak: 1.5M
Memory swap peak: 0B
Generating electron25 information...
Running as unit: run-u134.service
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 2.415s
CPU time consumed: 2.594s
Memory peak: 1.0M
Memory swap peak: 0B
Checking electron25 dependencies...
Cloning libpamac build files...
Running as unit: run-u135.service
fatal: not a git repository (or any parent up to mount point /var/cache/private)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Finished with result: exit-code
Main processes terminated with: code=exited/status=128
Service runtime: 8ms
CPU time consumed: 7ms
Memory peak: 608.0K
Memory swap peak: 0B
Running as unit: run-u136.service
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 13ms
CPU time consumed: 8ms
Memory peak: 824.0K
Memory swap peak: 0B
Running as unit: run-u137.service
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 333ms
CPU time consumed: 87ms
Memory peak: 1.5M
Memory swap peak: 0B
Generating libpamac information...
Running as unit: run-u138.service
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 5.894s
CPU time consumed: 6.489s
Memory peak: 1.1M
Memory swap peak: 0B
Checking libpamac dependencies...
Cloning v86d build files...
Running as unit: run-u139.service
fatal: not a git repository (or any parent up to mount point /var/cache/private)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Finished with result: exit-code
Main processes terminated with: code=exited/status=128
Service runtime: 6ms
CPU time consumed: 6ms
Memory peak: 396.0K
Memory swap peak: 0B
Running as unit: run-u140.service; invocation ID: 18d16503bdde41199fb99c9d51fc66f4
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 10ms
CPU time consumed: 8ms
Memory peak: 256.0K
Memory swap peak: 0B
Running as unit: run-u141.service
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 313ms
CPU time consumed: 78ms
Memory peak: 1.1M
Memory swap peak: 0B
Generating v86d information...
Running as unit: run-u142.service
Finished with result: success
Main processes terminated with: code=exited/status=0
Service runtime: 2.412s
CPU time consumed: 2.677s
Memory peak: 1.0M
Memory swap peak: 0B
Checking v86d dependencies...
Checking pacman-git dependencies...
Checking pamac-classic dependencies...
Checking pamac-all-git dependencies...
Checking pamac-all dependencies...
Checking pamac-aur dependencies...
Checking pamac-aur-git dependencies...
Checking pamac-nosnap dependencies...
Checking libpamac-full dependencies...
Checking libpamac-aur dependencies...
Checking libpamac-git dependencies...
Checking libpamac-nosnap dependencies...
Error: Failed to prepare transaction: invalid or corrupted database



Edit build files : [e] 
Apply transaction ? [e/y/N] y

Transaction cancelled.
[nls@h3 ~]$ git init
hint: Using 'master' as the name for the initial branch. This default branch name
hint: is subject to change. To configure the initial branch name to use in all
hint: of your new repositories, which will suppress this warning, call:
hint: 
hint:   git config --global init.defaultBranch <name>
hint: 
hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and
hint: 'development'. The just-created branch can be renamed via this command:
hint: 
hint:   git branch -m <name>
Initialized empty Git repository in /home/nls/.git/
[nls@h3 ~]$ 

pamac up date details

# Maintainer: WhitedonSAP <ayrtonarantes0987654321ayrt008 at gmail dot com> 

pkgname=libpamac
pkgver=11.6.4
pkgrel=1
pkgdesc="Library for Pamac package manager based on libalpm"
arch=('i686' 'pentium4' 'x86_64' 'arm' 'armv6h' 'armv7h' 'aarch64')
url="https://gitlab.manjaro.org/applications/libpamac"
license=('GPL3')
depends=('pacman-git' 'appstream-glib' 'polkit' 'archlinux-appstream-data')
makedepends=('gettext' 'itstool' 'vala' 'meson' 'ninja' 'gobject-introspection' 'xorgproto' 'asciidoc')
options=(!emptydirs)
conflicts=('libpamac-aur' 'libpamac-full')
source=(https://gitlab.manjaro.org/applications/libpamac/-/archive/$pkgver/libpamac-$pkgver.tar.bz2)
sha256sums=('4ac54679e25004d6af8154340bac2e060c3a109a6bcb336f54ce025b2d68f080')

build() {
  cd $pkgname-$pkgver
  mkdir -p builddir
  cd builddir
  meson setup --prefix=/usr --sysconfdir=/etc --buildtype=release
  # build
  ninja
}

package() {
  backup=('etc/pamac.conf')
  cd $pkgname-$pkgver
  cd builddir
  DESTDIR="$pkgdir" ninja install
}

# Maintainer: Nissar Chababy <funilrys at outlook dot com>
# Ex-Maintainer: 	Jeroen Bollen <jbinero at gmail dot comau>

pkgname=ckbcomp
pkgver=1.221
pkgrel=1
pkgdesc="Compile a XKB keyboard description to a keymap suitable for loadkeys or kbdcontrol"
arch=(any)
url="http://anonscm.debian.org/cgit/d-i/console-setup.git/"
license=('GPL2')
depends=('perl')
source=("http://ftp.debian.org/debian/pool/main/c/console-setup/console-setup_${pkgver}.tar.xz")
sha512sums=('083dcf8bb5b96f7e4d659df454355dd48ef85b49e08136570fa6ec270b61ef6aa46d54cd416a720a7abd1d524b100bc73230dc9edd20f6dd0c8be6f214b54aff')
conflicts=(ckbcomp-bin)

package() {
    if [[ -d "${srcdir}/console-setup" ]]
    then
        cd console-setup
    elif [[ -d "${srcdir}/console-setup-${pkgver}" ]]
    then 
        cd console-setup-${pkgver} 
    else
	echo "Source directory not found.".
	exit 1
    fi


    if [[ ${?} != 0 ]]
    then
        cd console-setup-${pkgver}
    fi

    install -d ${pkgdir}/usr/bin/
    install -m755 Keyboard/ckbcomp ${pkgdir}/usr/bin/
}

Thanks for your help.

This happens naturally when some packages are discontinued.

But if you are referring to the pamac ones … they have always been there … and this duplication of package names (in repos and aur) has been a source of problems in the past. I might expect it to continue to be.

1 Like

Manjaro extra package libpamac has not been updated to 11.1.6.4-1 yet
Manjaro Gitlab shows libpamac 11.1.6.4 created Mar 11, 2024 6:41pm UTC

Extra package pamac-tray-icon-plasma has not been updated to 0.1.3-3 yet
but no new version has been created pamac-tray-icon-plasma · GitLab

Pamac packages in AUR are maintained by and for users of other Arch-based distributions

I suggest uncheck updates for these AUR packages

1 Like

Thanks for your reply,

Really strange issue, now google chrome from aur is present for up date but same issue, can’t update this package.

edit 1 :I found something on the forum

[nls@h3 ~]$ pamac update --force-refresh
Preparing...
Synchronizing package databases...
Refreshing core.db...                                                                                                                                                   
Refreshing extra.db...                                                                                                                                                  
Refreshing community.db...                                                                                                                                              
Refreshing multilib.db...                                                                                                                                               
Refreshing core.files...                                                                                                                                                
Refreshing extra.files...                                                                                                                                               
Refreshing community.files...                                                                                                                                           
Refreshing multilib.files...                                                                                                                                            
Refreshing AUR...                                                                                                                                                       
Checking google-chrome dependencies...                                                                                                                                  
Resolving dependencies...
Checking inter-conflicts...

To build (1):
  google-chrome  122.0.6261.128-1  (122.0.6261.111-1)  AUR


Edit build files : [e] 
Apply transaction ? [e/y/N] y

Cloning google-chrome build files...
Generating google-chrome information...
==== AUTHENTICATING FOR org.manjaro.pamac.commit ====
Authentication is required to install, update, or remove packages
Authenticating as: nls
Password: 
==== AUTHENTICATION COMPLETE ====

Building google-chrome...
==> Making package: google-chrome 122.0.6261.128-1 (mer. 13 mars 2024 03:24:28)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading google-chrome-stable_122.0.6261.128-1_amd64.deb...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  101M  100  101M    0     0   100M      0  0:00:01  0:00:01 --:--:--  100M
  -> Found eula_text.html
  -> Found google-chrome-stable.sh
==> Validating source files with sha512sums...
    google-chrome-stable_122.0.6261.128-1_amd64.deb ... Passed
    eula_text.html ... Passed
    google-chrome-stable.sh ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting google-chrome-stable_122.0.6261.128-1_amd64.deb with bsdtar
==> Entering fakeroot environment...
==> Starting package()...
==> Tidying install...
  -> Removing empty directories...
  -> Removing libtool files...
  -> Purging unwanted files...
  -> Removing static library files...
  -> Compressing man and info pages...
==> Checking for packaging issues...
==> Creating package "google-chrome"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Adding install file...
  -> Generating .MTREE file...
  -> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: google-chrome 122.0.6261.128-1 (mer. 13 mars 2024 03:24:40)
==> Cleaning up...

Checking keyring...                                                                                                                                                [1/1]
Checking integrity...                                                                                                                                              [1/1]
Loading package files...                                                                                                                                           [1/1]
Checking file conflicts...                                                                                                                                         [1/1]
Checking available disc space...                                                                                                                                   [1/1]
==> skipping timeshift-autosnap due skipRsyncAutosnap in /etc/timeshift-autosnap.conf set to TRUE.
Upgrading google-chrome (122.0.6261.111-1 -> 122.0.6261.128-1)...                                                                                                  [1/1]
Running post-transaction hooks...
Arming ConditionNeedsUpdate...                                                                                                                                     [1/4]
Refreshing PackageKit...                                                                                                                                           [2/4]
Updating icon theme caches...                                                                                                                                      [3/4]
Updating the desktop file MIME type cache...                                                                                                                       [4/4]
Transaction successfully finished.
[nls@h3 ~]$ 

The issue is solve, pacman and pamac are now ok, nice

[nls@h3 ~]$ sudo pamac update -a
[sudo] password for nls: 
Warning: Building packages as dynamic user
Warning: Setting build directory to /var/cache/pamac
Preparing...
Synchronizing package databases...
Refreshing AUR...                                                                                                                                                       
Nothing to do.                                                                                                                                                          
Transaction successfully finished.
[nls@h3 ~]$ 

These indicate you have problems with your system in general.
The community repo was discontinued a long time ago.
This probably means you have unmanaged pacnews.
To print them all you can do:

pacdiff -o
2 Likes
[nls@h3 ~]$ pacdiff -o
bash: pacdiff: command not found

see you later,I have t go

tend to your .pacnew files in /etc
via pacdiff or any other way

1 Like

I guess you dont have pacman-contrib then.

1 Like

My partner has google-chrome and sometimes pamac would not find update until I use

pamac build google-chrome
1 Like

Additionally, you seem to have unrelated issues: The community repo hasn’t existed for some time, and should have been removed; there was a specific pacnew file a few months ago which you should have compared/merged to correct that.

See System Maintenance in the Manjaro Wiki, and scroll down to the section titled Pacnew and Pacsave files for general information. To find a reference to a specific pacnew file, you should search through the Stable Announcements until you find it. Cheers.

1 Like

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.