Dotaz: Gentoo - problem s upgrade

[pdp7]

atahualpa cernyv # revdep-rebuild   
Configuring search environment for revdep-rebuild

Checking reverse dependencies...

Packages containing binaries and libraries broken by a package update
will be emerged.

Collecting system binaries and libraries... done.
  (/root/.revdep-rebuild.1_files)

Collecting complete LD_LIBRARY_PATH... done.
  (/root/.revdep-rebuild.2_ldpath)

Checking dynamic linking consistency...
  broken /usr/bin/finch (requires  libpanelw.so.5)
  broken /usr/lib/libgnt.so.0.0.0 (requires  libpanelw.so.5)
  broken /usr/lib/python2.4/lib-dynload/_curses_panel.so (requires  libpanelw.so.5)
  broken /usr/lib64/libgnt.so.0.0.0 (requires  libpanelw.so.5)
  broken /usr/lib64/python2.4/lib-dynload/_curses_panel.so (requires  libpanelw.so.5)
 done.
  (/root/.revdep-rebuild.3_rebuild)

Assigning files to ebuilds... done.
  (/root/.revdep-rebuild.4_ebuilds)

Evaluating package order...
Warning: Failed to resolve package order.
Will merge in "random" order!
Possible reasons:
- An ebuild is no longer in the portage tree.
- An ebuild is masked, use /etc/portage/packages.keyword
  and/or /etc/portage/package.unmask to unmask it
..... done.
  (/root/.revdep-rebuild.5_order)

All prepared. Starting rebuild...
emerge --oneshot  =dev-lang/python-2.4.4-r5 =net-im/pidgin-2.1.0 
..........
Calculating dependencies -
emerge: there are no ebuilds to satisfy "=net-im/pidgin-2.1.0".


revdep-rebuild failed to emerge all packages
you have the following choices:

- if emerge failed during the build, fix the problems and re-run revdep-rebuild
    or
- use -X or --package-names as first argument (trys to rebuild package, not exact
  ebuild)
    or
- set ACCEPT_KEYWORDS="~<your platform>" and/or /etc/portage/package.unmask
  (and remove /root/.revdep-rebuild.5_order to be evaluated again)
    or
- modify the above emerge command and run it manually
    or
- compile or unmerge unsatisfied packages manually, remove temporary files and
  try again (you can edit package/ebuild list first)

To remove temporary files, please run:
rm /root/.revdep-rebuild*.?_*
atahualpa cernyv # 

Co dal? Prekompilovat vsechno, jenom to ne! Gentooisti prosim pomoc!

Odpovědi

[mirojira]

Stalo sa mi uz vselico, ale toto som este nevidel, takze sa len domnievam, ze mate vymazany ebuild k net-im/pidgin-2.1.0. Stare ebuilty by ste mal najst na http://sources.gentoo.org/viewcvs.py.Budete zrejme musiet nahradit aktualny ebuild verziou 2.1.0 a spustit revdep-rebuild znovu

[pdp7]

Zkusim, zatim diky.

[jm]

Zadny stary ebuildy nikde neshanej a pust revdep-rebuild -X

[pdp7]

To jsem zkousel, na konci vypsalo "all consistent", pak jsem zkusil znova revdep-rebuild bez parametru a zase ta chyba viz. moje otazka. Zkusim to jeste jednou.

[AraxoN]

Verzia 2.1.0 balíčku net-im/pidgin už nie je v portage, takže ju emerge nevie odznova prekompilovať. Namiesto nej sú v portage verzie 2.2.1 a 2.2.2. Takže miesto príkazu

emerge --oneshot =net-im/pidgin-2.1.0

ktorý sa revdep-rebuild pokúša spustiť, je treba spustiť update bez vyžadovania konkrétnej verzie, napríklad takto:

emerge --oneshot net-im/pidgin

Potom treba zmazať tie dočasné súbory, ktoré predtým revdep-rebuild vytvoril:

rm /root/.revdep-rebuild*.?_*

a spustiť revdep-rebuild odznova.

[pdp7]

atahualpa ~ # emerge --oneshot net-im/pidgin
Calculating dependencies... done!
>>> Verifying ebuild Manifests...

>>> Emerging (1 of 1) net-im/pidgin-2.2.1 to /
 * pidgin-2.2.1.tar.bz2 RMD160 SHA1 SHA256 size  ...                   [ ok ]
 * checking ebuild checksums  ...                                      [ ok ]
 * checking auxfile checksums  ...                                     [ ok ]
 * checking miscfile checksums  ...                                    [ ok ]
 * checking pidgin-2.2.1.tar.bz2  ...                                  [ ok ]
 * 
 * We strongly recommend that you backup your ~/.gaim directory
 * before running Pidgin for the first time. Things you should be
 * on the lookout for include problems with preferences being lost
 * or forgotten, buddy icons not working as you expect, plugins or
 * other external files not properly being found.
 * 
 * If you experience problems with pidgin, file them as bugs with
 * Gentoo's bugzilla, http://bugs.gentoo.org.  DO NOT report them
 * as bugs with pidgin's bug tracker, and by all means DO NOT
 * seek help in #pidgin.
 * 
 * Be sure to USE="debug" and include a backtrace for any seg
 * faults, see http://developer.pidgin.im/wiki/GetABacktrace for details on
 * backtraces.
 * 
 * Please read the pidgin FAQ at http://developer.pidgin.im/wiki/FAQ
 * 
 * 
 * You need to rebuild sys-libs/ncurses with USE=unicode in order
 * to build finch the console client of pidgin.
 * 
 * 
 * ERROR: net-im/pidgin-2.2.1 failed.
 * Call stack:
 *             ebuild.sh, line 1717:  Called dyn_setup
 *             ebuild.sh, line  768:  Called qa_call 'pkg_setup'
 *             ebuild.sh, line   44:  Called pkg_setup
 *   pidgin-2.2.1.ebuild, line  131:  Called die
 * The specific snippet of code:
 *              die "Configure failed"
 *  The die message:
 *   Configure failed
 * 
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/net-im/pidgin-2.2.1/temp/build.log'.
 * 

 * Messages for package net-im/pidgin-2.2.1:

 * 
 * You need to rebuild sys-libs/ncurses with USE=unicode in order
 * to build finch the console client of pidgin.
 * 
 * 
 * ERROR: net-im/pidgin-2.2.1 failed.
 * Call stack:
 *             ebuild.sh, line 1717:  Called dyn_setup
 *             ebuild.sh, line  768:  Called qa_call 'pkg_setup'
 *             ebuild.sh, line   44:  Called pkg_setup
 *   pidgin-2.2.1.ebuild, line  131:  Called die
 * The specific snippet of code:
 *              die "Configure failed"
 *  The die message:
 *   Configure failed
 * 
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/net-im/pidgin-2.2.1/temp/build.log'.
 * 
 * 
 * We strongly recommend that you backup your ~/.gaim directory
 * before running Pidgin for the first time. Things you should be
 * on the lookout for include problems with preferences being lost
 * or forgotten, buddy icons not working as you expect, plugins or
 * other external files not properly being found.
 * 
 * If you experience problems with pidgin, file them as bugs with
 * Gentoo's bugzilla, http://bugs.gentoo.org.  DO NOT report them
 * as bugs with pidgin's bug tracker, and by all means DO NOT
 * seek help in #pidgin.
 * 
 * Be sure to USE="debug" and include a backtrace for any seg
 * faults, see http://developer.pidgin.im/wiki/GetABacktrace for details on
 * backtraces.
 * 
 * Please read the pidgin FAQ at http://developer.pidgin.im/wiki/FAQ
 * 

[pdp7]

Cim dal lepe!

[jm]

Cim dal lepe!

You need to rebuild sys-libs/ncurses with USE=unicode in order to build finch the console client of pidgin.

Mozna kdyby sis tak precetl, co pastujes, predtim nez si zase zacnes na neco stezovat...

[pdp7]

Dekuji to bude ono

[pdp7]

Bylo to ono.