* [gentoo-user] Portage elog messages about historical symlinks
@ 2013-07-24 18:22 Mick
2013-07-24 20:43 ` Kerin Millar
0 siblings, 1 reply; 3+ messages in thread
From: Mick @ 2013-07-24 18:22 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: Text/Plain, Size: 941 bytes --]
I am getting messages like the one below from portage every now and then.
Especially, about /var/run, but in this case about a different directory:
* Messages for package dev-libs/klibc-1.5.20:
* One or more symlinks to directories have been preserved in order to
* ensure that files installed via these symlinks remain accessible. This
* indicates that the mentioned symlink(s) may be obsolete remnants of an
* old install, and it may be appropriate to replace a given symlink with
* the directory that it points to.
*
* /usr/lib/klibc/include/asm
*
Perhaps I am having a senior moment, but I am not clear what I should do
despite the friendly message. This is the symlink in question:
ls -la /usr/lib/klibc/include/asm
lrwxrwxrwx 1 root root 7 Nov 8 2008 /usr/lib/klibc/include/asm -> asm-x86
How am I supposed to *replace* it with the directory that it points to?
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [gentoo-user] Portage elog messages about historical symlinks
2013-07-24 18:22 [gentoo-user] Portage elog messages about historical symlinks Mick
@ 2013-07-24 20:43 ` Kerin Millar
2013-07-27 19:16 ` Mick
0 siblings, 1 reply; 3+ messages in thread
From: Kerin Millar @ 2013-07-24 20:43 UTC (permalink / raw
To: gentoo-user
On 24/07/2013 19:22, Mick wrote:
> I am getting messages like the one below from portage every now and then.
> Especially, about /var/run, but in this case about a different directory:
>
> * Messages for package dev-libs/klibc-1.5.20:
>
> * One or more symlinks to directories have been preserved in order to
> * ensure that files installed via these symlinks remain accessible. This
> * indicates that the mentioned symlink(s) may be obsolete remnants of an
> * old install, and it may be appropriate to replace a given symlink with
> * the directory that it points to.
> *
> * /usr/lib/klibc/include/asm
> *
>
> Perhaps I am having a senior moment, but I am not clear what I should do
> despite the friendly message. This is the symlink in question:
>
> ls -la /usr/lib/klibc/include/asm
> lrwxrwxrwx 1 root root 7 Nov 8 2008 /usr/lib/klibc/include/asm -> asm-x86
>
>
> How am I supposed to *replace* it with the directory that it points to?
>
I would take it to mean that /usr/lib/klibc/include/asm should be a
directory and contain the files that are currently residing in the
asm-x86 directory. For example:
# rm asm
# mkdir asm
# mv -- asm-x86/* asm/
# rmdir asm-x86
--Kerin
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [gentoo-user] Portage elog messages about historical symlinks
2013-07-24 20:43 ` Kerin Millar
@ 2013-07-27 19:16 ` Mick
0 siblings, 0 replies; 3+ messages in thread
From: Mick @ 2013-07-27 19:16 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: Text/Plain, Size: 1491 bytes --]
On Wednesday 24 Jul 2013 21:43:32 Kerin Millar wrote:
> On 24/07/2013 19:22, Mick wrote:
> > I am getting messages like the one below from portage every now and then.
> > Especially, about /var/run, but in this case about a different directory:
> >
> > * Messages for package dev-libs/klibc-1.5.20:
> > * One or more symlinks to directories have been preserved in order to
> > * ensure that files installed via these symlinks remain accessible.
> > This * indicates that the mentioned symlink(s) may be obsolete
> > remnants of an * old install, and it may be appropriate to replace a
> > given symlink with * the directory that it points to.
> > *
> > * /usr/lib/klibc/include/asm
> > *
> >
> > Perhaps I am having a senior moment, but I am not clear what I should do
> > despite the friendly message. This is the symlink in question:
> >
> > ls -la /usr/lib/klibc/include/asm
> > lrwxrwxrwx 1 root root 7 Nov 8 2008 /usr/lib/klibc/include/asm ->
> > asm-x86
> >
> >
> > How am I supposed to *replace* it with the directory that it points to?
>
> I would take it to mean that /usr/lib/klibc/include/asm should be a
> directory and contain the files that are currently residing in the
> asm-x86 directory. For example:
>
> # rm asm
> # mkdir asm
> # mv -- asm-x86/* asm/
> # rmdir asm-x86
Thanks Kerin, I did as you suggested, remerged dev-libs/klibc and now waiting
to see if anything breaks. Ha!
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-07-27 19:17 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-07-24 18:22 [gentoo-user] Portage elog messages about historical symlinks Mick
2013-07-24 20:43 ` Kerin Millar
2013-07-27 19:16 ` Mick
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox