Your message dated Fri, 7 Sep 2018 02:12:11 +0200
with message-id <[email protected]>
and subject line Re: Bug#892989: weird chars found in dpkg output
has caused the Debian Bug report #892989,
regarding weird chars found in dpkg output
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
892989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892989
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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.dfsg.P4-12.3+deb9u4) ...
Setting up ebtables (2.0.10.4-3.5+b1) ...
Created symlink /etc/systemd/system/multi-user.target.wants/ebtables.service
â /lib/systemd/system/ebtables.service.
update-rc.d: warning: start and stop actions are no longer supported; falling
back to defaults
insserv: fopen(/etc/insserv.conf): No such file or directory
Setting up wget (1.18-5+deb9u1) ...
:
Setting up resolvconf (1.79) ...
Created symlink /etc/systemd/system/sysinit.target.wants/resolvconf.service â
/lib/systemd/system/resolvconf.service.
insserv: fopen(/etc/insserv.conf): No such file or directory
Setting up libnfnetlink0:amd64 (1.0.1-3) ...
:
Setting up bsdmainutils (9.0.12+nmu1) ...
update-alternatives: using /usr/bin/bsd-write to provide /usr/bin/write (write)
in auto mode
Setting up anacron (2.3-24) ...
Created symlink /etc/systemd/system/multi-user.target.wants/anacron.service â
/lib/systemd/system/anacron.service.
Created symlink /etc/systemd/system/timers.target.wants/anacron.timer â
/lib/systemd/system/anacron.timer.
Setting up libevent-2.0-5:amd64 (2.0.21-stable-3) ...
:
Please reassign, if necessary.
Regards
Harri
--- End Message ---
--- Begin Message ---
On Fri, 16 Mar 2018 10:12:33 +0100 Michael Biebl <[email protected]> wrote:
> 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 matter
> > what? Ain't that "if locale == xxx" just asking for troubles?
>
> No, I don't think it's ridiculous at all to use Unicode in 2018. The
> ASCII fallback is only to be super-nice to people still refusing to use
> a UTF-8 locale.
I'm closing this bug report. Making use of unicode in 2018 is a sensible
thing to do.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
