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

2019-05-20 Thread Bruno Pagani via arch-general
Le 20/05/2019 à 11:42, Georg a écrit : > Am 18.05.2019 01:23, schrieb David C. Rankin: >> $ pmq | grep '^js' >> js 24.2.0-4 >> js17 17.0.0-4 >> js52 52.9.0-2 >> js60 60.6.3-1 > > What puzzles me is the wide range of version numbers with the > un-suffixd package not even being the highest. Can anyon

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

2019-05-20 Thread Georg
Am 18.05.2019 01:23, schrieb David C. Rankin: $ pmq | grep '^js' js 24.2.0-4 js17 17.0.0-4 js52 52.9.0-2 js60 60.6.3-1 What puzzles me is the wide range of version numbers with the un-suffixd package not even being the highest. Can anyone explain their versioning scheme, like does it make sen

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

2019-05-19 Thread Lone_Wolf
On 18-05-2019 01:23, David C. Rankin wrote: 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

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

2019-05-19 Thread David C. Rankin
On 05/18/2019 04:45 AM, Bruno Pagani wrote: > 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. Thank you B

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

2019-05-19 Thread Jagannathan Tiruvallur Eachambadi via arch-general
On 17-05-19 18:23:00 -0500, David C. Rankin wrote: Further checking whether any of the old packages are required shows they are not, e.g. $ pacman -Qdt ... js 24.2.0-4 js17 17.0.0-4 js52 52.9.0-2 ... So is this just one of those circumstances where you have to manually check if packages are

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

2019-05-19 Thread Ralph Corderoy
Hi David, > Is this normal that new versions of packages are just added without > removing the replaced package? Yes, I think so. Checking for orphans is part of the normal process. https://wiki.archlinux.org/index.php/System_maintenance#Check_for_orphans_and_dropped_packages -- Cheers, Ralph.

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

2019-05-19 Thread Bruno Pagani via arch-general
Hi, 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 diff

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

2019-05-18 Thread David C. Rankin
All, I don't know if this is an old packaging problem, or if this is normal, but with the following updates: Packages (6) js60-60.6.3-1 linux-lts-4.19.44-1 linux-lts-headers-4.19.44-1 perl-net-http-6.19-1 polkit-0.116-1 tmux-2.9_a-2 I saw the: Net Upgrade Size: 53.68 M