Description of problem: (maybe assigned to FundaWang) The new version of simgear (2.4.0) built with openscenegraph (3.0.0) requires some libs of openscenegraph (libosg.so.80 libosgDB.so.80 libosgParticle.so.80 and some others) The previous version of simgear (2.0.0) was built with the previous version of openscenegraph and so required the previous libs (libosg.so.74 libosgDB.so.74 libosgParticle.so.74) and libOpenThreads.so.11 that are no more provided by cauldron... But libsimgear2.0.0-2.0.0 was not obsoleted by libsimgear-2.4.0 and still remains in cauldron repo, creating 4 broken dependencies : libOpenThreads.so.11 libosg.so.74 libosgDB.so.74 libosgParticle.so.74 http://pkgsubmit.mageia.org/data/missing-deps.i586.txt http://check.mageia.org/dependencies.html There seems to be a name problem : for the previous version (2.0.0) libname was %define lib_name %mklibname %{name} %{lib_major} where %{lib_major} was defined as %{version} for the new version (2.4.0) libname is %define lib_name %mklibname %{name} The spec file needs some modifications to suppress the previous libsimgear2.0.0-2.0.0 from the repo Regards Philippe
New lib major don't obsolete old ones, we rebuild against the new major, then remove the old libs from the repos (and the plan is to get old libs not required by anything removed automatically from the repos). The point is, there's not libname for the latest submit of simgear, there's only -devel.
Assignee: bugsquad => fundawang
OK ! I read the commit 126215 to understand why there were two versions of libsimgear and broken dependencies... so indeed there wouldn't be any libsimgear anymore in the repo since apparently it is not created with the last spec... If I understand well : both of libsimgear2.0.0-2.0.0 and libsimgear-2.4.0 may be removed if they are not required by anything... and it seems that Flightgear, in its previous version, was the only one requiring libsimgear, no more needed by its new version apparently ! But thinking to the future... when upgrading from Mageia1 to Mageia2 if there's nothing to obsolete libsimgear it will remain on the computers. Sorry if it is useless (I don't understand everything in the process and may say some silly things) ;-) Most of all : I don't want to waste your time ! Regards Philippe
(In reply to comment #2) > OK ! > > I read the commit 126215 to understand why there were two versions of > libsimgear and broken dependencies... > > so indeed there wouldn't be any libsimgear anymore in the repo > since apparently it is not created with the last spec... > > If I understand well : both of libsimgear2.0.0-2.0.0 and libsimgear-2.4.0 may > be removed if they are not required by anything... and it seems that > Flightgear, in its previous version, was the only one requiring libsimgear, no > more needed by its new version apparently ! > > > > But thinking to the future... when upgrading from Mageia1 to Mageia2 if there's > nothing to obsolete libsimgear it will remain on the computers. > That's right; ideally that's what 'urpme --auto-orphans' should take of, even though --auto-orphans has a few niggles. > > Sorry if it is useless (I don't understand everything in the process and may > say some silly things) ;-) > Most of all : I don't want to waste your time ! > > Regards > Philippe
I guess now libsimgear is embedded in flightgear, so I think flightgear should obsolete libsimgear
CC: (none) => stormi
Upstream decided that simgear only produces static libs by default now, which is only used by flightgear.
OK, this bug will hopefully be fixed when orphaned old major libs (not required by anything) are automatically removed from the repos, AFAIK, this procedure isn't deployed yet.
close as invalid, it is the wanted feature.
Status: NEW => RESOLVEDResolution: (none) => INVALID