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

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.

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

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.

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

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.