[gentoo-user] Only two people in the gentoo world is having this problem?

[gentoo-user] Only two people in the gentoo world is having this problem?

[Damian]

While ago I reported a bug regarding gvfs:
    https://bugs.gentoo.org/show_bug.cgi?id=302196

It's been unresolved for quite a long time now, so I was wondering if
somebody could give me a hint on how to solve this problem.

Best,
Damian.

Re: [gentoo-user] Only two people in the gentoo world is having this problem?

[Mark Knecht]

On Wed, Mar 10, 2010 at 12:28 AM, Damian <damian.only@gmail.com> wrote:
> While ago I reported a bug regarding gvfs:
>    https://bugs.gentoo.org/show_bug.cgi?id=302196
>
> It's been unresolved for quite a long time now, so I was wondering if
> somebody could give me a hint on how to solve this problem.
>
> Best,
> Damian.
>
>

??

revdep-rebuild -ip

??

- Mark

Re: [gentoo-user] Only two people in the gentoo world is having this problem?

[Damian]

On Wed, Mar 10, 2010 at 2:02 PM, Mark Knecht <markknecht@gmail.com> wrote:
> On Wed, Mar 10, 2010 at 12:28 AM, Damian <damian.only@gmail.com> wrote:
>> While ago I reported a bug regarding gvfs:
>>    https://bugs.gentoo.org/show_bug.cgi?id=302196
>>
>> It's been unresolved for quite a long time now, so I was wondering if
>> somebody could give me a hint on how to solve this problem.
>>
>> Best,
>> Damian.
>>
>>
>
> ??
>
> revdep-rebuild -ip
I already tried (reconcilio actually), and didn't solve the problem:
it tries to rebuild gvfs, failing miserably again.

>
> ??
>
> - Mark
>
>

Re: [gentoo-user] Only two people in the gentoo world is having this problem?

[Mark Knecht]

On Wed, Mar 10, 2010 at 6:05 AM, Damian <damian.only@gmail.com> wrote:
> On Wed, Mar 10, 2010 at 2:02 PM, Mark Knecht <markknecht@gmail.com> wrote:
>> On Wed, Mar 10, 2010 at 12:28 AM, Damian <damian.only@gmail.com> wrote:
>>> While ago I reported a bug regarding gvfs:
>>>    https://bugs.gentoo.org/show_bug.cgi?id=302196
>>>
>>> It's been unresolved for quite a long time now, so I was wondering if
>>> somebody could give me a hint on how to solve this problem.
>>>
>>> Best,
>>> Damian.
>>>
>>>
>>
>> ??
>>
>> revdep-rebuild -ip
> I already tried (reconcilio actually), and didn't solve the problem:
> it tries to rebuild gvfs, failing miserably again.
>

I saw that in the bug report. If you want to keep going down the path
of what didn't work then do nothing. Potentially revdep-rebuild finds
something else.

You need to post some results. I've seen gvfs fail due to flag
settings. How would anyone here make a reasoned response with so
little data?

It's up to you.

- Mark

Re: [gentoo-user] Only two people in the gentoo world is having this problem?

[Damian]

On Wed, Mar 10, 2010 at 3:10 PM, Mark Knecht <markknecht@gmail.com> wrote:
> On Wed, Mar 10, 2010 at 6:05 AM, Damian <damian.only@gmail.com> wrote:
>> On Wed, Mar 10, 2010 at 2:02 PM, Mark Knecht <markknecht@gmail.com> wrote:
>>> On Wed, Mar 10, 2010 at 12:28 AM, Damian <damian.only@gmail.com> wrote:
>>>> While ago I reported a bug regarding gvfs:
>>>>    https://bugs.gentoo.org/show_bug.cgi?id=302196
>>>>
>>>> It's been unresolved for quite a long time now, so I was wondering if
>>>> somebody could give me a hint on how to solve this problem.
>>>>
>>>> Best,
>>>> Damian.
>>>>
>>>>
>>>
>>> ??
>>>
>>> revdep-rebuild -ip
>> I already tried (reconcilio actually), and didn't solve the problem:
>> it tries to rebuild gvfs, failing miserably again.
>>
>
> I saw that in the bug report. If you want to keep going down the path
> of what didn't work then do nothing. Potentially revdep-rebuild finds
> something else.
>
> You need to post some results. I've seen gvfs fail due to flag
> settings. How would anyone here make a reasoned response with so
> little data?
Actually the flag plays no role. Since I compiled the package again
with the original flags and I got the same results. I honestly don't
know which (other) relevant data I can provide.

I didn't intend to make anybody upset with my email, or with the
mention to the word paludis.

Re: [gentoo-user] Only two people in the gentoo world is having this problem?

[Mark Knecht]

On Wed, Mar 10, 2010 at 6:25 AM, Damian <damian.only@gmail.com> wrote:
> On Wed, Mar 10, 2010 at 3:10 PM, Mark Knecht <markknecht@gmail.com> wrote:
>> On Wed, Mar 10, 2010 at 6:05 AM, Damian <damian.only@gmail.com> wrote:
>>> On Wed, Mar 10, 2010 at 2:02 PM, Mark Knecht <markknecht@gmail.com> wrote:
>>>> On Wed, Mar 10, 2010 at 12:28 AM, Damian <damian.only@gmail.com> wrote:
>>>>> While ago I reported a bug regarding gvfs:
>>>>>    https://bugs.gentoo.org/show_bug.cgi?id=302196
>>>>>
>>>>> It's been unresolved for quite a long time now, so I was wondering if
>>>>> somebody could give me a hint on how to solve this problem.
>>>>>
>>>>> Best,
>>>>> Damian.
>>>>>
>>>>>
>>>>
>>>> ??
>>>>
>>>> revdep-rebuild -ip
>>> I already tried (reconcilio actually), and didn't solve the problem:
>>> it tries to rebuild gvfs, failing miserably again.
>>>
>>
>> I saw that in the bug report. If you want to keep going down the path
>> of what didn't work then do nothing. Potentially revdep-rebuild finds
>> something else.
>>
>> You need to post some results. I've seen gvfs fail due to flag
>> settings. How would anyone here make a reasoned response with so
>> little data?
> Actually the flag plays no role. Since I compiled the package again
> with the original flags and I got the same results. I honestly don't
> know which (other) relevant data I can provide.
>
> I didn't intend to make anybody upset with my email, or with the
> mention to the word paludis.
>
>
I'm sorry. I didn't mean to suggest I was upset or anything like that.
It's just that sometimes different tools tell you different things.
Additionally you are not posting anything much in this thread yet and
assume folks will go read the bug post. It's not your fault but I got
a certificate error when following your link so I didn't do that.

OK, that said let's look at basics.

1) What profile are you using? (eselect profile list)
2) USE flags from make.conf
3) Current results of emerge -pvDuN @world  (assuming portage 2.2 or higher...)
4) results of revdep-rebuild -ip

I don't know what else to suggest at this point. I've got the stable
version emerged. I haven't had any problems myself but Gentoo is
always a bit different from user to user.

- Mark

Re: [gentoo-user] Only two people in the gentoo world is having this problem?

[Damian]

Hi Mark,

> 1) What profile are you using? (eselect profile list)
    default/linux/amd64/10.0
> 2) USE flags from make.conf
    nls -kde -qt3 qt4 dvd alsa cdr X a52 aac acpi apm -arts \
bash-completion bzip2 crypt dbus dts dvdr ffmpeg flac gif hal hddtemp \
iconv jpeg jpeg2k latex libnotify lm_sensors mad mp3 mpeg mpi mplayer \
nsplugin ogg opengl pdf raw sdl sharedmem sockets spell sse2 ssl svg \
svga taglib threads usb -vim-syntax vorbis wifi win32codecs \
xcomposite xvid zlib truetype type1 avi dvdread mjpeg subtitles sse \
mmx ssse3 emacs pmu nvidia beagle bluetooth

> 3) Current results of emerge -pvDuN @world  (assuming portage 2.2 or higher...)
Sadly, I cannot use emerge on my system. The problem may be paludis
related (I also asked in the paludis mailing liist) but I doubt it.

> 4) results of revdep-rebuild -ip
reconcilio finds gvfs as a broken only package:
  * gnome-base/gvfs-1.2.3::installed
      /usr/libexec/gvfsd-archive (requires liblzmadec.so.0)


> I don't know what else to suggest at this point. I've got the stable
> version emerged. I haven't had any problems myself but Gentoo is
> always a bit different from user to user.
No problem, I will see what other things I can try. I'm far from being
a gentoo expert, so that might be the process of discovering the error
harder.

Best,
Damian.

Re: [gentoo-user] Only two people in the gentoo world is having this problem?

[Michele Alzetta]

[-- Attachment #1: Type: text/plain, Size: 232 bytes --]

Find out what package /usr/lib64/liblzmadec.so belongs to and re-emerge that
package.
If you have ccache activated, delete the whole cache before doing this.
If the problem is still present, at this point try
revdep-rebuild -i

HTH

[-- Attachment #2: Type: text/html, Size: 290 bytes --]

Re: [gentoo-user] Only two people in the gentoo world is having this problem?

[Paul Hartman]

On Wed, Mar 10, 2010 at 2:28 AM, Damian <damian.only@gmail.com> wrote:
> While ago I reported a bug regarding gvfs:
>    https://bugs.gentoo.org/show_bug.cgi?id=302196
>
> It's been unresolved for quite a long time now, so I was wondering if
> somebody could give me a hint on how to solve this problem.

I don't use gvfs (or gnome) but I just tried to emerge with the same
USE flags you listed in the bug report. It worked for me. I'm on
~amd64 and emerged gvfs-1.4.3 (and I do not have the file
/usr/lib64/liblzmadec.so on my system).

Re: [gentoo-user] Only two people in the gentoo world is having this problem?

[Arttu V.]

On 3/10/10, Damian <damian.only@gmail.com> wrote:
> While ago I reported a bug regarding gvfs:
>     https://bugs.gentoo.org/show_bug.cgi?id=302196
>
> It's been unresolved for quite a long time now, so I was wondering if
> somebody could give me a hint on how to solve this problem.

Are you still using lzma-utils, or have you moved on to xz-utils?

Which package owns your /usr/lib64/liblzmadec.*? (equery belongs
foofile on Gentoo, dunno what is the equivalent on paludis)

-- 
Arttu V.

Re: [gentoo-user] Only two people in the gentoo world is having this problem?

[Damian]

On Wed, Mar 10, 2010 at 9:58 PM, Arttu V. <arttuv69@gmail.com> wrote:
> On 3/10/10, Damian <damian.only@gmail.com> wrote:
>> While ago I reported a bug regarding gvfs:
>>     https://bugs.gentoo.org/show_bug.cgi?id=302196
>>
>> It's been unresolved for quite a long time now, so I was wondering if
>> somebody could give me a hint on how to solve this problem.
>
> Are you still using lzma-utils, or have you moved on to xz-utils?
I'm using app-arch/xz-utils.

> Which package owns your /usr/lib64/liblzmadec.*? (equery belongs
> foofile on Gentoo, dunno what is the equivalent on paludis)
Acording to the output of `paludis --owner /usr/lib64/liblzmadec.la`
no package is the owner. I'm really lost right now...

Re: [gentoo-user] Only two people in the gentoo world is having this problem?

[Mark Knecht]

On Thu, Mar 11, 2010 at 7:03 AM, Damian <damian.only@gmail.com> wrote:
> On Wed, Mar 10, 2010 at 9:58 PM, Arttu V. <arttuv69@gmail.com> wrote:
>> On 3/10/10, Damian <damian.only@gmail.com> wrote:
>>> While ago I reported a bug regarding gvfs:
>>>     https://bugs.gentoo.org/show_bug.cgi?id=302196
>>>
>>> It's been unresolved for quite a long time now, so I was wondering if
>>> somebody could give me a hint on how to solve this problem.
>>
>> Are you still using lzma-utils, or have you moved on to xz-utils?
> I'm using app-arch/xz-utils.
>
>> Which package owns your /usr/lib64/liblzmadec.*? (equery belongs
>> foofile on Gentoo, dunno what is the equivalent on paludis)
> Acording to the output of `paludis --owner /usr/lib64/liblzmadec.la`
> no package is the owner. I'm really lost right now...
>
>

This happens when an ebuild doesn't remove packages as well as it installs them.

revdep-rebuild should be telling you that the machine is clean except
there are these extra files like /usr/lib64/liblzmadec.la.

equery belongs /usr/lib64/liblzmadec.la

tells you nothing owns it which means the original package isn't on
the system anymore.

Since we think /usr/lib64/liblzmadec.la comes from  lzma-utils we would use

equiery files  lzma-utils

to determine whether this package provides it. I cannot do that as I
don't have lzma-utils on my systems anymore.

If you don't have  lzma-utils on your system anymore then erase
/usr/lib64/liblzmadec.la by hand and run revdep-rebuild -ip again and
see if it's clean.

Hope this helps,
Mark

Re: [gentoo-user] Only two people in the gentoo world is having this problem?

[Arttu V.]

On 3/11/10, Mark Knecht <markknecht@gmail.com> wrote:
> to determine whether this package provides it. I cannot do that as I
> don't have lzma-utils on my systems anymore.

Well, that can be sort of done with, e.g.:

ebuild /usr/portage/app-arch/lzma-utils/lzma-utils-4.32.7.ebuild install

It will run emerge phases until the system creates the installation
image, but it won't merge the files into their proper locations in the
file system. Listing files in the image directory shows all the five
liblzmadec.* files (or symlinks) that would get installed.

> If you don't have  lzma-utils on your system anymore then erase
> /usr/lib64/liblzmadec.la by hand and run revdep-rebuild -ip again and
> see if it's clean.

Yes, this whole issue smells like an overblown orphaned .la-file
issue. Package manager cannot help much with such, and IMHO it's not a
bug (well maybe in the package manager, but let's not start that
flamewar ;) ).

Anyway, if it were me I'd nuke the file in a heartbeat, but if OP is
too timid for that, he can also quarantine the file first, i.e., move
it to some other path where it won't cause trouble (and then delete
later). Also, (from the bug) his libarchive.la seems to still list the
.la, so he should re-emerge libarchive after moving away the orphaned
.la-file (or use lafilefixer?).

Still, there is something funny with paludis, as so many people using
it seem to have so many problems with orphaned libtool archive files.
Ahem, even the warning from exherbo front page is gone nowadays. Is it
production quality now? o.O

-- 
Arttu V.

Re: [gentoo-user] Only two people in the gentoo world is having this problem?

[Mark Knecht]

On Thu, Mar 11, 2010 at 1:39 PM, Arttu V. <arttuv69@gmail.com> wrote:
> On 3/11/10, Mark Knecht <markknecht@gmail.com> wrote:
>> to determine whether this package provides it. I cannot do that as I
>> don't have lzma-utils on my systems anymore.
>
> Well, that can be sort of done with, e.g.:
>
> ebuild /usr/portage/app-arch/lzma-utils/lzma-utils-4.32.7.ebuild install
>
> It will run emerge phases until the system creates the installation
> image, but it won't merge the files into their proper locations in the
> file system. Listing files in the image directory shows all the five
> liblzmadec.* files (or symlinks) that would get installed.
>
>> If you don't have  lzma-utils on your system anymore then erase
>> /usr/lib64/liblzmadec.la by hand and run revdep-rebuild -ip again and
>> see if it's clean.
>
> Yes, this whole issue smells like an overblown orphaned .la-file
> issue. Package manager cannot help much with such, and IMHO it's not a
> bug (well maybe in the package manager, but let's not start that
> flamewar ;) ).
>
> Anyway, if it were me I'd nuke the file in a heartbeat, but if OP is
> too timid for that, he can also quarantine the file first, i.e., move
> it to some other path where it won't cause trouble (and then delete
> later). Also, (from the bug) his libarchive.la seems to still list the
> .la, so he should re-emerge libarchive after moving away the orphaned
> .la-file (or use lafilefixer?).
>
> Still, there is something funny with paludis, as so many people using
> it seem to have so many problems with orphaned libtool archive files.
> Ahem, even the warning from exherbo front page is gone nowadays. Is it
> production quality now? o.O
>
> --
> Arttu V.

Hi Arttu,
   I agree with pretty much everything you say although I don't know
anything about plaudis so nothing at all to say about that.

   I think the OP could also do

equery depends /usr/lib64/liblzmadec.la

and if that shows nothing is depending on it then it's certainly an
orphaned file and can be deleted. (Or safely moved...)

   I went through a period maybe 3-6 months ago where it seems I had a
dozen of these orphaned files on all my systems. I cleaned them up,
ran

emerge -DuN world
revdep-rebuild -i
eix-test-obsolete -d

and have been very clean since.

   Anyway, I do think it's a really big deal. He'll work his way through it.

Cheers,
Mark

Re: [gentoo-user] Only two people in the gentoo world is having this problem?

[Damian]

> Anyway, if it were me I'd nuke the file in a heartbeat, but if OP is
> too timid for that, he can also quarantine the file first, i.e., move
> it to some other path where it won't cause trouble (and then delete
> later). Also, (from the bug) his libarchive.la seems to still list the
> .la, so he should re-emerge libarchive after moving away the orphaned
> .la-file (or use lafilefixer?).
Ok, the OP will try this. If I cannot fix it I will just install gvfs
without the archive flag.

> Still, there is something funny with paludis, as so many people using
> it seem to have so many problems with orphaned libtool archive files.
> Ahem, even the warning from exherbo front page is gone nowadays. Is it
> production quality now? o.O
Actually, it is the first problem I have with .la files using paludis,
but I don't know about other people's experience.

Thanks a lot for your help,
Damian.

Re: [gentoo-user] Only two people in the gentoo world is having this problem?

[Damian]

On Fri, Mar 12, 2010 at 9:05 AM, Damian <damian.only@gmail.com> wrote:
>> Anyway, if it were me I'd nuke the file in a heartbeat, but if OP is
>> too timid for that, he can also quarantine the file first, i.e., move
>> it to some other path where it won't cause trouble (and then delete
>> later). Also, (from the bug) his libarchive.la seems to still list the
>> .la, so he should re-emerge libarchive after moving away the orphaned
>> .la-file (or use lafilefixer?).
> Ok, the OP will try this. If I cannot fix it I will just install gvfs
> without the archive flag.
Ok, so moving the file, reinstalling libarchive, and running
lafilefixer didn't change the situation.

So I'm using gvfs without the archive flag.

Thanks again,
Damain.

Re: [gentoo-user] Only two people in the gentoo world is having this problem?

[Arttu V.]

On 3/12/10, Damian <damian.only@gmail.com> wrote:
> On Fri, Mar 12, 2010 at 9:05 AM, Damian <damian.only@gmail.com> wrote:
>>> Anyway, if it were me I'd nuke the file in a heartbeat, but if OP is
>>> too timid for that, he can also quarantine the file first, i.e., move
>>> it to some other path where it won't cause trouble (and then delete
>>> later). Also, (from the bug) his libarchive.la seems to still list the
>>> .la, so he should re-emerge libarchive after moving away the orphaned
>>> .la-file (or use lafilefixer?).
>> Ok, the OP will try this. If I cannot fix it I will just install gvfs
>> without the archive flag.
> Ok, so moving the file, reinstalling libarchive, and running
> lafilefixer didn't change the situation.
>
> So I'm using gvfs without the archive flag.

Bummer. Are you sure your libarchive.la is not another orphan, just
like liblzmadec.la was?

Please check (if you are still interested in hunting down the cause).
You should probably only end up with that la file if you have
USE="static-libs" for libarchive -- which (if I'm reading correctly
the paludis output attached in the bug) you do not have currently
enabled.

But since you have the libarchive.la file on your system you may have
had the USE flag enabled at one point, or the ebuild may have changed
to allow separate dynamic and static building while your package
manager might not have kept up with its records.

So, also check the owner of libarchive.la, and clean up if necessary.
Actually, since you seem to run a great risk of having more than one
orphan .la-file then maybe you should do something like "find /usr
-name '*.la' | xargs -r equery belongs" or some such generic flush-out
of orphaned .la files.

-- 
Arttu V.

Re: [gentoo-user] Only two people in the gentoo world is having this problem?

[Damian]

Hi Arttu,

>> Ok, so moving the file, reinstalling libarchive, and running
>> lafilefixer didn't change the situation.
>>
>> So I'm using gvfs without the archive flag.
>
> Bummer. Are you sure your libarchive.la is not another orphan, just
> like liblzmadec.la was?
Indeed.  libarchive.la is not owned by any package. Is this a symptom
of a bigger problem?

> Please check (if you are still interested in hunting down the cause).
Sure, and I really appreciate the gentoo community help.

> You should probably only end up with that la file if you have
> USE="static-libs" for libarchive -- which (if I'm reading correctly
> the paludis output attached in the bug) you do not have currently
> enabled.
That's correct. Should I enable static-libs and recompile libarchive?

> But since you have the libarchive.la file on your system you may have
> had the USE flag enabled at one point, or the ebuild may have changed
> to allow separate dynamic and static building while your package
> manager might not have kept up with its records.
Ok, if that's the case I will report it to the paludis developers.

> So, also check the owner of libarchive.la, and clean up if necessary.
Ok, I just moved the library to the trash.

What I don't understand is how to orphaned la files can cause
compilation failures.

Thanks,
Damian.

Re: [gentoo-user] Only two people in the gentoo world is having this problem?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 449 bytes --]

On Fri, 12 Mar 2010 14:23:51 +0100, Damian wrote:

> Indeed.  libarchive.la is not owned by any package. Is this a symptom
> of a bigger problem?

It probably means you have run fix_libtool_files.sh, or possibly
lafilefixer, between installing and removing the package responsible for
that file. Emerge won't remove files it installed if they have been
subsequently modified.


-- 
Neil Bothwick

Top Oxymorons Number 31: Small crowd

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Only two people in the gentoo world is having this problem?

[Arttu V.]

On 3/12/10, Neil Bothwick <neil@digimed.co.uk> wrote:
> Emerge won't remove files it installed if they have been
> subsequently modified.

Just checking: anybody know how long has it been like this?

-- 
Arttu V.

Re: [gentoo-user] Only two people in the gentoo world is having this problem?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 392 bytes --]

On Fri, 12 Mar 2010 21:10:41 +0200, Arttu V. wrote:

> > Emerge won't remove files it installed if they have been
> > subsequently modified.  
> 
> Just checking: anybody know how long has it been like this?

I've been using Gentoo since 2003 and AFAIK it's been like that all this
time.


-- 
Neil Bothwick

Isn't it a bit unnerving that doctors call what they do "practice?"

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Only two people in the gentoo world is having this problem?

[Walter Dnes]

On Fri, Mar 12, 2010 at 01:57:44PM +0000, Neil Bothwick wrote

> It probably means you have run fix_libtool_files.sh, or possibly
> lafilefixer, between installing and removing the package responsible for
> that file. Emerge won't remove files it installed if they have been
> subsequently modified.

  Do they warn about it?  There are other circumstances where files are
deliberately not removed.  I just updated my netbook after 6 weeks, and
the media-libs/jpeg-8 ebuild put this in my /var/log/portage/elog (note;
configuration in /etc/make.conf required)

====================================================================
WARN: postinst
Old versions of installed libraries were detected on your system.
In order to avoid breaking packages that depend on these old libs,
the libraries are not being removed.  You need to run revdep-rebuild
in order to remove these old dependencies.  If you do not have this
helper program, simply emerge the 'gentoolkit' package.

  # revdep-rebuild --library libjpeg.so.7

Once you've finished running revdep-rebuild, it should be safe to
delete the old libraries.  Here is a copy & paste for the lazy:
  # rm '/usr/lib/libjpeg.so.7'
====================================================================

-- 
Walter Dnes <waltdnes@waltdnes.org>

Re: [gentoo-user] Only two people in the gentoo world is having this problem?

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 702 bytes --]

On Fri, 12 Mar 2010 21:26:23 -0500, Walter Dnes wrote:

> > It probably means you have run fix_libtool_files.sh, or possibly
> > lafilefixer, between installing and removing the package responsible
> > for that file. Emerge won't remove files it installed if they have
> > been subsequently modified.  
> 
>   Do they warn about
> it? 

No, it's a simple rule: if portage didn't put the file there, portage
won't remove it. It is also a sensible rule (IMO) but it can lead to .la
files being orphaned (which is more a problem with the whole .la thing).
I'd rather that than have portage delete my customisations.


-- 
Neil Bothwick

Last yur I kudnt spel modjerater now I are won.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Only two people in the gentoo world is having this problem?

[Arttu V.]

On 3/12/10, Damian <damian.only@gmail.com> wrote:
>> Bummer. Are you sure your libarchive.la is not another orphan, just
>> like liblzmadec.la was?
> Indeed.  libarchive.la is not owned by any package. Is this a symptom
> of a bigger problem?

Probably not, unless running Gentoo is considered a big problem. :)

You can read many things about the problems of dynamic vs static
linking from, e.g., flameeyes' blog.

>> Please check (if you are still interested in hunting down the cause).
> Sure, and I really appreciate the gentoo community help.

Ah, I got the impression that you might have been satisfied with USE="-lzma".

>> You should probably only end up with that la file if you have
>> USE="static-libs" for libarchive -- which (if I'm reading correctly
>> the paludis output attached in the bug) you do not have currently
>> enabled.
> That's correct. Should I enable static-libs and recompile libarchive?

I don't think so, but I don't know what your system is for. If the box
currently runs without the static libs then I'd guess you don't need
them. I think you might want to hear a third opinion, if someone else
has one to lend.

>> But since you have the libarchive.la file on your system you may have
>> had the USE flag enabled at one point, or the ebuild may have changed
>> to allow separate dynamic and static building while your package
>> manager might not have kept up with its records.
> Ok, if that's the case I will report it to the paludis developers.

Given Neil's comment I think it might not be a bug, but rather a nasty
"feature", apparently of portage as well (that was news to me).

-- 
Arttu V.