On 01-12-2019 23:51, Matthew Selsky wrote:
> On Sun, Dec 01, 2019 at 10:45:28AM +0100, Udo van den Heuvel via devel wrote:
>> Perhaps also in this way:
>>
>> rpmbuild -bb --define '_wrong_version_format_terminate_build 0'
>> SPECS/ntpsec.spec
>
> Udo,
>
> Do you have a local patch that updates
On Sun, Dec 01, 2019 at 10:45:28AM +0100, Udo van den Heuvel via devel wrote:
> On 01-12-2019 10:14, Udo van den Heuvel via devel wrote:
> > The macro _wrong_version_format_terminate_build can be used to work
> > around this issue:
>
> Perhaps also in this way:
>
> rpmbuild -bb --define
On 01-12-2019 10:14, Udo van den Heuvel via devel wrote:
> The macro _wrong_version_format_terminate_build can be used to work
> around this issue:
Perhaps also in this way:
rpmbuild -bb --define '_wrong_version_format_terminate_build 0'
SPECS/ntpsec.spec
Kind regards,
Udo
Hello,
The macro _wrong_version_format_terminate_build can be used to work
around this issue:
On 01-12-2019 09:00, Udo van den Heuvel via devel wrote:
> Processing files: ntpsec-1.1.8-1.fc31.x86_64
> error: Invalid version (double separator '-'):
> 1.1.8.2019-08-02T00-00-00Z: python3.7dist(ntp)
On 12/1/19 2:44 AM, Achim Gratz via devel wrote:
> Richard Laager via devel writes:
>> The issue persists when removing "nts" from "server" lines (i.e.
>> disabling NTS client behavior).
>>
>> The problem goes away when disabling NTS server behavior.
To clarify: If I run as an NTS client but not
Richard Laager via devel writes:
> The issue persists when removing "nts" from "server" lines (i.e.
> disabling NTS client behavior).
>
> The problem goes away when disabling NTS server behavior.
I don't serve NTS from the two test machines, so that would be an
additional code path to consider.
Richard Laager via devel writes:
> That was the case for me _at startup_, but not after that. (See the
> attached logs.)
I think the culprit is somewhere in the NTS client code.
>>> This would also explain why a server
>>> that has many clients would see many more such errors.
>
> Why's that?
On 12/1/19 2:17 AM, Richard Laager via devel wrote:
> On 11/30/19 6:17 AM, ASSI via devel wrote:
>> ASSI via devel writes:
>>> is… intriguing. If you follow the code through the function, ts_min in
>>> the log should always be ts_prev+sys_fuzz; these two values can't be
>>> identical or differ by
On 11/30/19 6:17 AM, ASSI via devel wrote:
> ASSI via devel writes:
>> is… intriguing. If you follow the code through the function, ts_min in
>> the log should always be ts_prev+sys_fuzz; these two values can't be
>> identical or differ by any other value, ts_min must strictly be greater
>> than
Hello,
Previously 1.1.8 built OK, now I get:
(...)
+ popd
~/rpmbuild/BUILD/ntpsec-1.1.8
+ /usr/lib/rpm/check-buildroot
+ /usr/lib/rpm/redhat/brp-ldconfig
+ /usr/lib/rpm/brp-compress
+ /usr/lib/rpm/brp-strip /usr/bin/strip
+ /usr/lib/rpm/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump
+
10 matches
Mail list logo