On 10/23/2015 07:47 AM, Lubos Kardos wrote:
Hi,
I want to just to inform you that the new version of rpmbuild
(rpm-build-4.13.0-0.rc1.6.fc24) that is available in rawhide terminates build
when a wrong version format is used in spec i. e. epoch is not unsigned integer
or mutilple separators are used.
Example of wrong versions:
Requires: packageA = -1:2.3-fc24 // negative epoch
Requires: packageA = foo:2.3-fc24 // non alphanumeric epoch
Requires: packageA = 1:3:2.3-fc24 // multiple separators ":"
Requires: packageA = 1:2.3-5-12-fc24 // multiple separators "-"
If you need to build packages which don't comply with these new rules then you
can set macro %_wrong_version_format_terminate_build to 0 then only warnings
are showed but building is not terminated.
Some more info in [1].
Lubos
[1]
https://bugzilla.redhat.com/show_bug.cgi?id=1251453
This seems to have broken building some python srpms:
Executing command: ['bash', '--login', '-c',
'/usr/bin/rpmbuild -bs --target
noarch --nodeps /builddir/build/SPECS/scipy.spec'] with env {'LANG':
'en_US.UTF-8', 'TERM': 'vt100', 'SHELL':
'/bin/bash', 'PROMPT_COMMAND':
'printf "\x1b]0;<mock-chroot>\x07<mock-chroot>"',
'PATH':
'/usr/bin:/bin:/usr/sbin:/sbin', 'HOME': '/builddir',
'HOSTNAME': 'mock'} and
shell False
error: line 53: Invalid version (epoch must be unsigned integer):
%{epoch}:0.16.1-1.fc24: Provides: scipy = %{epoch}:0.16.1-1.fc24
This is from the automatically generated Provides form %python_provide. It does:
vr = rpm.expand("%{?epoch:%{epoch}:}%{version}-%{release}")
to generate the version request, so perhaps epoch is getting handled
inconsistently?
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion(a)nwra.com
Boulder, CO 80301
http://www.nwra.com