Re: Upgrading from bo to hamm

To: debian-devel@lists.debian.org
Subject: Re: Upgrading from bo to hamm
From: Guy Maor <maor@ece.utexas.edu>
Date: 09 Apr 1998 20:04:56 -0700
Message-id: <[🔎] 871zv6tm07.fsf@1Cust99.max71.los-angeles.ca.ms.uu.net>
In-reply-to: "LeRoy D. Cressy"'s message of "Thu, 09 Apr 1998 18:00:32 -0400"
References: <[🔎] 352D4500.58CAE40F@netaxs.com>

"LeRoy D. Cressy" <ldc@netaxs.com> writes:

> I question the purpose of leaving broken symbolic links when 
> upgrading the libraries.  For instance libreadline2 leaves
> the following broken links reported by ldconfig:

Those symlinks are part of libreadline2-dev.  If you upgrade to
libreadline2-altdev, then the links will be fixed.

Guy

--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to:

Follow-Ups:
- Re: Upgrading from bo to hamm
  - From: Steve Greenland <stevegr@master.debian.org>
- Re: Upgrading from bo to hamm
  - From: "LeRoy D. Cressy" <ldc@netaxs.com>
- Re: Upgrading from bo to hamm
  - From: Chris Fearnley <cjf@netaxs.com>

References:
- Upgrading from bo to hamm
  - From: "LeRoy D. Cressy" <ldc@netaxs.com>

Prev by Date: Re: #19519: tmpreaper: Will not remove dirs
Next by Date: packaging Pam modules?
Previous by thread: Upgrading from bo to hamm
Next by thread: Re: Upgrading from bo to hamm
Index(es):
- Date
- Thread