On Mon, 26 Nov 2012 16:34:33 -0800 Igor Korot <[email protected]> wrote:
> Hi, > Well, it's kind of OK list... ;-) > > * Messages for package kde-base/konq-plugins-3.5.10: > > * emerge --keep-going: kde-base/konq-plugins-3.5.10 dropped due to > * unsatisfied dependency. > * > * The following 21 packages have failed to build or install: > * [...] > > What would be the first package to look at? (meaning most important one?) Let's see here. Ignore packages with the -meta suffix, first off, since they're just aggregators for other packages. Secondly, since Portage's dependency identification sometimes messes up in --keep-going runs, attempt to individually re-emerge any package that didn't get far enough to produce a log. Start with the kde-base packages: > * (kde-base/kdm-3.5.10::kde-sunset, ebuild scheduled for merge) > * (kde-base/kdebase-startkde-3.5.10-r5::kde-sunset, ebuild scheduled for > merge) > * (kde-base/konqueror-3.5.10::kde-sunset, ebuild scheduled for merge) > * (kde-base/kdesktop-3.5.10::kde-sunset, ebuild scheduled for merge) > * (kde-base/konsole-3.5.10::kde-sunset, ebuild scheduled for merge) Most of these packages are important to the basic functioning of KDE, and you need to get them merged if you want a functioning desktop. Then look at the extras: > * (kde-base/kmail-3.5.10::kde-sunset, ebuild scheduled for merge) > * (kde-base/konqueror-akregator-3.5.10::kde-sunset, ebuild scheduled for > merge) > * (kde-base/konq-plugins-3.5.10::kde-sunset, ebuild scheduled for merge) > * (kde-base/kontact-specialdates-3.5.10::kde-sunset, ebuild scheduled for > merge) These packages are less important, and if you can live with the idea of using a different (probably GTK-based) mailer and calendar application, you don't absolutely need them. For the remainder: > * (kde-base/kcontrol-3.5.10::kde-sunset, ebuild scheduled for merge) > * (kde-base/ksvg-3.5.10::kde-sunset, ebuild scheduled for merge) > * (kde-base/kopete-3.5.10-r5::kde-sunset, ebuild scheduled for merge) > * (kde-base/kate-plugins-3.5.10::kde-sunset, ebuild scheduled for merge) > * (kde-base/konsolekalendar-3.5.10::kde-sunset, ebuild scheduled for merge) > * (kde-base/korganizer-3.5.10::kde-sunset, ebuild scheduled for merge) and for any packages on the other lists that still won't merge, use the equery command to determine what the most recent KDE3 ebuild is: # equery meta kcontrol * kde-base/kcontrol [gentoo] Herd: kde ([email protected]) Maintainer: None specified Upstream: None specified Homepage: http://www.kde.org/ Location: /usr/portage/kde-base/kcontrol Keywords: 3.5.10:3.5: alpha amd64 hppa ia64 ppc ppc64 sparc x86 Keywords: 3.5.10-r1:3.5: ~alpha ~amd64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~sparc ~x86 ~x86-fbsd <--this one Keywords: 4.8.5:4: amd64 ppc x86 ~ppc64 ~x86-fbsd Keywords: 4.9.1:4: Keywords: 4.9.2:4: ~amd64 ~amd64-linux ~arm ~x86 ~x86-linux and unmask it, then try to merge again. If you don't have the equery command, emerge gentoolkit. The packages you absolutely need to get working are the ones I shortlisted as part of kde-base, and kcontrol. Most of the others can be worked around by substituting other applications with the same functionality. Note that kopete has at least one broken plugin (I think it's jabber) that may not compile under any circumstances. Oh, and incidentally, No. >Should I top-post? Good luck.
