On 5/19/19 6:16 PM, Anatol Pomozov via arch-general wrote:
...
>> lsof4.91201804044.93.2 20190508399
>
> Where did you find lsof version 4.93.2?>
> The official website does not mention current version. And the mirror
> Arch uses hosts 4.91 only
Hello
On Sun, May 19, 2019 at 3:08 PM Genes Lists via arch-general
wrote:
>
> Hi - First a thank you for all the great work managing and keeping
> packages up to date. It can a significant amount of work.
>
> That said, periodically I check the repos for out of date packages. I've
> selected a
Hi - First a thank you for all the great work managing and keeping
packages up to date. It can a significant amount of work.
That said, periodically I check the repos for out of date packages. I've
selected a few to highlight based on age and my own view of importance
(no claim its a good view).
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
On Thu, 16 May 2019 16:06:51 +0100
Andy Pieters wrote:
> On Thu, May 16, 2019 at 3:23 PM mike lojkovic via arch-general <
> arch-general@archlinux.org> wrote:
>
> > Suggesting pacman add some portage style features for dependency
> > resolution and packaging? Modifying packages on a local
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
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
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,
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
9 matches
Mail list logo
