![]() |
|
|
|||
|
emerge problems
For a while I've had freetype blocked in packages.provided because one
update at one point messed up every single danged font on every application. Recently I found out that when it was stopping emerges: -------------------------------------------------------------------------- WARNING: A requested package will not be merged because it is listed in package.provided: media-libs/freetype pulled in by 'world' This problem can be solved in one of the following ways: A) Use emaint to clean offending packages from world (if not installed). B) Uninstall offending packages (cleans them from world). C) Remove offending entries from package.provided. The best course of action depends on the reason that an offending package.provided entry exists. -------------------------------------------------------------------------- it was leaving several updates undone. I found out quite by accident, for example, that updates for ksvg kdvi kdelibs kcontrol librsvg and imlib2 were available and not implemented. So I commented out the line in packages.provided that stifled freetype and ran emerge -auD world, and got this: -------------------------------------------------------------------------- Calculating world dependencies | !!! Multiple versions within a single package slot have been !!! pulled into the dependency graph: media-libs/freetype:2 ('installed', '/', 'media-libs/freetype-2.3.3', 'nomerge') pulled in by ('installed', '/', 'kde-base/ksvg-3.5.8', 'nomerge') ('ebuild', '/', 'media-libs/freetype-2.1.10-r3', 'merge') pulled in by ('installed', '/', 'gnome-base/libgnomeprint-2.18.3', 'nomerge') ('installed', '/', 'media-gfx/imagemagick-6.3.7.9', 'nomerge') ('installed', '/', 'x11-libs/qt-4.3.2-r1', 'nomerge') (and 24 more) -------------------------------------------------------------------------- I'm lost now. -- Iran tells us what the mainstream media won't: "A new opinion poll suggests that over 54 percent of Americans do not trust mainstream media and consider news websites more reliable." <http://www.presstv.ir/detail.aspx?id=46837§ionid=3510203> |
|
|||
|
Re: emerge problems
clifto wrote:
> -------------------------------------------------------------------------- > Calculating world dependencies | > !!! Multiple versions within a single package slot have been > !!! pulled into the dependency graph: > > media-libs/freetype:2 > > ('installed', '/', 'media-libs/freetype-2.3.3', 'nomerge') pulled in by > ('installed', '/', 'kde-base/ksvg-3.5.8', 'nomerge') > > ('ebuild', '/', 'media-libs/freetype-2.1.10-r3', 'merge') pulled in by > ('installed', '/', 'gnome-base/libgnomeprint-2.18.3', 'nomerge') > ('installed', '/', 'media-gfx/imagemagick-6.3.7.9', 'nomerge') > ('installed', '/', 'x11-libs/qt-4.3.2-r1', 'nomerge') > (and 24 more) > -------------------------------------------------------------------------- > > I'm lost now. Freetype is a slotted package. This means that portage allows for many major versions of the package to be installed at the same time. Each major version gets installed into its own so-called slot. Freetype has two slots: one for versions 1.x, and another for versions 2.x. The two slots are identified by media-libs/freetype:1 and media-libs/freetype:2. What's happening to you is that various programs are trying to pull in different versions of freetype /whithin the same slot/ (namely freetype:2). In your case, you have freetype-2.3.3 installed (which fills the :2 slot), but other packages (libgnomeprint, imagemagick, etc.) are trying to install freetype-2.1.10-r3, which would also go into the same slot. That is a bit strange, since the packages that are trying to pull in freetype-2.1.10-r3 do not depend specifically on that version, but rather are fine with just any freetype:2 version. Chack that, besides package.provided, you don't have any entry for media-libs/freetype in /etc/portage/package.mask or /etc/portage/package.unmask that locks freetype to a certain version. Also remove any entry for media-libs/freetype you might have in /etc/portage/package.keywords. Then, try this at first: # emerge --sync # emerge -uDavNt world If it's still complaining, try this: # quickpkg freetype # emerge -C freetype # emerge -uDavNt world and see what it tells you. If things break after removing freetype, you can restore it by doing: # emerge -k freetype As a side note, what's the output of # eix freetype ? if you don't have eix installed, emerge it by doing # emerge eix |
|
|||
|
Re: emerge problems
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1 On Wed, 12 Mar 2008 11:12:11 +0100, pk <pk@pk.pk> probably wrote (unless it was a Kook): > In your case, you have freetype-2.3.3 installed (which fills the :2 slot), > but other packages (libgnomeprint, imagemagick, etc.) are trying to install > freetype-2.1.10-r3, which would also go into the same slot. > That is a bit strange, since the packages that are trying to pull in > freetype-2.1.10-r3 do not depend specifically on that version, but rather > are fine with just any freetype:2 version. > Chack that, besides package.provided, you don't have any entry for > media-libs/freetype in /etc/portage/package.mask > or /etc/portage/package.unmask that locks freetype to a certain version. > Also remove any entry for media-libs/freetype you might have > in /etc/portage/package.keywords. > I also have this problem. I ended up masking off anything below -2.2. I didn't have it in package.keywords. I'm half tempted to try your suggestions. - -- eval join"",map{chomp;s/^.+?>\s*//;$_}grep{/>/}<DATA>; __DATA__ .' .' Kelly "STrRedWolf" Price -- WolfSkunk Designs xX xX .' http://stalag99.net tygris @ same domain "X "X X .' _____. X" X > XXXXXXXx. X".' > '"XXXXXX| X > "XXX| X" > 'XX' > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) iD8DBQFH3T2Iz/HaS8OXiYERAsWIAJ940UzON6bNl5iIQMFdXuozPU8TrQCfXAo7 60hHRU4ZCIaJ7xIz8ZcXQo8= =v2SV -----END PGP SIGNATURE----- |
![]() |
|
| Thread Tools | Search this Thread |
| Display Modes | |
|
|