Your message dated Wed, 19 Dec 2018 23:40:29 +0000
with message-id <[email protected]>
and subject line Re: Bug#534713: Can probably close this
has caused the Debian Bug report #534713,
regarding /sbin/startpar: startpar: garbled output with CONCURRENCY=makefile
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.)
--
534713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534713
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sysvinit-utils
Version: 2.86.ds1-62
Severity: normal
File: /sbin/startpar
Hi,
when using starpar, I sometimes get garbled output (only noticed it for
the rc2 stage so far)
Starting serviceA: serviceA.
Starting serviceB: serviceBStarting serviceC: serviceC.
.
Starting serviceC: serviceC.
Cheers,
Michael
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (300, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.30
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages sysvinit-utils depends on:
ii libc6 2.9-18 GNU C Library: Shared libraries
ii libselinux1 2.0.82-1 SELinux shared libraries
ii libsepol1 2.0.36-1 Security Enhanced Linux policy lib
sysvinit-utils recommends no packages.
Versions of packages sysvinit-utils suggests:
pn sash <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
[2018-12-17 18:57] Jesse Smith <[email protected]>
> I think this bug can probably be closed. The submitter seems to think
> it's Upstart-related and since Upstart isn't used anymore (so far as I
> know) it seems safe to close this. If the problem persists using SysV
> init (or another init system) then the issue can be re-opened.
Sure. Closing. Dear submitter, feel free to re-open bug if issue persist
with modern installations.
--- End Message ---
