Pacman didn't ask to change/upgrade a package that was renamed

andreyv · 2012-11-14 10:45:43

I had a package named "libkeybinder" installed on my system. Today I noticed that there was no such package in the repositories anymore — it seems to have moved to "libkeybinder2". But when I ran full system upgrade with "yaourt -Syua", I didn't get any notification of this, and the old package remained on the system.

Is this a bug/error or is this generally allowable? Now I can't be sure that there are no other similarly outdated packages on my system.

loafer · 2012-11-14 10:52:48

I think libkeybinder was in the AUR rather than the repos and has now been moved to [community] as libkeybinder2. AUR packages are the responsibility of the user.

Your title says pacman but you actually apear to be using the yaourt wrapper to carry out system upgrades.

WorMzy · 2012-11-14 11:00:30

Normally, whenever a package is renamed like this, packages that depended on the old package are updated to depend on the new package. So when you update package foo, which used to depend on package bar, but now depends on bar2, bar2 will be installed, and pacman will inform you that package bar will be removed (due to file conflicts).

'libkeybinder2' (and it's python2 bindings) is a community package which isn't a dependency for anything in the official repos other than terminator. I suspect that there may be a few AUR packages that depend on it though, and these will need to be updated too.

If you've explicitly installed the old-named package, but don't have any packages that depend on it, then it will just stagnate until you manually intervene.

andreyv · 2012-11-14 11:16:34

WorMzy wrote:

If you've explicitly installed the old-named package, but don't have any packages that depend on it, then it will just stagnate until you manually intervene.

That's what I've feared. Is there a good way to detect such packages? I can see only "pacman/yaourt -Qm", but this also lists all packages installed from AUR.

WorMzy · 2012-11-14 11:36:00

I've cobbled together a bash loop to check this, but I've no doubt there's more sophisticated ways of finding out.

for i in $(yaourt -Qqm); do
  yaourt -Sia "$i" &>/dev/null || echo $i    
done

Requires yaourt, obviously. Basically searches the AUR for "local" packages, and prints out the name of any packages that can't be found.

Last edited by WorMzy (2012-11-14 11:37:07)

falconindy · 2012-11-14 11:47:06

The replace mechanism is dependent on the new package declaring replaces=(oldpkg) in the PKGBUILD. It shouldn't be requisite under normal circumstances that you update the dependencies of all preexistent packages.

andreyv · 2012-11-14 11:51:18

WorMzy wrote:

I've cobbled together a bash loop to check this, but I've no doubt there's more sophisticated ways of finding out.
for i in $(yaourt -Qqm); do
  yaourt -Sia "$i" &>/dev/null || echo $i    
done
Requires yaourt, obviously. Basically searches the AUR for "local" packages, and prints out the name of any packages that can't be found.

This works. Thanks! With the help of this command I've found that "powertop2" has also been moved/deleted.

andreyv · 2012-11-19 09:56:52

It turns out that there is indeed a simpler and much faster command to list local packages not found in AUR:

yaourt -Qma | grep local

cfr · 2012-11-19 23:36:46

What happens in the case of packages such as consolekit? Will this eventually get removed by pacman or am I supposed to remove it?

Actually, I notice that it shows as "explicitly installed" for some reason so would that be why I still have it?

andreyv · 2012-11-20 09:13:35

Yes, you would have to remove it manually.

Arch Linux

#1 2012-11-14 10:45:43

Pacman didn't ask to change/upgrade a package that was renamed

#2 2012-11-14 10:52:48

Re: Pacman didn't ask to change/upgrade a package that was renamed

#3 2012-11-14 11:00:30

Re: Pacman didn't ask to change/upgrade a package that was renamed

#4 2012-11-14 11:16:34

Re: Pacman didn't ask to change/upgrade a package that was renamed

#5 2012-11-14 11:36:00

Re: Pacman didn't ask to change/upgrade a package that was renamed

#6 2012-11-14 11:47:06

Re: Pacman didn't ask to change/upgrade a package that was renamed

#7 2012-11-14 11:51:18

Re: Pacman didn't ask to change/upgrade a package that was renamed

#8 2012-11-19 09:56:52

Re: Pacman didn't ask to change/upgrade a package that was renamed

#9 2012-11-19 23:36:46

Re: Pacman didn't ask to change/upgrade a package that was renamed

#10 2012-11-20 09:13:35

Re: Pacman didn't ask to change/upgrade a package that was renamed

Board footer