[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Remaining critical bugs (IMHO)

> > A 20 second clock error does not count as a "critical bug".
> Why not? We are in 1997. A 20 second clock error is a BIG error, if you
> take in account that xntp usually allows the computer clock error to
> be less than 0.001 seconds.

The problem only occurs because different machines are running different
versions of the package.  If everybody ran the same, there would be
no problem.  When you run different configurations, you have to expect
you're going to get a few minor discrepencies every now and then.

> There are some bugs that do not prevent Debian to be installed, but
> could damage our good reputation, think about Debian in the shuttle, for
> example. Would they allow for a 20 second clock error?

I'm not trying to stop anybody from fixing it!  If it's so important,
then two weeks should be plenty of time.  If it doesn't get fixed then
it obviously wasn't that important.  Feel free to put all the pressure
you want on the maintainer, but please don't ask me to do it for something
that affects such a tiny number of people and has no serious consequences.

                                 ( bcwhite@verisim.com )

    In theory, theory and practice are the same.  In practice, they're not.

TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .

Reply to: