Re: Bug#799093: RFS: chrony/1.31.1-2

[Vincent Blut <vincent.debian@free.fr>]

Le mar. 15 sept. 2015 à 22:59, Jerome BENOIT <calculus@rezozer.net> a 
écrit :
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,

Hello Jerome,

> On 15/09/15 22:50, Vincent Blut wrote:
> >  Le mar. 15 sept. 2015 à 22:33, Paul Gevers <elbrus@debian.org> a 
> > écrit :
> > >  On 15-09-15 22:06, Paul Gevers wrote:
> > > >   On 15-09-15 21:56, Vincent Blut wrote:
> > > > >   Could you please take a look at chrony 1.31.1-2¹?
> > > >
> > > >   Sure, my dashboard told me that there was a new chrony, so I was
> > > >   expecting this e-mail. Surprisingly it was not to package that. 
> > > > Could
> > > >   you also fix the watch file, as you seem to be not following the 
> > > > 2.x branch?
> > >
> > >  And I may have asked before, why aren't you? Looking at the version
> > >  numbers and their timing, you are just lagging, not really 
> > > following an
> > >  other branch are you? What is the plan? So if you want to switch 
> > > to 2.x,
> > >  you don't need to update the watch file, and I can upload as is 
> > > (after
> > >  checking).
> >
> >  Well, I didn’t start packaging the 2.x upstream release, because 
> > I wanted to
> >  smoothly upgrade chrony in Debian to catch regressions more easily, 
> > but don’t
> >  worry, 2.0 (and 2.1.1 soon after) is in the pipe. The changes from 
> > 1.3x and 2.x
> >  are quite huge (NTP v4 support, etc.), so it will take some times 
> > to be in good
> >  shape, but I’m currently working on this and hope to send you 
> > some stuff to review
> >  in october.
>
> You may want to put the 2 branch in experiemental to begin with.

Indeed, depending on how tests will go, I’ll either push it to master 
or
as you say, create an experimental branch for it.

> Jerome

Cheers,
Vincent