Re: Bug#6621: Bug in cfengine Version: 1.3.8-1
> > In the postinst script, it does not prompt the user to press Enter after
> > displaying its important information (as required by Poliy manual section
> > 3.5). This causes administrators, etc. to receive an error mail daily from
> > the program, with no explanation for this.
>
> After further inspection of the policy manual, I have decided not to do this.
OK, but then, IMHO, you should not use the fact that it printed a message
during
install as a reason to immediately dismiss my other bug report. Since the
installation procedure did not pause for user response, the message went right
past. If a package
is installed in a buggy state, it is a sufficient reason to use the bug report
system. It is not just a "tiny" problem as you told me in a different
message. The error message sent complains of having too many files open, etc.
It is not easily determinable that the message comes directly from cfengine.
Other packages, for instance, dwww, are mentioned in the error message.
Getting errors about having too many files open is often indicitive of a
serious problem somewhere.
As for documentation, there is no /usr/doc/cfengine directory (a bug in
itself!), no manpage, etc.
If there is no solution to the problem of sending the error messages, perhaps
a README.Debian file in /usr/doc/cfengine would be a good idea. Otherwise,
you should prompt the user to press Enter after displaying the info in
postinst.
But a much better solution would be to not install the package in a state
where it sends error messages all the time, IMHO.
--
John Goerzen | Running Debian GNU/Linux (www.debian.org)
Custom Programming |
jgoerzen@complete.org |
--
John Goerzen | Running Debian GNU/Linux (www.debian.org)
Custom Programming |
jgoerzen@complete.org |
--
John Goerzen | Running Debian GNU/Linux (www.debian.org)
Custom Programming |
jgoerzen@complete.org |
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com
Reply to: