Mailinglist Archive: opensuse-buildservice (138 mails)

< Previous Next >
Re: [opensuse-buildservice] Re: RPMLINT report. No errors, but failed
  • From: Roman Evstifeev <someuniquename@xxxxxxxxx>
  • Date: Sun, 21 Feb 2016 02:13:01 +0300
  • Message-id: <CAMX-vmLJvdJ5TcZKGitXd=VRvykpjFFC6sk5=oGFRxCu_dCAXw@mail.gmail.com>
I think this is the relevant bugreport:
https://github.com/rpm-software-management/rpmlint/issues/61

On Sun, Feb 21, 2016 at 1:48 AM, Roman Evstifeev
<someuniquename@xxxxxxxxx> wrote:
Maybe rpmlint has issues with handling cyrillic dirnames\flienames?

On Sat, Feb 20, 2016 at 11:58 PM, Andreas Schwab <schwab@xxxxxxxxxxxxxx>
wrote:
Kyrill Detinov <lazy.kent@xxxxxxxxxxxx> writes:

I do not understand, why it is failed.

[ 73s] RPMLINT report:
[ 73s] ===============
[ 76s] outwiker.noarch: W: zero-length
/usr/share/outwiker/help/help_en/Page Types/Wiki Page/Wiki
Commands/childlist command/page 2/__page.text
[ 76s] 2 packages and 0 specfiles checked; 0 errors, 20 warnings.
[ 76s] Traceback (most recent call last):
[ 76s] File "rpmlint.py", line 385, in <module>
[ 76s] File "rpmlint.py", line 196, in main
[ 76s] File "Filter.py", line 131, in printAllReasons
[ 76s] File "Filter.py", line 40, in __print
[ 76s] File "/usr/lib/python2.7/codecs.py", line 357, in write
[ 76s] data, consumed = self.encode(object, self.errors)
[ 76s] UnicodeDecodeError: 'ascii' codec can't decode byte 0xd0 in
position 65: ordinal not in range(128)

24 warnings changed to 20 warnings (?).
Is anything wrong in rpmlint or anywhere?

Most likely a bug in rpmlint, suggest to file a bug report.

Andreas.

--
Andreas Schwab, schwab@xxxxxxxxxxxxxx
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx

--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups