<?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>188542</bug_id>
          
          <creation_ts>2007-08-12 08:36 0000</creation_ts>
          <short_desc>file collision between app-arch/fastjar-0.95 and dev-java/kaffe-1.1.7-r5</short_desc>
          <delta_ts>2007-08-15 09:23:58 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>Java</component>
          <version>unspecified</version>
          <rep_platform>All</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>caster@gentoo.org</reporter>
          <assigned_to>java@gentoo.org</assigned_to>
          <cc>robilad@kaffe.org</cc>
    
    <cc>zmedico@gentoo.org</cc>

      

      
          <long_desc isprivate="0">
            <who>caster@gentoo.org</who>
            <bug_when>2007-08-12 08:36:26 0000</bug_when>
            <thetext>package app-arch/fastjar-0.95 NOT merged

Searching all installed packages for file collisions...
Press Ctrl-C to Stop

 * dev-java/kaffe-1.1.7-r5:

     &apos;/usr/share/info/fastjar.info.bz2&apos;
     &apos;/usr/share/man/man1/fastjar.1.bz2&apos;

Given that kaffe depends on fastjar, fastjar package&apos;s man and info should stay and kaffe&apos;s copy should go... possibly replace even kaffe&apos;s own fastjar binary with symlink to system fastjar and make it a RDEPEND?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>betelgeuse@gentoo.org</who>
            <bug_when>2007-08-12 09:17:58 0000</bug_when>
            <thetext>-r6 now uses system copies of zlib and fastjar. There is a bug in kaffe with --disable-fastjar that it does not make the jar wrapper point to system fastjar. I will need to see with dalibor to report this. For now I just used dosym.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>zmedico@gentoo.org</who>
            <bug_when>2007-08-15 06:47:50 0000</bug_when>
            <thetext>Is there any reason why we don&apos;t make app-arch/fastjar-0.95 block &lt;=dev-java/kaffe-1.1.7-r5?  That way the kaffe-1.1.7-r6 upgrade will happen before the fastjar-0.95 upgrade when necessary, preventing the user from experiencing a file collision.

[ebuild     U ] dev-java/kaffe-1.1.7-r6 [1.1.7-r5] USE=&quot;alsa esd gmp gtk nls&quot; 0 kB
[ebuild     U ] app-arch/fastjar-0.95 [0.94] 0 kB [1]

I don&apos;t see the blocker causing any problems, but maybe I&apos;m missing something.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>caster@gentoo.org</who>
            <bug_when>2007-08-15 08:45:41 0000</bug_when>
            <thetext>Yeah I also had the wrong order and wondered bout this. If portage is smart enough, why not.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>caster@gentoo.org</who>
            <bug_when>2007-08-15 09:23:58 0000</bug_when>
            <thetext>Ok, so app-arch/fastjar-0.95 blocks
&lt;=dev-java/kaffe-1.1.7-r5 in RDEPEND, seems to help, kaffe is now upgraded first.
Also, all kaffe versions &lt;=1.1.7-r6 block on &gt;=app-arch/fastjar-0.95 in RDEPEND, to be sure people don&apos;t install new fastjar and then old kaffe.

Now we just have to remember we need to stabilize kaffe -r6 before fastjar 0.95...</thetext>
          </long_desc>
      
    </bug>

</bugzilla>