Dear Michal, thank you very much for this lightning fast response.
> This is indeed invalid rpm version - is separator between version and > release and it is not allowed in either of them. It used to be warning > for ages and now is an error. This clears this up for me. I will take this bug to the 3rd party developers whose code I wanted to compile. Thank you again and excuse this wrongly filed bug, I should have checked the recent status of this string handling by rpm considering warning/error. Kind regards, Martin On 20.11.2017 19:29, Michal Čihař wrote: > Hello > > On Mon, 2017-11-20 at 18:27 +0100, Martin Petersen wrote: >> Package: rpm >> Version: >> >> Dear Maintainer, >> >> *** Reporter, please consider answering these questions, where >> appropriate *** >> >> * What led up to the situation? >> Upgrading rpm from 4.12.0.2+dfsg1-2 to 4.14.0+dfsg1-2 in a apt-get >> dist-upgrade run >> >> * What exactly did you do (or not do) that was effective (or >> ineffective)? >> Trying to build zfsonlinux kernel modules for new linux-kernels. >> Building this modules for quite some time no. Failing to build >> startet >> about kernel version 4.14-0-0. > > This is indeed invalid rpm version - is separator between version and > release and it is not allowed in either of them. It used to be warning > for ages and now is an error. > > See upstream commit: > https://github.com/rpm-software-management/rpm/commit/5e94633660d0e2b97 > 0bf42f1dc24346ed46cae2e > > If I'm reading it correctly, it should be possible to workaround this > by defining %_wrong_version_format_terminate_build to 0. > > Anwyay, no, we're not going to diverge from upstream in this. >
signature.asc
Description: OpenPGP digital signature
