harmful python-* Provides without epoch
Jakub Bogusz
qboosh at pld-linux.org
Sat Dec 11 17:24:42 CET 2004
[main]
Provides: %{name} = %{py_ver}
%package libs
Provides: %{name}-libs = %{py_ver}
%package modules
Provides: %{name}-modules = %{py_ver}
%package static
Provides: %{name}-static = %{py_ver}
are harmful - they break existing %pyrequires_eq.
$ rpm -q --provides python-libs | grep python-libs
python-libs = 2.3
python-libs = 1:2.3.4-1
(and so on for base, -modules, -static)
So "Requires: python-libs < 1:2.4" rule generated by pyrequires_eq is
_satisfied_ by python-libs 1:2.4 providing "python-libs = 2.4"...
Some workaround could be not to use epoch in less-than rules... but it
could turn out harmful in the future.
Does anyone have better, reliable solution than dropping these
non-epoched provides and updating existing non-epoched dependencies?
--
Jakub Bogusz http://cyber.cs.net.pl/~qboosh/
More information about the pld-devel-en
mailing list