Aur package that I didn't install shows up in my updates


I hope someone can help me shed some light on the following. Every couple of days I install the latest updates with the command yay. Today at the end of the update there was a “weird” aur package “aur/libkipi” that I didn’t install myself. This if the first time that happened, before it only ever showed package I installed myself.

So I was wondering where does this package come from? Is it maybe a dependency a different aur package installed? Is it possible to check that?

Thanks for any help/advice in advance :slight_smile:

1 Like


pactree -r libkipi

Could it be that it has dropped from the repos and now it is in AUR?


First Submitted: 2022-04-22 14:18 (UTC)


I don’t have that package so I used:

$ yay -Si libkipi
Repository      : extra
Name            : libkipi
Version         : 21.12.3-1
Description     : An interface to use kipi-plugins from a KDE application
Architecture    : x86_64
URL             :
Licenses        : GPL  LGPL  FDL
Groups          : None
Provides        : None
Depends On      : kxmlgui  kservice  hicolor-icon-theme
Optional Deps   : None
Conflicts With  : None
Replaces        : None
Download Size   : 100.99 KiB
Installed Size  : 273.86 KiB
Packager        : Antonio Rojas <>
Build Date      : Tue 01 Mar 2022 01:56:04 AM MST
Validated By    : MD5 Sum  SHA-256 Sum  Signature

to gain some info.
You could use :`yay -Qi` for a packages on your machine.

I love how yay closely mirrors pacman commands. very useful when you have aur and repository packages…


1 Like

On my end:

:: Querying AUR...
Repository      : aur
Name            : libkipi
Keywords        : None
Version         : 22.04.0-1
Description     : An interface to use kipi-plugins from a KDE application
URL             :
AUR URL         :
Groups          : None
Licenses        : GPL  LGPL  FDL
Provides        : None
Depends On      : kxmlgui  kservice  hicolor-icon-theme
Make Deps       : extra-cmake-modules
Check Deps      : None
Optional Deps   : None
Conflicts With  : None
Maintainer      : Xenfo
Votes           : 1
Popularity      : 0.975055
First Submitted : Fri 22 Apr 2022 04:18:39 PM CEST
Last Modified   : Fri 22 Apr 2022 04:18:39 PM CEST
Out-of-date     : No

Perhaps it will show it in AUR when your mirrors get synced to the latest updates.

If I run your command I just get this output

pactree -r libkipi

What ever I don’t need to have my mirrors synced until I update. The point was info on libkipi

You did. Or at least you approved it to be installed. As you said, if you didn’t approve it, it would arguably be the first time ever in the history of the Arch repositories. As others noted, you can find out when, and why.

Perhaps it was a dependency of something you installed at some point and now it is not.

If the following doesn’t show “breaking dependency”

sudo pacman -R libpiki

You might want to remove the package.

1 Like

I wasn’t implying that you


before you update.

Good point. However, erroneous info because of not synced mirrors.


This is the output

sudo pacman -R libpiki
error: target not found: libpiki

So I guess I can remove it?

Sorry for the typo in the command line I gave above:

libpiki >> libkipi

1 Like

Ah yeah, silly me… didn’t check for the typo :sweat_smile:

sudo pacman -R libkipi
[sudo] password for shamshiel: 
checking dependencies...

Package (1)  Old Version  Net Change

libkipi      22.04.0-1     -0,28 MiB

Total Removed Size:  0,28 MiB

:: Do you want to remove these packages? [Y/n] Y 
:: Processing package changes...
(1/1) removing libkipi
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Updating icon theme caches...

No “breaking dependency”, so I deleted it… Thanks for the help, appreciate it. :+1:

1 Like

pacman.log is in /var/log

grep libkipi /var/log/pacman.log

should show when it was installed and today/yesterday when you removed it. While grep won’t show you much, you could also open that file in an editor and search for libpiki to see what is before it that likely brought it onto your system.

Looking at the page, it’s required by kipi-plugins and spectacle-light, each of which are required by some packages (and maybe more).


I got rid of this on the 22nd, no idea what it was but it was in the repos:

[2022-03-29T21:46:53+0100] [ALPM] installed libkipi (21.12.3-1)
[2022-04-22T18:49:37+0100] [PACMAN] Running 'pacman -U --noconfirm --config /etc/pacman.conf -- /home/xircon/.cache/yay/libkipi/libkipi-22.04.0-1-x86_64.pkg.tar /home/xircon/.cache/yay/libkipi/libkipi-debug-22.04.0-1-x86_64.pkg.tar'
[2022-04-22T18:49:37+0100] [ALPM] upgraded libkipi (21.12.3-1 -> 22.04.0-1)
[2022-04-22T18:49:37+0100] [ALPM] installed libkipi-debug (22.04.0-1)
[2022-04-22T18:49:38+0100] [PACMAN] Running 'pacman -D -q --asdeps --noconfirm --config /etc/pacman.conf -- libkipi-debug'
[2022-04-22T18:49:46+0100] [PACMAN] Running 'pacman -R --config /etc/pacman.conf -- libkipi'
[2022-04-22T18:49:47+0100] [ALPM] removed libkipi (22.04.0-1)
[2022-04-22T18:55:41+0100] [PACMAN] Running 'pacman -Rsu --noconfirm extra-cmake-modules libkipi-debug'
[2022-04-22T18:55:41+0100] [ALPM] removed libkipi-debug (22.04.0-1)

Thanks for the hint, I checked the pacman.log and got the following:

[2021-09-30T14:21:08+0200] [ALPM] installed libkipi (21.08.1-1)
[2021-10-08T07:34:34+0200] [ALPM] upgraded libkipi (21.08.1-1 -> 21.08.2-1)
[2021-11-04T17:49:33+0100] [ALPM] upgraded libkipi (21.08.2-1 -> 21.08.3-1)
[2021-12-10T17:56:00+0100] [ALPM] upgraded libkipi (21.08.3-1 -> 21.12.0-1)
[2022-01-06T17:42:32+0100] [ALPM] upgraded libkipi (21.12.0-1 -> 21.12.1-1)
[2022-02-04T18:16:08+0100] [ALPM] upgraded libkipi (21.12.1-1 -> 21.12.2-1)
[2022-03-07T18:07:25+0100] [ALPM] upgraded libkipi (21.12.2-1 -> 21.12.3-1)
[2022-04-24T05:19:54+0200] [PACMAN] Running 'pacman -U --noconfirm --config /etc/pacman.conf -- /home/shamshiel/.cache/yay/libkipi/libkipi-22.04.0-1-x86_64.pkg.tar.zst /home/shamshiel/.cache/yay/libkipi/libkipi-debug-22.04.0-1-x86_64.pkg.tar.zst'
[2022-04-24T05:19:54+0200] [ALPM] upgraded libkipi (21.12.3-1 -> 22.04.0-1)
[2022-04-24T05:19:54+0200] [ALPM] installed libkipi-debug (22.04.0-1)
[2022-04-24T05:19:55+0200] [PACMAN] Running 'pacman -D -q --asdeps --noconfirm --config /etc/pacman.conf -- libkipi-debug'
[2022-04-24T07:31:37+0200] [PACMAN] Running 'pacman -R libkipi'
[2022-04-24T07:31:58+0200] [ALPM] removed libkipi (22.04.0-1)

The 2021-09-30T14:21:08+0200 date means that this package was installed with EndeavourOS because this was when I first installed the OS.

Like this case yesterday, I was amazed at libmediawiki because I didn’t remember being specifically installed by me.

Packages will be installed as dependencies, and this is a pretty safe assumption for a library package like libkipi and libmediawiki .

Anyway, the solution to this thread is most definitely this:


libkipi was, until recently, a dependency of gwenview and spectacle (and maybe some other applications in the Arch repos). Those dependencies are no longer necessary.

Here’s the commit that removed libkipi as a dependency of gwenview (notice line #13), and here’s the commit that removed it as a dependency of spectacle (line #10).

The package was kept available by moving it to the AUR because it is still required by 2 AUR packages (spectacle-light and kipi-plugins, both of which require either libkipi or libkipi-git).


:point_up: I think this post should be marked as the solution, as it explains exactly what happened.


I know that packages are often installed as dependencies and are mostly safe to use, but in some cases they can be optional and not needed.

1 Like