* Note that circular dependencies can often be avoided by temporarily
* disabling USE flags that trigger optional dependencies.
Try this:
emerge -1av =*glibc*-2.10.1-r1
Then try to finish the upgrade.
Hope that helps.
Dale
:-) :-)
09-06-2010, 09:16 PM
Alex Schuster
How to fix circular dependency?
Ajai Khattri writes:
> On Sun, 5 Sep 2010, Dale wrote:
> > Try this:
> >
> > emerge -1av =*glibc*-2.10.1-r1
>
> # emerge -1av =*glibc*-2.10.1-r1
>
> * IMPORTANT: 1 news items need reading for repository 'gentoo'.
> * Use eselect news to read news items.
>
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies -
>
> !!! '=*glibc*-2.10.1-r1' is not a valid package atom.
> !!! Please check ebuild(5) for full details.
> !!! (Did you specify a version but forget to prefix with '='?)
> ... done!
What Dale meant is to try installling sys-libs/glibc-2.10.1-r1. I have not
checked the depencencies, but the idea is that this version of glibc does
not depend on the new gcc, which would pull in the new glibc. So try this:
emerge -1a =sys-libs/glibc-2.10.1-r1
If it does not work, I'd try another glibc. eix sys-libs/glibc lists them
all.
Wonko
09-06-2010, 11:33 PM
Ajai Khattri
How to fix circular dependency?
On Mon, 6 Sep 2010, Alex Schuster wrote:
What Dale meant is to try installling sys-libs/glibc-2.10.1-r1. I have not
checked the depencencies, but the idea is that this version of glibc does
not depend on the new gcc, which would pull in the new glibc. So try this:
emerge -1a =sys-libs/glibc-2.10.1-r1
If it does not work, I'd try another glibc. eix sys-libs/glibc lists them
all.
OK, Ive managed to proceed a little further, but now Im encountering this:
# emerge -uDtpvk world
These are the packages that would be merged, in reverse order:
Calculating dependencies... done!
!!! Multiple package instances within a single package slot have been
pulled
!!! into the dependency graph, resulting in a slot conflict:
dev-php/PEAR-PEAR:0
('ebuild', '/', 'dev-php/PEAR-PEAR-1.9.0', 'merge') pulled in by
>=dev-php/PEAR-PEAR-1.6.1 required by ('installed', '/',
'dev-php/PEAR-Net_Socket-1.0.8', 'nomerge')
>=dev-php/PEAR-PEAR-1.6.1 required by ('installed', '/',
'dev-php/PEAR-Mail-1.1.14', 'nomerge')
dev-php/PEAR-PEAR required by world
(and 1 more)
('installed', '/', 'dev-php/PEAR-PEAR-1.6.2-r1', 'nomerge') pulled in by
<dev-php/PEAR-PEAR-1.8.1 required by ('installed', '/',
'dev-php/PEAR-Net_SMTP-1.2.10', 'nomerge')
<dev-php/PEAR-PEAR-1.8.1 required by ('installed', '/',
'dev-php/PEAR-Mail-1.1.14', 'nomerge')
dev-php/PEAR-PEAR required by world
(and 1 more)
Not sure what this message means?
--
A
09-07-2010, 12:56 PM
Alex Schuster
How to fix circular dependency?
Ajai Khattri writes:
> OK, Ive managed to proceed a little further, but now Im encountering
> this:
>
> # emerge -uDtpvk world
>
> These are the packages that would be merged, in reverse order:
>
> Calculating dependencies... done!
>
> !!! Multiple package instances within a single package slot have been
> pulled
> !!! into the dependency graph, resulting in a slot conflict:
[...]
> Not sure what this message means?
It means that portage wants to install both dev-php/PEAR-PEAR-1.9.0 and
dev-php/PEAR-PEAR-1.6.2-r1 at the same time. I don't understand why, looks
to me like it should keep you already installed 1.6.2-r1 version.
Do you need to have this package in world? Does the conflict also happen
if not?
In case you are running portage 2.1, you might give 2.2 a try. It is
better at resolving such stuff, but still fails sometimes.
No more ideas,
Wonko
09-07-2010, 04:15 PM
Ajai Khattri
How to fix circular dependency?
On Tue, 7 Sep 2010, Alex Schuster wrote:
It means that portage wants to install both dev-php/PEAR-PEAR-1.9.0 and
dev-php/PEAR-PEAR-1.6.2-r1 at the same time. I don't understand why, looks
to me like it should keep you already installed 1.6.2-r1 version.
Do you need to have this package in world? Does the conflict also happen
if not?
In case you are running portage 2.1, you might give 2.2 a try. It is
better at resolving such stuff, but still fails sometimes.
I decided to uninstall PEAR-PEAR to get past this (I figured I could
always reinstall later after I finish all other updates).
So far so good, thanks.
--
A
09-07-2010, 09:03 PM
Francesco Talamona
How to fix circular dependency?
On Tuesday 07 September 2010, Ajai Khattri wrote:
> OK, Ive managed to proceed a little further, but now Im encountering
> this:
>
> # emerge -uDtpvk world
When it's time to upgrade a large number of programs, it's better to
take the task one step at a time, for example the following command:
emerge -pu system
Will (tell you to) upgrade a little subset, it'll less likely get stuck
on circular deps and will upgrade the more important programs first.
HTH
Francesco
--
Linux Version 2.6.35-gentoo-r5, Compiled #1 SMP PREEMPT Sat Aug 28
12:20:05 CEST 2010
Two 1GHz AMD Athlon 64 Processors, 4GB RAM, 4019.06 Bogomips Total
aemaeth
09-07-2010, 09:44 PM
Alan McKinnon
How to fix circular dependency?
Apparently, though unproven, at 14:56 on Tuesday 07 September 2010, Alex
Schuster did opine thusly:
> Ajai Khattri writes:
> > OK, Ive managed to proceed a little further, but now Im encountering
> > this:
> >
> > # emerge -uDtpvk world
> >
> > These are the packages that would be merged, in reverse order:
> >
> > Calculating dependencies... done!
> >
> > !!! Multiple package instances within a single package slot have been
> > pulled
>
> > !!! into the dependency graph, resulting in a slot conflict:
> [...]
>
> > Not sure what this message means?
>
> It means that portage wants to install both dev-php/PEAR-PEAR-1.9.0 and
> dev-php/PEAR-PEAR-1.6.2-r1 at the same time. I don't understand why, looks
> to me like it should keep you already installed 1.6.2-r1 version.
> Do you need to have this package in world? Does the conflict also happen
> if not?
>
> In case you are running portage 2.1, you might give 2.2 a try. It is
> better at resolving such stuff, but still fails sometimes.
I don't have the dependency listing to hand, but I did study it earlier.
PEAR-PEAR-1.9.0 is being pulled in because something else has a dep on
>=PEAR-PEAR-1.7.something
PEAR-PEAR-1.6.2-r1 is being pulled in because that specific version is a hard
dep on something else.
Reading the output is easy, read it bottom up, paying attention to the
prefixes (>, =, etc). The format is like this:
=packageA-v2 pulled in (not already installed)
>=packageA-v1 pulled in by
packageB-v1 (in world)
Or words to that effect. There's a lot of detail and it translates to
something like this:
packageB has a dep on packageA. The exact dep is (follow with version range
that packageB is happy with, straight out of DEPEND). To satisfy this, portage
will install packageA-v<blah>
v<blah> depends on what is in the tree, the arch, contents of
package-{un-}mask and various other bits.
Often one can get away with hardmasking recent packages that block which will
force portage to find lower versions, hopefully something that satisfies all
relevant DEPENDs
The OP has inconsistent requirements that cannot be fixed except by removing
PEAR-PEAR, or by removing one or more packages the DEPEND on it.
How to fix circular dependency?
