<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>12557</bug_id>
          
          <creation_ts>2002-12-22 07:29 0000</creation_ts>
          <short_desc>app-arch/rar version bump to 3.1</short_desc>
          <delta_ts>2003-02-04 19:42:18 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Unspecified</component>
          <version>1.4_rc1</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>CLOSED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>ronald@hummelink.net</reporter>
          <assigned_to>bug-wranglers@gentoo.org</assigned_to>
          

      

      
          <long_desc isprivate="0">
            <who>ronald@hummelink.net</who>
            <bug_when>2002-12-22 07:29:01 0000</bug_when>
            <thetext>Rar is precompiled by rarlabs aparently using gcc 2.95.x and linked verses
libstdc++-libc6.2-2.so.3
That causes rar and unrar installed by the ebuild unrunnable on pure gcc 3
systems. rarlabs distributes rar_static, a static linked binary which is usable
in a gcc 3 system. I would only install rar_static as rar on pure gcc3 systems
as the dynamic rar and unrar are useless.
Also rar 3.1.0 was released, only requires a rename of the ebuild and its go.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>vapier@gentoo.org</who>
            <bug_when>2002-12-22 14:15:10 0000</bug_when>
            <thetext>install lib-compat-1.1</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>ronald@hummelink.net</who>
            <bug_when>2002-12-22 14:45:50 0000</bug_when>
            <thetext>lib-compat does make this work, however for pure gcc 3 systems (like upcoming
gentoo 1.4), lib-compat should be a depend then for this package, as else this
package will not work properly (I do not think a user shoud manually install
lib-compat to make this work)</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>seemant@gentoo.org</who>
            <bug_when>2002-12-23 13:25:12 0000</bug_when>
            <thetext>lib-compat added as a DEPEND.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>seemant@gentoo.org</who>
            <bug_when>2002-12-23 13:29:13 0000</bug_when>
            <thetext>added to portage.

thanks for the heads up.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>ronald@hummelink.net</who>
            <bug_when>2002-12-23 17:40:06 0000</bug_when>
            <thetext>No problem, glad I can help out a little.

As test unmerged rar and lib-compat. emerging masked rar 3.1.0 installs
lib-compat fine and rar seems to work fine. Marking closed.</thetext>
          </long_desc>
      
    </bug>

</bugzilla>