On Sun, 2005-05-08 at 16:03 +0200, Holly Bostick wrote: > Alex Bennee wrote: > > Both versions are ~amd64 so I don't think that is the reason. Any idea > > what is causing emerge to think it wants to revert to a broken package? > > There could be a couple of reasons reasons: > > 1) you're running a amd64 system (~amd64 is not set in /etc/make.conf), > and you've installed evolution-data-server with ACCEPT_KEYWORDS instead > of with an entry in /etc/portage/package.keywords; > > 2) something else is installed that depends on the earlier version of > evo-data-server and must downgrade evo-data-server to the version it can > use.
Both evolution and the data server are set ~amd64 in package.keywords > For 2) instead of emerge -upDv, try > > emerge -upDtv > > to get a tree view of what is trying to downgrade evo-data-server. > Perhaps that program needs to be updated to an unstable version that > will accept the higher version of evo-data-server. 00:56 [EMAIL PROTECTED] [portage] >emerge -upDtv world These are the packages that I would merge, in reverse order: Calculating world dependencies ...done! [nomerge ] gnome-extra/libgail-gnome-1.1.0 -debug [nomerge ] gnome-base/gnome-panel-2.8.2 -debug -doc +eds* [ebuild UD] gnome-extra/evolution-data-server-1.0.4 [1.2.1] -debug -doc It seems that +eds support in gnome-panel wants a fixed version of evolution-data-server. I don't suppose there is a easy way of forcing the build to build against the latest eds to check its happy? Or is it easiest to just directly tweak the ebuild to test? -- Alex, homepage: http://www.bennee.com/~alex/ We're all looking for a woman who can sit in a mini-skirt and talk philosophy, executing both with confidence and style. -- gentoo-user@gentoo.org mailing list
