[opensuse-packaging] rpmlint - non-utf8-spec-file ?

What does this mean: RPMLINT report: =============== jfsutils.src: W: non-utf8-spec-file /tmp/rpmlint.jfsutils-1.1.15-1.src.rpm.zuUJ47/jfsutils.spec The character encoding of the spec file is not UTF-8. Convert it for example using iconv(1). The spec file contains only US-ASCII, I've checked. What does rpmlint know that I don't? -- Per Jessen, Zürich (14.6°C) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Quoting Per Jessen <per@opensuse.org>:
What does this mean:
RPMLINT report: ===============
jfsutils.src: W: non-utf8-spec-file /tmp/rpmlint.jfsutils-1.1.15-1.src.rpm.zuUJ47/jfsutils.spec The character encoding of the spec file is not UTF-8. Convert it for example using iconv(1).
The spec file contains only US-ASCII, I've checked. What does rpmlint know that I don't?
This is very likely in this case a non-UTF8 character in jfsutils.changes. Bare in mind that build is merging the changes into the %changelog section of the .spec file and the resulting file (as is being injected into the .src.rpm) is being checked on UTF8 compatibility. Dominique -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Quoting "Dominique Leuenberger a.k.a DimStar" <dimstar@opensuse.org>:
Quoting Per Jessen <per@opensuse.org>: This is very likely in this case a non-UTF8 character in jfsutils.changes.
Bare in mind that build is merging the changes into the %changelog section of the .spec file and the resulting file (as is being injected into the .src.rpm) is being checked on UTF8 compatibility.
Just a small follow up: The error/warning has been there for a while I guess: $> iconv -f ISO-8859-8 -t UTF-8 jfsutils.spec > converted.spec $> diff jfsutils.spec converted.spec 187,191c187,191 < � fix undefined reference to errno < � allow jfs_mkfs to run on regular file < � fix for-loop going past last element of vopen array < � sanity checking on variable this_ag < � s_label displayed incorrectly when 16 chars long ---
· fix undefined reference to errno · allow jfs_mkfs to run on regular file · fix for-loop going past last element of vopen array · sanity checking on variable this_ag · s_label displayed incorrectly when 16 chars long 194,195c194,195 < � fix segmentation fault in mkfs.jfs when given bad block device < � fix jfs_debugfs to display directory index with directory entries
· fix segmentation fault in mkfs.jfs when given bad block device · fix jfs_debugfs to display directory index with directory entries
so those are the lines you were looking for :) Dominique -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Dominique Leuenberger a.k.a DimStar wrote:
Quoting "Dominique Leuenberger a.k.a DimStar" <dimstar@opensuse.org>:
Quoting Per Jessen <per@opensuse.org>: This is very likely in this case a non-UTF8 character in jfsutils.changes.
Bare in mind that build is merging the changes into the %changelog section of the .spec file and the resulting file (as is being injected into the .src.rpm) is being checked on UTF8 compatibility.
Just a small follow up: The error/warning has been there for a while I guess:
Yeah, since 2006 by the looks of it. :-) Thanks, I didn't know jfsutils.changes was being checked here too. -- Per Jessen, Zürich (15.0°C) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

On Apr 01, 11 12:27:55 +0200, Dominique Leuenberger a.k.a DimStar wrote:
Quoting "Dominique Leuenberger a.k.a DimStar" <dimstar@opensuse.org>:
Quoting Per Jessen <per@opensuse.org>: This is very likely in this case a non-UTF8 character in jfsutils.changes.
The original error message was misleading: ] non-utf8-spec-file /tmp/rpmlint.jfsutils-1.1.15-1.src.rpm.zuUJ47/jfsutils.spec ] The character encoding of the spec file is not UTF-8. Convert it for ] example using iconv(1). Can we change this to say e.g. ] non-utf8-spec-file /tmp/rpmlint.jfsutils-1.1.15-1.src.rpm.zuUJ47/jfsutils.spec ] The character encoding of the spec file (or merged changes file) is not UTF-8. ] Convert it for example using iconv(1). Per, would that have helped? cheers, JW- -- o \ Juergen Weigert paint it green! __/ _=======.=======_ <V> | jw@suse.de back to ascii! __/ _---|____________\/ \ | 0911 74053-508 __/ (____/ /\ (/) | _____________________________/ _/ \_ vim:set sw=2 wm=8 SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) SuSE. Supporting Linux since 1992. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Juergen Weigert wrote:
On Apr 01, 11 12:27:55 +0200, Dominique Leuenberger a.k.a DimStar wrote:
Quoting "Dominique Leuenberger a.k.a DimStar" <dimstar@opensuse.org>:
Quoting Per Jessen <per@opensuse.org>: This is very likely in this case a non-UTF8 character in jfsutils.changes.
The original error message was misleading: ] non-utf8-spec-file /tmp/rpmlint.jfsutils-1.1.15-1.src.rpm.zuUJ47/jfsutils.spec ] The character encoding of the spec file is not UTF-8. Convert it for ] example using iconv(1).
Can we change this to say e.g. ] non-utf8-spec-file /tmp/rpmlint.jfsutils-1.1.15-1.src.rpm.zuUJ47/jfsutils.spec ] The character encoding of the spec file (or merged changes file) is not UTF-8. ] Convert it for example using iconv(1).
Per, would that have helped?
That would have given me a better idea, yes. I'm pretty certain I would have spotted the problem if I had known to look in the changes file too. /Per -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Hello, looks like this was somehow forgotten/overlooked... Dirk, can you change the rpmlint message (see below) or do I need to open a bugreport? ;-) (No response until wednesday will result in a bugreport.) on Freitag, 1. April 2011, Per Jessen wrote:
Juergen Weigert wrote:
On Apr 01, 11 12:27:55 +0200, Dominique Leuenberger a.k.a DimStar wrote:
Quoting "Dominique Leuenberger a.k.a DimStar" :
Quoting Per Jessen <per@opensuse.org>: This is very likely in this case a non-UTF8 character in jfsutils.changes.
The original error message was misleading: ] non-utf8-spec-file /tmp/rpmlint.jfsutils-1.1.15-1.src.rpm.zuUJ47/jfsutils.spec ] The character encoding of the spec file is not UTF-8. Convert it for ] example using iconv(1).
Can we change this to say e.g. ] non-utf8-spec-file /tmp/rpmlint.jfsutils-1.1.15-1.src.rpm.zuUJ47/jfsutils.spec ] The character encoding of the spec file (or merged changes file) is not UTF-8. ] Convert it for example using iconv(1).
Per, would that have helped?
That would have given me a better idea, yes. I'm pretty certain I would have spotted the problem if I had known to look in the changes file too.
Regards, Christian Boltz -- Ich habe es satt, gegen die YaSTs [Linuxconfs, ...] dieser Welt zu kämpfen, die schlauer sein wollen als ich. Ich will keine "Bootgrafiken", die die bösen, hässlichen Startmeldungen verdecken. Und ich will keinen Installer, der mir Partitionierungs"vorschläge" macht ("Nackenschläge" wäre zutreffender). [Ratti in suse-linux] -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (4)
-
Christian Boltz
-
Dominique Leuenberger a.k.a DimStar
-
Juergen Weigert
-
Per Jessen