![]() |
[GENTOO] emerge gambas
не могу понять в чем дело, помогите плиз
Цитата:
|
>Blocked Packages
ни о чем не говорит? заблокированный пэкаж, глянь файлы маскировки /etc/portage/package... и в хэндбуке гентушном есть очень хорошая статья по этому поводу, ;-) |
а лучше доставь
emerge -pv gambas |
Цитата:
|
emerge -C poppler poppler-bindings && emerge gambas
|
[blocks B ] app-text/poppler ("app-text/poppler" is blocking dev-libs/poppler-0.10.7)
[blocks B ] dev-libs/poppler ("dev-libs/poppler" is blocking app-text/poppler-bindings-0.10.5, app-text/poppler-0.10.5-r1) [blocks B ] app-text/poppler-bindings ("app-text/poppler-bindings" is blocking dev-libs/poppler-0.10.7) то что заблокированны это я понял, а что делать? |
Цитата:
|
ну поплеры я удалил)))
# emerge gambas Calculating dependencies... done! >>> Verifying ebuild manifests >>> Starting parallel fetch >>> Emerging (1 of 3) kde-base/kdelibs-3.5.10-r6 * kde-3.5.9-seli-xinerama.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * kdelibs-3.5-patchset-15.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * kdelibs-3.5.10.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * On some setups, which rely on the correct update of utmp records, not using * utempter might not update them correctly. If you experience unexpected * behaviour, try to rebuild kde-base/kdelibs with utempter use-flag enabled. ^C Exiting on signal 2 * The ebuild phase 'setup' has exited unexpectedly. This type of behavior * is known to be triggered by things such as failed variable assignments * (bug #190128) or bad substitution errors (bug #200313). Normally, before * exiting, bash should have displayed an error message above. If bash did * not produce an error message above, it's possible that the ebuild has * called `exit` when it should have called `die` instead. This behavior * may also be triggered by a corrupt bash binary or a hardware problem * such as memory or cpu malfunction. If the problem is not reproducible or * it appears to occur randomly, then it is likely to be triggered by a * hardware problem. If you suspect a hardware problem then you should try * some basic hardware diagnostics such as memtest. Please do not report * this as a bug unless it is consistently reproducible and you are sure * that your bash binary and hardware are functioning properly. >>> Failed to emerge kde-base/kdelibs-3.5.10-r6, Log file: >>> '/var/lib/entropy/logs/kde-base:kdelibs-3.5.10-r6:20090621-191318.log' |
Код:
echo "kde-base/kdelibs utempter" >> /etc/portage/package.useКод:
emerge gambas |
чувак не е помогло((((
Installing (1 of 3) kde-base/kdelibs-3.5.10-r6 * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / <filename>` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at http://bugs.gentoo.org unless you report exactly which * two packages install the same file(s). Once again, please do NOT file * a bug report unless you have completely understood the above message. * * package kde-base/kdelibs-3.5.10-r6 NOT merged * * Detected file collision(s): * * /etc/env.d/45kdepaths-3.5 * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * None of the installed packages claim the file(s). * * Package 'kde-base/kdelibs-3.5.10-r6' NOT merged due to file * collisions. If necessary, refer to your elog messages for the whole * content of the above message. >>> Failed to install kde-base/kdelibs-3.5.10-r6, Log file: >>> '/var/lib/entropy/logs/kde-base:kdelibs-3.5.10-r6:20090621-205307.log' |
| Время: 16:07 |