[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#612000: marked as done (libc6: please postinst symlink /usr/local/lib64 -> /usr/local/lib for consistency with /, and /usr ones)

Your message dated Tue, 30 Aug 2011 18:44:16 +0200
with message-id <20110830164416.GC5712@volta.aurel32.net>
and subject line Re: Bug#612000: libc6: please postinst symlink /usr/local/lib64 -> /usr/local/lib for consistency with /, and /usr ones
has caused the Debian Bug report #612000,
regarding libc6: please postinst symlink /usr/local/lib64 -> /usr/local/lib for consistency with /, and /usr ones
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
612000: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612000
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libc6
Version: 2.11.2-9
Severity: minor


Without /usr/local/lib64 symlink to /usr/local/lib  many local installations of
upstream projects (not that I am encouraging such cruel activity) would install
into /usr/local/lib64 on amd64 systems.  Since symlink is not available,
install would create a directory /usr/local/lib64 to place the content;
but default Debian setup of ldconfig does not include any of */lib64
directories, so those libraries would not become readily available.

Having a symlink /usr/local/lib64 -> /usr/local/lib should make our systems
"friendlier" to the users willing sacrificing piece of mind by installing
something 'locally'.

-- System Information:
Debian Release: 6.0
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (300, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libc6 depends on:
ii  libc-bin                      2.11.2-9   Embedded GNU C Library: Binaries
ii  libgcc1                       1:4.4.5-8  GCC support library

libc6 recommends no packages.

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]         1.5.36     Debian configuration management sy
pn  glibc-doc                     <none>     (no description available)
ii  locales                       2.11.2-7   Embedded GNU C Library: National L

-- debconf information:
* glibc/upgrade: true
  glibc/disable-screensaver:
  glibc/restart-failed:
* glibc/restart-services: exim4 cups cron atd

--- End Message ---
--- Begin Message --- 
On Fri, Feb 04, 2011 at 10:09:51AM -0500, Yaroslav Halchenko wrote:
> Package: libc6
> Version: 2.11.2-9
> Severity: minor
> 
> 
> Without /usr/local/lib64 symlink to /usr/local/lib  many local installations of
> upstream projects (not that I am encouraging such cruel activity) would install
> into /usr/local/lib64 on amd64 systems.  Since symlink is not available,
> install would create a directory /usr/local/lib64 to place the content;
> but default Debian setup of ldconfig does not include any of */lib64
> directories, so those libraries would not become readily available.
> 
> Having a symlink /usr/local/lib64 -> /usr/local/lib should make our systems
> "friendlier" to the users willing sacrificing piece of mind by installing
> something 'locally'.

Now that lib64 symlinks have been removed from / and /usr (they are
causing problems with multiarch), it doesn't make sense to add one in 
/usr/local. I am therefore closing this bug, feel free to reopen it if
you disagree.

-- 
Aurelien Jarno                          GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net

--- End Message ---
Reply to: