NetBSD Problem Report #52804
From dholland@netbsd.org Sun Dec 10 05:10:35 2017
Return-Path: <dholland@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
by mollari.NetBSD.org (Postfix) with ESMTPS id 677677A177
for <gnats-bugs@gnats.NetBSD.org>; Sun, 10 Dec 2017 05:10:35 +0000 (UTC)
Message-Id: <20171210051035.1E46184D68@mail.netbsd.org>
Date: Sun, 10 Dec 2017 05:10:35 +0000 (UTC)
From: dholland@NetBSD.org
Reply-To: dholland@NetBSD.org
To: gnats-bugs@NetBSD.org
Subject: make postinstall obsoletelibs a separate thing?
X-Send-Pr-Version: 3.95
>Number: 52804
>Category: toolchain
>Synopsis: make postinstall obsoletelibs a separate thing?
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: toolchain-manager
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Sun Dec 10 05:15:00 +0000 2017
>Last-Modified: Sun Dec 10 10:30:01 +0000 2017
>Originator: David A. Holland
>Release: NetBSD 8.99.8 (20171205)
>Organization:
>Environment:
System: NetBSD valkyrie 8.99.8 NetBSD 8.99.8 (VALKYRIE) #24: Tue Dec 5 17:30:57 EST 2017 dholland@valkyrie:/usr/src/sys/arch/amd64/compile/VALKYRIE amd64
Architecture: x86_64
Machine: amd64
>Description:
It occurred to me tonight while working on unborking a machine that
was running a mixture of 6.1 and 7.99.33 that it would be useful to be
able to run subsets of "postinstall fix obsolete", so as to allow
clearing away the bulk of the obsolete files while leaving dangerous
ones or suspect ones for closer analysis.
But I think it would be sufficient to just split the obsolete library
handling apart from the obsolete paths handling and make them separate
toplevel targets. As far as I know the downgrade hazards associated
with postinstall fix obsolete are limited to shared library images.
>How-To-Repeat:
>Fix:
>Audit-Trail:
From: Thomas Klausner <wiz@NetBSD.org>
To: NetBSD bugtracking <gnats-bugs@NetBSD.org>
Cc:
Subject: Re: toolchain/52804: make postinstall obsoletelibs a separate thing?
Date: Sun, 10 Dec 2017 08:21:34 +0100
On Sun, Dec 10, 2017 at 05:15:01AM +0000, David Holland wrote:
> It occurred to me tonight while working on unborking a machine that
> was running a mixture of 6.1 and 7.99.33 that it would be useful to be
> able to run subsets of "postinstall fix obsolete", so as to allow
> clearing away the bulk of the obsolete files while leaving dangerous
> ones or suspect ones for closer analysis.
>
> But I think it would be sufficient to just split the obsolete library
> handling apart from the obsolete paths handling and make them separate
> toplevel targets. As far as I know the downgrade hazards associated
> with postinstall fix obsolete are limited to shared library images.
Can you please expand what you want in more detail?
AFAIK, postinstall fix does not delete old versions of libraries.
Thomas
From: matthew green <mrg@eterna.com.au>
To: gnats-bugs@NetBSD.org
Cc: toolchain-manager@netbsd.org, gnats-admin@netbsd.org,
netbsd-bugs@netbsd.org, dholland@NetBSD.org
Subject: re: toolchain/52804: make postinstall obsoletelibs a separate thing?
Date: Sun, 10 Dec 2017 21:29:02 +1100
> On Sun, Dec 10, 2017 at 05:15:01AM +0000, David Holland wrote:
> > It occurred to me tonight while working on unborking a machine that
> > was running a mixture of 6.1 and 7.99.33 that it would be useful to be
> > able to run subsets of "postinstall fix obsolete", so as to allow
> > clearing away the bulk of the obsolete files while leaving dangerous
> > ones or suspect ones for closer analysis.
> >
> > But I think it would be sufficient to just split the obsolete library
> > handling apart from the obsolete paths handling and make them separate
> > toplevel targets. As far as I know the downgrade hazards associated
> > with postinstall fix obsolete are limited to shared library images.
>
> Can you please expand what you want in more detail?
> AFAIK, postinstall fix does not delete old versions of libraries.
> Thomas
the main problem is that it can delete the version pointed to
by the symlinks. it deletes all but the latest of a major
version of a library, but if you downgrade, then the latest
is no longer the "in use" one, but postinstall deletes it.
eg, say you have libfoo.so.2.3, ugprade to libfoo.so.2.4 and
then find a bug, and install old libs. libfoo.so and
libfoo.so.2 now point to libfoo.so.2.3 but install will
delete this version, since it's older than libfoo.so.2.4.
it's really annoying, and i'd rather fix this than to make
the change dh is suggesting, but either would be good..
.mrg.
(Contact us)
$NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2014
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.