| 1 |
On Mon, 26 Nov 2012 16:34:33 -0800 |
| 2 |
Igor Korot <ikorot01@×××××.com> wrote: |
| 3 |
|
| 4 |
> Hi, |
| 5 |
> Well, it's kind of OK list... ;-) |
| 6 |
> |
| 7 |
> * Messages for package kde-base/konq-plugins-3.5.10: |
| 8 |
> |
| 9 |
> * emerge --keep-going: kde-base/konq-plugins-3.5.10 dropped due to |
| 10 |
> * unsatisfied dependency. |
| 11 |
> * |
| 12 |
> * The following 21 packages have failed to build or install: |
| 13 |
> * |
| 14 |
[...] |
| 15 |
> |
| 16 |
> What would be the first package to look at? (meaning most important one?) |
| 17 |
|
| 18 |
Let's see here. Ignore packages with the -meta suffix, first off, since they're just |
| 19 |
aggregators for other packages. Secondly, since Portage's dependency identification |
| 20 |
sometimes messes up in --keep-going runs, attempt to individually re-emerge |
| 21 |
any package that didn't get far enough to produce a log. Start with the kde-base packages: |
| 22 |
|
| 23 |
> * (kde-base/kdm-3.5.10::kde-sunset, ebuild scheduled for merge) |
| 24 |
> * (kde-base/kdebase-startkde-3.5.10-r5::kde-sunset, ebuild scheduled for merge) |
| 25 |
> * (kde-base/konqueror-3.5.10::kde-sunset, ebuild scheduled for merge) |
| 26 |
> * (kde-base/kdesktop-3.5.10::kde-sunset, ebuild scheduled for merge) |
| 27 |
> * (kde-base/konsole-3.5.10::kde-sunset, ebuild scheduled for merge) |
| 28 |
|
| 29 |
Most of these packages are important to the basic functioning of KDE, and you need |
| 30 |
to get them merged if you want a functioning desktop. Then look at the extras: |
| 31 |
|
| 32 |
> * (kde-base/kmail-3.5.10::kde-sunset, ebuild scheduled for merge) |
| 33 |
> * (kde-base/konqueror-akregator-3.5.10::kde-sunset, ebuild scheduled for merge) |
| 34 |
> * (kde-base/konq-plugins-3.5.10::kde-sunset, ebuild scheduled for merge) |
| 35 |
> * (kde-base/kontact-specialdates-3.5.10::kde-sunset, ebuild scheduled for merge) |
| 36 |
|
| 37 |
These packages are less important, and if you can live with the idea of using a |
| 38 |
different (probably GTK-based) mailer and calendar application, you don't |
| 39 |
absolutely need them. |
| 40 |
|
| 41 |
For the remainder: |
| 42 |
|
| 43 |
> * (kde-base/kcontrol-3.5.10::kde-sunset, ebuild scheduled for merge) |
| 44 |
> * (kde-base/ksvg-3.5.10::kde-sunset, ebuild scheduled for merge) |
| 45 |
> * (kde-base/kopete-3.5.10-r5::kde-sunset, ebuild scheduled for merge) |
| 46 |
> * (kde-base/kate-plugins-3.5.10::kde-sunset, ebuild scheduled for merge) |
| 47 |
> * (kde-base/konsolekalendar-3.5.10::kde-sunset, ebuild scheduled for merge) |
| 48 |
> * (kde-base/korganizer-3.5.10::kde-sunset, ebuild scheduled for merge) |
| 49 |
|
| 50 |
and for any packages on the other lists that still won't merge, use the |
| 51 |
equery command to determine what the most recent KDE3 ebuild is: |
| 52 |
|
| 53 |
# equery meta kcontrol |
| 54 |
* kde-base/kcontrol [gentoo] |
| 55 |
Herd: kde (kde@g.o) |
| 56 |
Maintainer: None specified |
| 57 |
Upstream: None specified |
| 58 |
Homepage: http://www.kde.org/ |
| 59 |
Location: /usr/portage/kde-base/kcontrol |
| 60 |
Keywords: 3.5.10:3.5: alpha amd64 hppa ia64 ppc ppc64 sparc x86 |
| 61 |
Keywords: 3.5.10-r1:3.5: ~alpha ~amd64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~sparc ~x86 ~x86-fbsd <--this one |
| 62 |
Keywords: 4.8.5:4: amd64 ppc x86 ~ppc64 ~x86-fbsd |
| 63 |
Keywords: 4.9.1:4: |
| 64 |
Keywords: 4.9.2:4: ~amd64 ~amd64-linux ~arm ~x86 ~x86-linux |
| 65 |
|
| 66 |
and unmask it, then try to merge again. If you don't have the equery command, |
| 67 |
emerge gentoolkit. |
| 68 |
|
| 69 |
The packages you absolutely need to get working are the ones I shortlisted as part |
| 70 |
of kde-base, and kcontrol. Most of the others can be worked around by substituting |
| 71 |
other applications with the same functionality. Note that kopete has at least one |
| 72 |
broken plugin (I think it's jabber) that may not compile under any circumstances. |
| 73 |
|
| 74 |
Oh, and incidentally, |
| 75 |
|
| 76 |
No. |
| 77 |
>Should I top-post? |
| 78 |
|
| 79 |
Good luck. |
Archives