* Re: [gentoo-user] What's going on with scons
2005-09-04 19:58 [gentoo-user] What's going on with scons Rafael Fernández López
@ 2005-09-04 20:12 ` Holly Bostick
0 siblings, 0 replies; 2+ messages in thread
From: Holly Bostick @ 2005-09-04 20:12 UTC (permalink / raw
To: gentoo-user
Rafael Fernández López schreef:
> Hi,
>
> I'm doing right now an "emerge -vuD world". Now portage wants to
> UPDATE scons. If I do another "emerge -vuD world" (not necessary to
> run "emerge sync") portage wants to DOWNGRADE scons.
>
> Always that I do an "emerge sync" and later an "emerge -vuD world",
> it updates my system, but scons depends on the last time, if it was
> updated, portage will downgrade it and if was downgraded, portage
> will try to update it...
>
> What's going on with scons?
>
> Thanks.
One of two things could be happening here:
1) Did you originally emerge scons with ACCEPT_KEYWORDS="~arch" in the
command line, and forget to add scons to /etc/portage/package.keywords?
If so, as far as Portage is concerned, the package is "illegal", so it
attempts to downgrade it to stable, but something that depends on the
later version then attempts to upgrade it.
If this is the case, add scons to /etc/portage/package.keywords, and the
madness should stop.
2) The reverse dependencies on scons are (hopefully) temporarily mixed.
Sometimes packages with many 'plugins' that depend on the main package
get 'out of sync' with the main package (gstreamer comes to mind). The
problem being that some of the installed reverse dependencies depend on
an earlier version, and some depend on a later. As I said, this is
usually temporary; upstream/Portage usually gets updated packages that
conform everything to the same version (meaning the current version)
within a day (two at most). If it's longer than that, check
bugs.gentoo.org for more information, since that tends to indicate an
'issue'.
If this is the case, do an emerge -vuDt world to get the dependency tree
and see which plugin/module is depending on the old version. First, see
if there's an update already that perhaps needs to be unmasked in
/etc/portage/package.keywords. If not (yet), and you can do without that
particular plugin for a short time, unmerge it; problem solved. Just
keep your eye out for the updated version. If you can't do without the
older-version module/plugin, try downgrading the ones that are causing
the update (mask them to keep Portage from trying to drag the later ones
in).
You can thereafter watch Portage like a hawk for the updates and reverse
your changes, or you can go on with the earlier versions until the later
versions go stable, in which case they'll be updated normally in due time.
HTH,
Holly
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 2+ messages in thread