Best way to handle packages removed from repo

Nickm · 2022-11-15 10:39:35

Hi, today I updated using `pacman -Syu` and ran into some issues with a package that needed to be installed where the filesystem actually already contained these files but from another package.
I had dleyna-renderer and dleyna-core installed where the new package was dleyna, if I remember the details correctly.

So I did some searching on my system...

First I ran:

pacman -Q |awk '{print $1}' > pkglist.txt

then I ran:

for i in `cat pkglist.txt`; do pacman -Si "$i" >> /dev/null || echo $i >> notfound3.txt; done
error: package 'cloog' was not found
error: package 'deadbeef' was not found
error: package 'dropbox' was not found
error: package 'espeak' was not found
error: package 'freemind' was not found
error: package 'gnome-books' was not found
error: package 'gnome-getting-started-docs' was not found
error: package 'libretro-shaders-cg' was not found
error: package 'makemkv' was not found
error: package 'osl' was not found
error: package 'python-pychromecast-git' was not found
error: package 'slack-desktop' was not found
error: package 'tracker' was not found
error: package 'tracker-miners' was not found
error: package 'vino' was not found

I know some of these packages I installed through aur, so they were expected. But for example gnome-books was not.

pacman -Qi gnome-books
Name            : gnome-books
Version         : 40.0-1.1
Description     : Access and organize your e-books on GNOME
Architecture    : x86_64
URL             : https://wiki.gnome.org/Apps/Books
Licenses        : GPL
Groups          : gnome
Provides        : None
Depends On      : evince  gjs  gtk3  gnome-desktop  tracker3-miners  webkit2gtk
                  libgepub  gnome-epub-thumbnailer
Optional Deps   : None
Required By     : None
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 1605.71 KiB
Packager        : ALHP Buildbot <alhp@anonfunc.net>
Build Date      : Sun 30 May 2021 08:35:29 AM CEST
Install Date    : Wed 27 Oct 2021 07:10:16 PM CEST
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature

So my question is, what is the best way to keep this in sync with the official repos? Or should maybe pacman inform us of such things?

dogknowsnx · 2022-11-15 12:19:34

EDIT:

pacman -Qqe > pkglist.txt

(no orphans)

EDIT2: *headbump* - thanks @Allan

Last edited by dogknowsnx (2022-11-15 12:39:17)

Allan · 2022-11-15 12:28:03

Or....

pacman -Qm

cfr · 2022-11-15 17:03:34

Often such packages end up in AUR, so if you are checking for AUR updates, you can manage them that way.

If you get conflicting files when upgrading the system, the typical case is that the files are owned by a package not in the official repos. In that case, you should generally uninstall that package and complete the update, then consider your options. Obviously, that's not true if the package is critical to your system.

If the conflicting files are part of a package installed from the official repos, you shouldn't get a complaint about conflicting files. Rather, you might be told a package needs to be removed or replaced - something like that. Otherwise, it is a bug in an official package and should be reported.

Even when it is something you installed from AUR, packages will typically declare conflicts so you don't get the conflicting files message.

The most common reason for conflicting files is that you installed something without using pacman, so the files aren't owned by any package. But you should definitely know if that i the case and should typically avoid the situation by not installing things in other ways to the system directories pacman manages.

Nickm · 2022-11-16 13:32:39

Thanks you very much for the replies, this will make such situations easier for me.

Arch Linux

#1 2022-11-15 10:39:35

Best way to handle packages removed from repo

#2 2022-11-15 12:19:34

Re: Best way to handle packages removed from repo

#3 2022-11-15 12:28:03

Re: Best way to handle packages removed from repo

#4 2022-11-15 17:03:34

Re: Best way to handle packages removed from repo

#5 2022-11-16 13:32:39

Re: Best way to handle packages removed from repo

Board footer