Bug#689012: Status of chrony

2012-11-23 Thread John Hasler
Enrico Zini writes: > So please do not consider the ball to be in the release team's > court... I said nothing about anything being in any court. I merely observed that only the release team can make exceptions to the freeze. I did not request an exception: I assume that the decision not to admi

Bug#689012: Bug#692923: Bug#689012: Status of chrony

2012-11-23 Thread Joachim Wiedorn
Hello Enrico, Enrico Zini wrote on 2012-11-23 22:23: > So please do not consider the ball to be in the release team's court: > for this to be fixed, the relevant changes need to be backported to > 1.24. I am on the way to upload a new chrony version 1.24-3.1+deb7u1 as David Prévot wrote on 2012-

Bug#689012: Status of chrony

2012-11-23 Thread Enrico Zini
On Fri, Nov 16, 2012 at 07:49:46AM -0600, John Hasler wrote: > None of these bugs (or any bugs above "normal") apply to the version of > Chrony in Sid. They could all by fixed by migrating that version (the > current upstream release) to Wheezy but as it is frozen that is not > possible unless th

Bug#689012: Status of chrony

2012-11-16 Thread John Hasler
None of these bugs (or any bugs above "normal") apply to the version of Chrony in Sid. They could all by fixed by migrating that version (the current upstream release) to Wheezy but as it is frozen that is not possible unless the release team decides to make an exception. That is entirely up to t