On 07.03.2013 22:03, Michael Schwendt wrote:
On Thu, 07 Mar 2013 21:36:12 +0100, Sandro Mani wrote:
It started with yum-3.4.3-70.fc19. Is this a bug in yum >= 3.4.3-70, or
is this a problem with my rpm db? Both yum erase and rpm -e <reported
installed obsolete package> tell me that the indicated package is not
installed.
You misread the output. It tells which "Obsoletes" tags are found in
packages. For example:
$ rpm --query --obsoletes fedora-logos
redhat-logos
gnome-logos
It doesn't ask you to uninstall anything. ;)
Uhm, ok, but why is this something yum suddenly wants to report?
The Yum changelog is not detailed enough to tell, but rpmsack.py considers
these as "problems". I think normal installing/updating with Yum also
prints those warnings. As a guess, it could be these are all for "strange"
Obsoletes/Provides pairs that aren't specific enough, or confusing, or lacking
versions. Such as:
rpcbind-0.2.0-21.fc19.x86_64 has installed obsoletes portmap <= ('0', '4.0', '65.3'): rpcbind-0.2.0-21.fc19.x86_64
$ rpm -q --obsoletes rpcbind|grep port
portmap <= 4.0-65.3
$ rpm -q --provides rpcbind|grep port
portmap = 0.2.0-21.fc19
In other words, it obsoletes itself due to the versions that are specified.
You are right, i.e. these ones from fedora-logos are clearly ambiguous:
[...]
Obsoletes: redhat-logos
Obsoletes: gnome-logos
Provides: redhat-logos = %{version}-%{release}
Provides: gnome-logos = %{version}-%{release}
[...]
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
