Holly Bostick wrote:
Dale schreef:
Who is this schreef guy? I'm just Dale.
Hi guys, and Holly,
I ran a revdep-rebuild on my main rig and it says it needs to do this:
[ebuild UD] gnome-base/gnome-vfs-2.10.1-r2 [2.12.2]
OK, the "U" means Upgrade right? The "D" means downgrade right? What
the heck is going on here? How is it going to upgrade then downgrade
and why?
It's not going to "upgrade, then downgrade" It means that the upgrade
*is* a downgrade from the version currently installed.
Oh, I see. Sort of looks funny though. LOL
This can happen for a number of reasons, but all the reasons relate to
the currently-installed package being "illegal" on your system in
Portage's view.
For example:
1. You installed the current version with "ACCEPT_KEYWORDS=~arch" on the
command line; because this is a temporary setting that Portage doesn't
remember after a new shell login, when a global Portage search is later
run, Portage sees that only stable packages are "legal" and downgrades
the upgrade;
I never do this.
2. The package has changed status since installation and is no longer
legal (for example, the dev team has discovered major problems and hard
masked the package, making it legal on _no-one's_ system-- this happened
to me yesterday with the bash upgrade);
3. The package that uses this package as a dependency cannot use this
version of the currently-installed lib as a dependency (has a hard
version dependency), so the package must be downgraded to serve as a
dependency for the package in your world file that's demanding it.
Etc., etc, enz.
Mine was in package.keywords for some reason. I dunno. A ghost
maybe???? LOL
You see that "using exisiting /root/.revdep-rebuild.1_files"?
That means that you previously ran revdep-rebuild -p and the system is
using that output to run the actual rebuild.
Yea, I just used the up arrow and bash history. I usually rm the files
before I run revdep. The first time anyway.
Do an emerge -upDtv gnome-vfs (after the downgrade, if you allow it).
That should show you what is bringing it in (the --tree view), and the
USE flags that package is using It's possible that you have the "gnome"
USE flag enabled for a package that "doesn't need it", or another USE
flag-- "eds" comes to mind" that forces the dependency.
Hope this helps.
Holly
Well, I took it out of package.keyword and this is what I get now.
[EMAIL PROTECTED] / # revdep-rebuild -p
Checking reverse dependencies...
Packages containing binaries and libraries broken by any package update,
will be recompiled.
Collecting system binaries and libraries... done.
(/root/.revdep-rebuild.1_files)
Collecting complete LD_LIBRARY_PATH... done.
(/root/.revdep-rebuild.2_ldpath)
Checking dynamic linking consistency...
done.
(/root/.revdep-rebuild.3_rebuild)
Assigning files to ebuilds... Nothing to rebuild
Evaluating package order... done.
(/root/.revdep-rebuild.5_order)
Dynamic linking on your system is consistent... All done.
[EMAIL PROTECTED] / #
It works and it didn't change anything. Oh well. It works, I'm happy.
Thanks
Dale
:-)
--
To err is human, I'm most certainly human.
I have four rigs:
1: Home built; Abit NF7 ver 2.0 w/ AMD 2500+ CPU, 1GB of ram and right now two
80GB hard drives.
2: Home built; Iwill KK266-R w/ AMD 1GHz CPU, 256MBs of ram and a 4GB drive.
3: Home built; Gigabyte GA-71XE4 w/ 800MHz CPU, 128MBs of ram and a 2.5GB
drive.
4: Compaq Proliant 6000 Server w/ Quad 200MHz CPUs, 128MBs of ram and a 4.3GB
SCSI drive.
All run Gentoo Linux, all run folding. #1 is my desktop, 2, 3, and 4 are set up as servers.
--
gentoo-user@gentoo.org mailing list
