Re: Bug#799093: RFS: chrony/1.31.1-2
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
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.
Jerome
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJV+IasAAoJEIC/w4IMSybjFBwIAIumA/5ykTkNN7iHHZTzFYHX
sJFH3dH0hud+BJ+WrlThT45Gw78DSbHBcEDrfg+1DkdT33CjloBI/BaIL2yY/kx3
W5tqOoWzIlBweL4pcHAxFxnDRAUN0/IQisW9xUfZlDVuKLch3iXOhbI5GY7Hs38q
lq4i3fWG3oRRMDdpSe81tMM3rZ4bKUNeQDOKqyqyPUNHmNlv3oRs97K+ELJznDnf
TLSa2HzvUGnu9Ft/9YcFVwE+DhoW0qyqnBh0+RoIs/g5+/HbsT2F8bJ8E7H8Gb/l
TKhHyLNzV5SB3tKtTORkhBHvodcN54KDFCvvlG5F2D5Z4SQKDjmw0eWj7M53VSo=
=TvA2
-----END PGP SIGNATURE-----
Reply to: