[arch-general] js60 update -- reveals older packages installed as deps not updated and left on system

Bruno Pagani bruno.n.pagani at gmail.com
Sat May 18 09:45:08 UTC 2019


Le 18/05/2019 à 01:23, David C. Rankin a écrit :
>   Is this normal that new versions of packages are just added without removing
> the replaced package?

Yes, because they are not straight upgrade from previous version and
often have incompatibilities so that both packages can be used by
different software. So newer js version never replaces the old ones.

> I would have expected 'js' to be removed when `js17` was
> updated and then 'js17' to be removed when `js185` became available?

And in this particular case, js17>js185, because js185 is 1.8.5 while
js17 is 17.0.

>   So is this just one of those circumstances where you have to manually check
> if packages are no longer needed by the system and uninstall manually? It's
> not a big deal, but more a curiosity to understand when this type thing can
> occur in the normal process of just calling pacman -Syu.

Yes, this is the standard case of old dependencies becoming unneeded, it
just seems strange to you because all those packages are js*, but if
they have a different name and don’t upgrade over the previous one
that’s for a good reason.


More information about the arch-general mailing list