<?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>33123</bug_id>
          
          <creation_ts>2003-11-10 00:39 0000</creation_ts>
          <short_desc>im-ja version 0.8 now includes XIM (distfile needs new digest)</short_desc>
          <delta_ts>2003-12-13 07:30:57 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>Applications</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>plate@gentoo.org</reporter>
          <assigned_to>cjk@gentoo.org</assigned_to>
          

      

      
          <long_desc isprivate="0">
            <who>plate@gentoo.org</who>
            <bug_when>2003-11-10 00:39:45 0000</bug_when>
            <thetext>Yesterday the developer of im-ja has announced xim support
for non-GTK-applications. This being great in itself, he
unfortunately hasn&apos;t changed the version number, meaning 
the old tarball named im-ja-0.8.tar.gz is not the same as 
the one residing at the ebuild&apos;s SRC_URI now.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>usata@gentoo.org</who>
            <bug_when>2003-11-10 03:20:19 0000</bug_when>
            <thetext>Can you show exactly the SRC_URI where we can get the sourcetarball? I&apos;ve
just fetched im-ja from http://im-ja.sourceforge.net/im-ja-0.8.tar.gzbut
it has the same MD5 as in /usr/portage/app-i18n/im-ja/files/digest-im-ja-0.8.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>plate@gentoo.org</who>
            <bug_when>2003-11-10 03:37:41 0000</bug_when>
            <thetext>Of course. The new tarball is here: http://siliconium.net/~boti/im-ja/im-ja-0.8.tar.gz


Check http://www.tlug.jp/ML/0311/msg00056.html for the 
announcement and a few details on what B0Ti did. ID &amp; 
password for the mailing list archive are: http://www.tlug.jp/images/tlug-pword.png.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>usata@gentoo.org</who>
            <bug_when>2003-11-10 06:27:53 0000</bug_when>
            <thetext>yakina, what do you think about making an ebuild with a different
name, say, im-ja-0.9_alpha20031109.ebuild ?
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>plate@gentoo.org</who>
            <bug_when>2003-11-11 01:43:54 0000</bug_when>
            <thetext>Coincidentally, this is what the author implicitly seems to 
recommend. :) Quoting http://www.tlug.jp/ML/0311/msg00061.html:

&quot;The official v0.8 release (from September) available from SF 
doesn&apos;t have any xim support, I was just too lazy to bump the 
version number for this preview release  to 0.9-alpha. I&apos;d want 
to wait pushing this into portage until it&apos;s released as 0.9.&quot;

Sorry to have started this unnecessary precipitation...</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>usata@gentoo.org</who>
            <bug_when>2003-12-13 07:30:57 0000</bug_when>
            <thetext>I&apos;ve just included it as im-ja-0.9_alpha20031109.ebuild.  It is masked
until the next 0.9 release, so if you are interested in trying it,
unmask it using /etc/portage/package.unmask and then emerge.
Thanks for reporting.
</thetext>
          </long_desc>
      
    </bug>

</bugzilla>