Grrr multiple accounts... ---------- Forwarded message ---------- From: "Sven Vermeulen" <[email protected]> Date: Nov 30, 2012 6:06 PM Subject: Re: [gentoo-hardened] setools and libsemanage conflicting dependencies To: <[email protected]>
On Nov 30, 2012 5:39 PM, "Stan Sander" <[email protected]> wrote: > > Am getting ready to do a world update on my ~amd64 box this morning and > came across the following conflict. > > (dev-lang/swig-1.3.40-r1::gentoo, ebuild scheduled for merge) pulled in by > <dev-lang/swig-2.0 required by (app-admin/setools-3.3.7-r6::gentoo, > ebuild scheduled for merge) > > (dev-lang/swig-2.0.8::gentoo, installed) pulled in by > >=dev-lang/swig-2.0.4-r1 required by > (sys-libs/libsemanage-2.1.9::gentoo, installed) > > If I mask 3.3.7-r6 of setools the problem does not exist as r5 which I > already have seems quite happy with swig-2.x. So I'm thinking that the > < in the dependency should actually be a > in the r6 ebuild. Nope it is correct. setools requires swig-1 whereas others require swig-2. The dependencies are build-only dependencies so in theory portage can downgrade/upgrade swig as needed. If you upgrade setools first and then @world, does that make it happy?
