Bug#998372: "debsums: can't check debsums file ... (Wide character in subroutine entry)"

[Axel Beckert]

Control: tag -1 + unreproducible help

Hi Philipp,

thanks for this bug report!

Philipp Marek wrote:
> When using debsums, some files (non-ASCII?) can't be checked.

Huh? This is weird…

> Example:
> 
>     $ reportbug debsums
>     *** Welcome to reportbug.  Use ? for help at prompts. ***
>     Note: bug reports are publicly archived (including the email address of the submitter).
>     Detected character set: UTF-8
>     Please change your locale if this is incorrect.
> 
>     Using 'Philipp Marek <philipp at marek.priv.at>' as your from address.
>     Getting status for debsums...
>     Verifying package integrity...
>     There may be a problem with your installation of debsums;
>     the following problems were detected by debsums:
>     debsums: can't check debsums file /usr/share/doc/debsums/NEWS.Debian.gz (Wide character in subroutine entry)
>     […]

Can't reproduce:

    ~/pkg-perl/debsums → reportbug debsums
    Note: bug reports are publicly archived (including the email address of the submitter).
    Detected character set: UTF-8
    Please change your locale if this is incorrect.
    
    Using 'Axel Beckert <abe at debian.org>' as your from address.
    Getting status for debsums...
    Verifying package integrity...
    Checking for newer versions at madison, incoming.debian.org and http://ftp-master.debian.org/new.html
    Will send report to Debian (per lsb_release).
    Nothing new to report; exiting.

I also tried

    env LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 LANGUAGE=de_DE:de debsums debsums

(no de_AT available on my dev box, but de_DE should be close enough
for that case), but to no avail. (Tagging as "unreproducible" for that
— which doesn't mean that the bug is not there, it's just unclear
under what conditions it shows up.)

Showed up even in the automatically gathered section:

> -- debsums errors found:
> debsums: can't check debsums file /usr/share/doc/debsums/NEWS.Debian.gz (Wide character in subroutine entry)
> debsums: can't check debsums file /usr/share/doc/debsums/changelog.gz (Wide character in subroutine entry)
> debsums: can't check debsums file /usr/share/man/de/man1/debsums.1.gz (Wide character in subroutine entry)
> debsums: can't check debsums file /usr/share/man/es/man1/debsums.1.gz (Wide character in subroutine entry)
> debsums: can't check debsums file /usr/share/man/fr/man1/debsums.1.gz (Wide character in subroutine entry)
> debsums: can't check debsums file /usr/share/man/man1/debsums.1.gz (Wide character in subroutine entry)
> debsums: can't check debsums file /usr/share/man/man1/rdebsums.1.gz (Wide character in subroutine entry)
> debsums: can't check debsums file /usr/share/man/pt/man1/debsums.1.gz (Wide character in subroutine entry)
> debsums: can't check debsums file /usr/share/man/ru/man1/debsums.1.gz (Wide character in subroutine entry)
> debsums: can't check debsums file /usr/share/man/sv/man1/debsums.1.gz (Wide character in subroutine entry)

And indeed, those are just the non-ASCII (well, binary) files.

But sorry, currently no idea what the cause could be. Especially not
why this wide character is reported to be in a subroutine entry. I
though suspect that this is caused by debsums usage of lambda calculus
style subroutines. So if someone has an idea… (Tagging as "help" for
that.)

And yes, I probably could just add something "binmode STDIN, ':utf8';"
or so, but without understanding the issue, I'm reluctant to add such
snippet. And without being able to reproduce it, it's also hard to
say, if it would help at all, as the wide character wasn't reported in
STDIN or STDOUT or so, but in a subroutine entry.

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe at debian.org>, https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE