Mark Haney wrote:
Duncan wrote:
"Mark Haney" <[email protected]> posted
[email protected], excerpted below, on Mon, 22 Dec 2008
14:13:27 -0500:
I've been updating my system after having some surgery and taking time
off from everything and I've noticed a funny thing. Certain packages are
requiring that I install v2.1.4.5 or portage (I'm running 2.1.6.2 now)
before updating the other packages. Why is that?
So you're saying they're asking you to downgrade? Do you have an
example and is it in the main tree or some overlay (which)?
I /think/ that'd be a bug as to date portage has been backward
compatible such that new versions should handle old ebuilds just fine,
but I can't say for sure without an example to look at the code on and
see what it's actually trying to do, where and why.
What I suspect is happening is that it's depending on a specific
portage version, say =2.1.4*, instead of a slot, which portage should
support everything at least in the main tree. IOW it shouldn't be
happening in the main tree. However, it could still be occurring in
some obscure overlay that doesn't get much testing from ~portage,
maybe one that has mostly paludis or pkgcore users?
But it's all speculation until there's an example to look at, and the
problem sounds strange enough I'm doubting I'm reading what you said
correctly in the first place.
It seems anything java related and mplayer as well. Which of course I
don't understand at all. It also might be a required portage version as
you say, but I don't know how to determine that.
A quick check shows java and a bunch of others requiring portage
>=2.1.27 so that shouldn't be an issue I wouldn't think.
--
Frustra laborant quotquot se calculationibus fatigant pro inventione
quadraturae circuli
Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415
Call (866) ERC-7110 for after hours support
