<?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>178690</bug_id>
          
          <creation_ts>2007-05-15 21:33 0000</creation_ts>
          <short_desc>Stabilise app-text/aspell-0.60.5 and dicts (for KDE 3.5.7 stabilization)</short_desc>
          <delta_ts>2007-08-25 22:43:41 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>Ebuilds</component>
          <version>unspecified</version>
          <rep_platform>All</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <keywords>STABLEREQ</keywords>
          <priority>P2</priority>
          <bug_severity>blocker</bug_severity>
          <target_milestone>---</target_milestone>
          <dependson>178199</dependson>
          <blocked>176297</blocked>
    
    <blocked>177707</blocked>
          
          <everconfirmed>1</everconfirmed>
          <reporter>carlo@gentoo.org</reporter>
          <assigned_to>app-dicts@gentoo.org</assigned_to>
          <cc>alonbl@gentoo.org</cc>
    
    <cc>cryos@gentoo.org</cc>
    
    <cc>damian01w@gmail.com</cc>
    
    <cc>juantxorena@gmail.com</cc>
    
    <cc>simon@siemonsma.name</cc>

      

      
          <long_desc isprivate="0">
            <who>carlo@gentoo.org</who>
            <bug_when>2007-05-15 21:33:36 0000</bug_when>
            <thetext>More exactly we need app-text/aspell-0.60.5 andd app-dicts/aspell-en-6.0.0, but I guess users will complain, if the other dictionaries won&apos;t go stable as well.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>cycoone@hotmail.com</who>
            <bug_when>2007-06-27 23:27:08 0000</bug_when>
            <thetext>Is anyone looking at this, app-text/aspell-0.60.5 has been out since the beginning of March and the only bug in that time afaik is 178199 which should be a quick fix.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>juantxorena@gmail.com</who>
            <bug_when>2007-07-05 18:45:24 0000</bug_when>
            <thetext>Hello? Is somebody of app-dicts team here?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>cryos@gentoo.org</who>
            <bug_when>2007-07-09 20:17:39 0000</bug_when>
            <thetext>Well time has moved on and the KDE herd are now looking at the stabilisation of KDE 3.5.7. We need this version stable for 3.5.7 too - is there any reason why this is not possible? Is there something we could do to help with this?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>cryos@gentoo.org</who>
            <bug_when>2007-07-15 16:17:28 0000</bug_when>
            <thetext>Is there any reason we cannot stabilise this version? It is a dependency for KDE 3.5.7 stabilisation and we would like to stabilise very soon but cannot afford to lose spell checking. I would appreciate some feedback if there would be issues in us asking for this version of aspell to be stabilised. Thanks.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>juantxorena@gmail.com</who>
            <bug_when>2007-07-15 17:06:40 0000</bug_when>
            <thetext>(In reply to comment #4)
&gt; Is there any reason we cannot stabilise this version? It is a dependency for
&gt; KDE 3.5.7 stabilisation and we would like to stabilise very soon but cannot
&gt; afford to lose spell checking. I would appreciate some feedback if there would
&gt; be issues in us asking for this version of aspell to be stabilised. Thanks.
&gt; 

It seems that this bug depends on another one (Bug 178199) that must be solved first.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>cryos@gentoo.org</who>
            <bug_when>2007-07-15 17:16:11 0000</bug_when>
            <thetext>It would be good to solve that but it is not a regression as far as I can tell, i.e. the new version is not doing anything wrong that isn&apos;t already broken. Therefore it would still be useful to stabilise the new version so that we can stabilise. I am not sure on the correct response to the other bug - I thought it was a design decision of the ebuilds that users should emerge the dictionary.

Personally I am most interested in moving forward and getting the latest version of KDE stable as it has already been significantly delayed. If it is not a regression I don&apos;t think it should block us from stabilising. It would be good to hear what the maintainers think if any of them are around.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>juantxorena@gmail.com</who>
            <bug_when>2007-07-20 19:21:42 0000</bug_when>
            <thetext>If Bug #178199 is not a regression, then this one shouldn&apos;t depend on that one, and should be fixed easily, don&apos;t you think, app-dicts?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>juantxorena@gmail.com</who>
            <bug_when>2007-07-26 11:12:03 0000</bug_when>
            <thetext>app-dicts, come on, stabilize this, the bug was opened two months ago and there is no reason to not stabilize this. Maybe priority should be upgraded to P1.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>carlo@gentoo.org</who>
            <bug_when>2007-07-30 18:23:53 0000</bug_when>
            <thetext>Dear dictionary team, do we have to take this in our hands, shall we escalate in some way or what? Do you care to respond - finally!?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>philantrop@gentoo.org</who>
            <bug_when>2007-07-30 18:30:52 0000</bug_when>
            <thetext> (In reply to comment #9)
&gt; Dear dictionary team, do we have to take this in our hands, shall we escalate in
&gt; some way or what? Do you care to respond - finally!?

Carlo, I&apos;ve spoken with the app-dicts team who have a very serious staffing problem. I&apos;ve joined the herd and will try to sort out the issues blocking this bug ASAP.

I don&apos;t see this as a blocker for our KDE stabilisation, though. Or did I miss something?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>philantrop@gentoo.org</who>
            <bug_when>2007-08-04 14:47:50 0000</bug_when>
            <thetext>All issues have been resolved. Arch teams, please stabilise the following packages:

app-text/aspell-0.60.5
app-dicts/aspell-en-6.0.0
app-dicts/aspell-et-0.1.21.1
app-dicts/aspell-he-1.0.0
app-dicts/aspell-sr-0.60
app-dicts/aspell-fi-0.7.0
app-dicts/aspell-vi-0.01.1.1
app-dicts/aspell-ca-0.60.20040130
app-dicts/aspell-cs-0.60.20040614
app-dicts/aspell-pl-6.0.20061121.0
app-dicts/aspell-uk-1.4.0.0
app-dicts/aspell-de-0.60_pre20030222
app-dicts/aspell-it-2.2.20050523
app-dicts/aspell-ru-0.99.1

All app-dicts/* are basically just text files so even though some haven&apos;t been in for the customary 30 days, their stabilisation shouldn&apos;t be a problem, so please do it. Plus, we&apos;d like to have it stable for KDE 3.5.7. (see the blocked KDE bug) :-)</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>tanderson@gentoo.org</who>
            <bug_when>2007-08-04 15:28:21 0000</bug_when>
            <thetext>====amd64====

I can verify that aspell and aspell-en work, but I don&apos;t know words in any of the other listed languages. Here&apos;s my emerge --info. Sorry for using baselayout-2.0.0_rc1 but I am testing stuff for Uberlord and didn&apos;t want to switch back so quickly.

Portage 2.1.2.9 (default-linux/amd64/2007.0, gcc-4.1.2, glibc-2.5-r4, 2.6.20-gentoo-r7 x86_64)
=================================================================
System uname: 2.6.20-gentoo-r7 x86_64 unknown
Gentoo Base System release 2.0.0_rc1
Timestamp of tree: Thu, 02 Aug 2007 19:01:01 +0000
ccache version 2.4 [enabled]
dev-java/java-config: 1.3.7, 2.0.33-r1
dev-lang/python:     2.4.4-r4
dev-python/pycrypto: 2.0.1-r6
dev-util/ccache:     2.4-r7
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.61
sys-devel/automake:  1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
sys-devel/binutils:  2.17
sys-devel/gcc-config: 1.3.16
sys-devel/libtool:   1.5.23b
virtual/os-headers:  2.6.21
ACCEPT_KEYWORDS=&quot;amd64&quot;
AUTOCLEAN=&quot;yes&quot;
CBUILD=&quot;x86_64-pc-linux-gnu&quot;
CFLAGS=&quot;-march=athlon64 -O2 -pipe&quot;
CHOST=&quot;x86_64-pc-linux-gnu&quot;
CONFIG_PROTECT=&quot;/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config&quot;
CONFIG_PROTECT_MASK=&quot;/etc/env.d /etc/env.d/java/ /etc/gconf /etc/revdep-rebuild /etc/terminfo&quot;
CXXFLAGS=&quot;-march=athlon64 -O2 -pipe&quot;
DISTDIR=&quot;/distfiles&quot;
FEATURES=&quot;ccache collision-protect distlocks metadata-transfer multilib-strict parallel-fetch sandbox sfperms strict test userpriv&quot;
GENTOO_MIRRORS=&quot;http://mirrors.acm.cs.rpi.edu/gentoo/ http://distfiles.gentoo.org/&quot;
MAKEOPTS=&quot;-j2&quot;
PKGDIR=&quot;/usr/portage/packages&quot;
PORTAGE_RSYNC_OPTS=&quot;--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*&quot;
PORTAGE_TMPDIR=&quot;/var/tmp&quot;
PORTDIR=&quot;/usr/portage&quot;
PORTDIR_OVERLAY=&quot;/overlay&quot;
SYNC=&quot;rsync://kv80/gentoo-portage&quot;
USE=&quot;X acl aiglx aim amd64 berkdb bitmap-fonts branding cli cracklib crypt cups dri fortran gdbm gpm gtk iconv imap ipv6 isdnlog libg++ midi mmx mpeg3 mudflap ncurses nls nptl nptlonly nvidia opengl openmp pam pcre perl pppd python qt3 readline reflection session sockets spl sqlite3 sse sse2 ssl tcpd test truetype-fonts type1-fonts unicode vim xcomposite xine xorg zlib&quot; ALSA_CARDS=&quot;ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci&quot; ALSA_PCM_PLUGINS=&quot;adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol&quot; ELIBC=&quot;glibc&quot; INPUT_DEVICES=&quot;keyboard mouse evdev&quot; KERNEL=&quot;linux&quot; LCD_DEVICES=&quot;bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text&quot; USERLAND=&quot;GNU&quot; VIDEO_CARDS=&quot;nvidia&quot;
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>philantrop@gentoo.org</who>
            <bug_when>2007-08-04 17:18:45 0000</bug_when>
            <thetext>Marked stable on amd64. Thanks, Thomas!</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>fmccor@gentoo.org</who>
            <bug_when>2007-08-04 19:09:22 0000</bug_when>
            <thetext>All stable on sparc.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>madxray@gmx.net</who>
            <bug_when>2007-08-04 21:48:47 0000</bug_when>
            <thetext>(In reply to comment #13)
&gt; Marked stable on amd64. Thanks, Thomas!
dependency

!=app-dicts/aspell-en-0.5*

caused problems during emerge world.

change to

&gt;=app-dicts/aspell-en-0.6

fixed it for me.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>philantrop@gentoo.org</who>
            <bug_when>2007-08-04 22:12:43 0000</bug_when>
            <thetext>As would have a simple &quot;emerge -C =app-dicts/aspell-en-0.5*&quot;. :-)</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>cryos@gentoo.org</who>
            <bug_when>2007-08-05 10:52:11 0000</bug_when>
            <thetext>I have to admit I don&apos;t get what the blocking nets us? If we depend on &gt; or &gt;= it forces portage to upgrade before this package right? Isn&apos;t that better than forcing users to unmerge old packages? This seems to be something that is happening with more and more packages and where it can be avoided I think it should until portage begins to automatically unmerge and then merge the new version (if this is ever really necessary). If I am totally wrong I would love to know why - may be this belongs on -dev rather than here though?

Back to finishing my thesis anyway.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>nixnut@gentoo.org</who>
            <bug_when>2007-08-05 11:25:19 0000</bug_when>
            <thetext>stable on ppc</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>armin76@gentoo.org</who>
            <bug_when>2007-08-05 14:47:47 0000</bug_when>
            <thetext>alpha/ia64/x86 stable</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>kumba@gentoo.org</who>
            <bug_when>2007-08-06 03:45:54 0000</bug_when>
            <thetext>mips stable.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>corsair@gentoo.org</who>
            <bug_when>2007-08-09 16:33:50 0000</bug_when>
            <thetext>ppc64  stable</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>jer@gentoo.org</who>
            <bug_when>2007-08-10 05:16:22 0000</bug_when>
            <thetext>Stable for HPPA.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>philantrop@gentoo.org</who>
            <bug_when>2007-08-25 22:43:41 0000</bug_when>
            <thetext>We&apos;re done here now. Thanks, guys!</thetext>
          </long_desc>
      
    </bug>

</bugzilla>