With just “aptitude install chrony”, the “starting” step took a very long
while, several minutes before doing anything. People might (quite rightfully)
consider it hung, and interrupt the package installation/upgrade, which then
leaves the package management system in a bad state.
That's
Helmut Grohne [EMAIL PROTECTED] (06/11/2008):
Did you notice that the bug was reported on i386 initially? So it is
even a bit cross-architecture.
Sure, but I wasn't going to emphasize something that I didn't experience
personally. ;)
Mraw,
KiBi.
signature.asc
Description: Digital signature
Cyril writes:
All of the boxes in my company are. Too bad I can't test on more
systems. That's quite different from “a single system”. And it's not like
amd64 is an obscure architecture, last time I checked.
It works fine on amd64 here as well as on two different i386 boxes. It has
to do with
Michael writes:
I beg to disagree because this bug seems to hit only some systems but not all.
Of course I agree that this is bad if your system is hit, but with a lot of
systm not being hit I do not consider this release critical.
Aynway, the best solution is to fix this, if it is fixable
Michael Meskes [EMAIL PROTECTED] (06/11/2008):
I beg to disagree because this bug seems to hit only some systems but
not all.
I didn't upgrade to grave, only to serious.
Of course I agree that this is bad if your system is hit, but with a
lot of system not being hit I do not consider this
All of the boxes in my company are. Too bad I can't test on more
systems. That's quite different from ???a single system???. And it's not
like amd64 is an obscure architecture, last time I checked.
Did you notice that the bug was reported on i386 initially? So it is
even a bit
6 matches
Mail list logo
