Summary: | Stabilise app-text/aspell-0.60.5 and dicts (for KDE 3.5.7 stabilization) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Carsten Lohrke (RETIRED) <carlo> |
Component: | New packages | Assignee: | Spell checking utilities and dictionaries -- related bugs (OBSOLETE) <app-dicts+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | alonbl, cryos, damian01w, juantxorena, simon |
Priority: | High | Keywords: | STABLEREQ |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 178199 | ||
Bug Blocks: | 176297, 177707 |
Description
Carsten Lohrke (RETIRED)
2007-05-15 21:33:36 UTC
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. Hello? Is somebody of app-dicts team here? 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? 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. (In reply to comment #4) > 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. > It seems that this bug depends on another one (Bug 178199) that must be solved first. 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'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't think it should block us from stabilising. It would be good to hear what the maintainers think if any of them are around. If Bug #178199 is not a regression, then this one shouldn't depend on that one, and should be fixed easily, don't you think, app-dicts? 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. 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!? (In reply to comment #9) > 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!? Carlo, I've spoken with the app-dicts team who have a very serious staffing problem. I've joined the herd and will try to sort out the issues blocking this bug ASAP. I don't see this as a blocker for our KDE stabilisation, though. Or did I miss something? 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't been in for the customary 30 days, their stabilisation shouldn't be a problem, so please do it. Plus, we'd like to have it stable for KDE 3.5.7. (see the blocked KDE bug) :-) ====amd64==== I can verify that aspell and aspell-en work, but I don't know words in any of the other listed languages. Here's my emerge --info. Sorry for using baselayout-2.0.0_rc1 but I am testing stuff for Uberlord and didn'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="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=athlon64 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-march=athlon64 -O2 -pipe" DISTDIR="/distfiles" FEATURES="ccache collision-protect distlocks metadata-transfer multilib-strict parallel-fetch sandbox sfperms strict test userpriv" GENTOO_MIRRORS="http://mirrors.acm.cs.rpi.edu/gentoo/ http://distfiles.gentoo.org/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--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-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/overlay" SYNC="rsync://kv80/gentoo-portage" USE="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" ALSA_CARDS="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" ALSA_PCM_PLUGINS="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" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="nvidia" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS Marked stable on amd64. Thanks, Thomas! All stable on sparc. (In reply to comment #13) > Marked stable on amd64. Thanks, Thomas! dependency !=app-dicts/aspell-en-0.5* caused problems during emerge world. change to >=app-dicts/aspell-en-0.6 fixed it for me. As would have a simple "emerge -C =app-dicts/aspell-en-0.5*". :-) I have to admit I don't get what the blocking nets us? If we depend on > or >= it forces portage to upgrade before this package right? Isn'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. stable on ppc alpha/ia64/x86 stable mips stable. ppc64 stable Stable for HPPA. We're done here now. Thanks, guys! |