Your message dated Sun, 3 May 2020 22:41:24 +0200
with message-id <[email protected]>
and subject line Re: #375114: sysvinit: mesg should write its name when
outputting an error message
has caused the Debian Bug report #375114,
regarding util-linux: mesg should write its name when outputting an error
message
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.)
--
375114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375114
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sysvinit
Version: 2.86.ds1-14.1
Severity: wishlist
Users get confused because of "stdin: is not a tty" error message,
e.g. when using svn+ssh. See for instance:
http://svn.haxx.se/users/archive-2004-07/1381.shtml
The same problem happened a few days ago. The mesg command should
write its name in its error messages, e.g.:
mesg: stdin: is not a tty
so that the user can know which command generated it.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14.4-20051215
Locale: LANG=POSIX, LC_CTYPE=en_US.ISO8859-1 (charmap=ISO-8859-1)
Versions of packages sysvinit depends on:
ii initscripts 2.86.ds1-14.1 Scripts for initializing and shutt
ii libc6 2.3.6-15 GNU C Library: Shared libraries
ii libselinux1 1.30-1 SELinux shared libraries
ii libsepol1 1.12-1 Security Enhanced Linux policy lib
ii sysv-rc 2.86.ds1-14.1 System-V-like runlevel change mech
sysvinit recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Per Dmitry's comment this appears to be fixed.
Thanks,
Chris
--- End Message ---
