Bug#892989: closed by Michael Biebl (Re: Bug#892989: weird chars found in dpkg output)

2018-09-07 Thread Harald Dunkel
I think you misunderstood the problem. This is not about using UTF-8, but about producing binary log files, refused by tools like less and others. Writing the log file you don't know the locale used when it is read, so the "if locale == xxx" is bad code. I am forced to *avoid* UTF-8 as

Bug#892989: weird chars found in dpkg output

2018-03-16 Thread Harald Dunkel
systemd is version 232-25+deb9u2. Please remember that we are talking about running apt and dpkg using root to setup a server. Personal user desktop preferences don't matter here. I do not set LANG or LC_something for system administration. Just using the default system environment suggested by

Bug#892989: weird chars found in dpkg output

2018-03-16 Thread Michael Biebl
Am 16.03.2018 um 08:45 schrieb Harald Dunkel: > On 03/15/18 18:46, Michael Biebl wrote: >> >> With a UTF-8 locale (which you really should enable), systemctl will use >> '→', for a non-UTF8 locale, systemctl will fall back to '->' >> >> > > Sorry to say, but thats ridiculous. Shouldn't it work no

Bug#892989: weird chars found in dpkg output

2018-03-16 Thread Harald Dunkel
On 03/15/18 18:46, Michael Biebl wrote: With a UTF-8 locale (which you really should enable), systemctl will use '→', for a non-UTF8 locale, systemctl will fall back to '->' Sorry to say, but thats ridiculous. Shouldn't it work no matter what? Ain't that "if locale == xxx" just asking for tr

Bug#892989: weird chars found in dpkg output

2018-03-15 Thread Michael Biebl
Am 15.03.2018 um 18:11 schrieb Michael Biebl: > Am 15.03.2018 um 14:38 schrieb Guillem Jover: > >> AFAIR, this is coming from systemd, and the character should be an >> arrow (→), but I assume there's some kind of locale/encoding problem >> somewhere. Perhaps even a misconfiguration in your system

Bug#892989: weird chars found in dpkg output

2018-03-15 Thread Michael Biebl
Am 15.03.2018 um 14:38 schrieb Guillem Jover: > AFAIR, this is coming from systemd, and the character should be an > arrow (→), but I assume there's some kind of locale/encoding problem > somewhere. Perhaps even a misconfiguration in your system, but I'll > leave that up to the systemd maintainers

Bug#892989: weird chars found in dpkg output

2018-03-15 Thread Guillem Jover
Control: reassign -1 systemd [ Leaving all context for the reassignment. ] Hi! On Thu, 2018-03-15 at 10:05:44 +0100, Harald Dunkel wrote: > Package: dpkg > Version: 1.18.24 > > Running atp upgrade I get several lines about "Created symlink" with some > weird chars, turning my log file into a bi

Bug#892989: weird chars found in dpkg output

2018-03-15 Thread Harald Dunkel
Package: dpkg Version: 1.18.24 Running atp upgrade I get several lines about "Created symlink" with some weird chars, turning my log file into a binary file: : : Processing triggers for systemd (232-25+deb9u2) ... Setting up libhtml-parser-perl (3.72-3) ... Setting up liblwres141:amd64 (1:9.10.3