Mailinglist Archive: zypp-devel (30 mails)

[Dave Plater <dplater@xxxxxxxxxxxxxxxx>]

I'm trying to get python3-base-3.2 to trigger the removal of python3-3.1 without using "Conflicts:", python3-3.1 is one package but 
python-3.2 has been split into two packages python3-base which provides a minimum and python3. Obviously I can't provide python3 = 
%{version} so I looked at what python3-base-3.2 provided that was also provided by python3-3.1 and tried :
"Obsoletes:   python(abi) < %{version}" but it doesn't work. I've added a provides for "python(abi) = %{version}" but I'm pretty sure that 
will only give me an rpmlint warning when it's finished building.
So does libzypp respect things like mime and abi? If not I suppose that python3-3.1 is going to have to provide python3-base. This puts me 
in a spot, I'm trying to get Packman to take python3-3.2 for blender which is making full use of py3.2's new api additions, it changes 
pages of code into lines and to get an update for python3-3.1 is timeous and difficult but I suppose I'll end up using "Conflicts:".
Any help appreciated.
Dave Plater
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx