Bug 7810 - All ispell-NON-ENGLISH-3.1.20-22 packages are broken
Summary: All ispell-NON-ENGLISH-3.1.20-22 packages are broken
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: ispell
Version: 6.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-12-15 08:03 UTC by grtodd
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2000-04-10 15:25:59 UTC

Attachments (Terms of Use)

Description grtodd 1999-12-15 08:03:55 UTC
Various ispell-LANGUAGE-3.1.20-22 packages broken and will not build with
supplied src.rpm package.  The required

To see a list of all the improperly built packages simply mount the CD on
/mnt/cdrom and do:

for i in `/bin/ls /mnt/cdrom/RedHat/RPMS/ispell-[a-z]*`; do rpm -Vp $i

Or after rebuilding the src.rpms:

for i in `/bin/ls /usr/src/redhat/RPMS/i386/ispell-[a-z]*`; do rpm -Vp $i

The spec file and build/Makefile system are preventing non-english
(american and british) .hash and .aff files from being built. However all
the non-Englis dictionaries are included in the source.

Please fix.

Comment 1 grtodd 1999-12-15 08:08:59 UTC
See also bug #4960 - perhaps other hash files (eg. the medical terms?) aren't
being built.

Comment 2 grtodd 1999-12-16 02:33:59 UTC
Looked at this again quickly - running the build in the source tree and adding
{languages} to LANGUAGE in local.h seems to work (all the *.aff and *.hash files
get built and installed), but building using the ispell.spec breaks something.
Perhaps %_install_langs or LINGUAS or LANG can fix this?

The build process aside the main issue is that all the current distributed
non-english ispell packages are non-functional (those on my CD and at mirror
sites that I checked).

BTW just for clarity, the rpm -Vp commands show the missing files if you run
them against the package files *after* you have them installed. When this is
done they will list the missing files.

Note You need to log in before you can comment on or make changes to this bug.