Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#22275 - [hunspell-it] v. 2.4-1 bad flagvector error

Attached to Project: Arch Linux
Opened by speps (archspeps) - Saturday, 01 January 2011, 17:45 GMT
Last edited by Andrea Scarpino (BaSh) - Sunday, 02 January 2011, 01:15 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andrea Scarpino (BaSh)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Hunspell reports the annoying bad flagvector error while reading
the /usr/share/hunspell/it_IT.dic dictionary file.
The lines with just "/" causes the problem.

I'm the previous hunspell-it AUR maintainer,
and already solved this in my ex PKGBUILD with:

# Fix dic file empty lines
sed '/^\/$/d' -i it_IT.dic

Probably when Andrea ported this into EXTRA didn't noticed that line.

Additional info:
Package version affected ==> 2.4-1

Steps to reproduce:
$ hunspell
error: line 3: bad flagvector
error: line 7: bad flagvector
error: line 10: bad flagvector
error: line 12: bad flagvector
error: line 14: bad flagvector
error: line 16: bad flagvector
error: line 21: bad flagvector
error: line 26: bad flagvector
Hunspell 1.2.12 - 2.4 (01/09/2007)
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Sunday, 02 January 2011, 01:15 GMT
Reason for closing:  Fixed
Additional comments about closing:  hunspell-it 2.4-2
Comment by Ionut Biru (wonder) - Saturday, 01 January 2011, 17:50 GMT
@Andrea Andy wants to have on all hunspell-foo packages optdepends=hunspell and not as dependency. Take a look at hunspell-de
Comment by speps (archspeps) - Saturday, 01 January 2011, 18:01 GMT
Also, maybe a little OT:
@Andy IMHO hunspell-en should add provides and conflicts on 'hunspell-en-gb' && 'hunspell-en-us'
I'm the previous maintainer of hunspell-en-gb and this conflicts with hunspell-en.

I suppose other users will encounter the same issue, so for the first times this could be useful. Cheers

Loading...