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)
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
+