From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] revdep-rebuild keeps repeating the same steps
Date: Fri, 25 May 2012 13:47:11 +0100 [thread overview]
Message-ID: <CAG2jQ8hPLfuohZ+VRRf8eHNNk3WUj+Ey4iSw_Fc+gUV9Vgn3KA@mail.gmail.com> (raw)
In-Reply-To: <20120525124136.GA2911@1126.localdomain>
On Fri, May 25, 2012 at 1:41 PM, 1126
<mailinglists@elfsechsundzwanzig.de> wrote:
> Hello list!
>
> When I run revdep-rebuild, it keeps repeating the same steps over and over
> again.
>
> Here is what I mean:
>
> * 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
> * Generated new 1_files.rr
> * Collecting complete LD_LIBRARY_PATH
> * Generated new 2_ldpath.rr
> * Checking dynamic linking consistency
> [ 36% ] * broken /usr/lib32/libavdevice.so.53.4.100 (requires
> libpulse-simple.so.0
> libpulse.so.0)
> [ 100% ]
> * Generated new 3_broken.rr
> * Assigning files to packages
> * /usr/lib32/libavdevice.so.53.4.100 ->
> app-emulation/emul-linux-x86-medialibs
> * Generated new 4_raw.rr and 4_owners.rr
> * Cleaning list of packages to rebuild
> * Generated new 4_pkgs.rr
> * Assigning packages to ebuilds
> * Generated new 4_ebuilds.rr
> * Evaluating package order
> * Generated new 5_order.rr
> * All prepared. Starting rebuild
> emerge --complete-graph=y --oneshot app-emulation/emul-linux-x86-medialibs:0
> ..........
> Calculating dependencies... done!
>
>>>> Verifying ebuild manifests
>
>>>> Emerging (1 of 1) app-emulation/emul-linux-x86-medialibs-20120520
> * emul-linux-x86-medialibs-20120520.tar.xz RMD160 SHA1 SHA256 size ;-) ...
> [ ok ]
>>>> Unpacking source...
>>>> Unpacking emul-linux-x86-medialibs-20120520.tar.xz to
> /var/tmp/portage/app-emulation/emul-linux-x86-medialibs-20120520/work
>>>> Source unpacked in
> /var/tmp/portage/app-emulation/emul-linux-x86-medialibs-20120520/work
>>>> Preparing source in
> /var/tmp/portage/app-emulation/emul-linux-x86-medialibs-20120520/work ...
>>>> Source prepared.
>>>> Configuring source in
> /var/tmp/portage/app-emulation/emul-linux-x86-medialibs-20120520/work ...
>>>> Source configured.
>>>> Compiling source in
> /var/tmp/portage/app-emulation/emul-linux-x86-medialibs-20120520/work ...
>>>> Source compiled.
>>>> Test phase [not enabled]: app-emulation/emul-linux-x86-medialibs-20120520
>
>>>> Install emul-linux-x86-medialibs-20120520 into
> /var/tmp/portage/app-emulation/emul-linux-x86-medialibs-20120520/image/ category
> app-emulation
>>>> Completed installing emul-linux-x86-medialibs-20120520 into
> /var/tmp/portage/app-emulation/emul-linux-x86-medialibs-20120520/image/
>
>
> * QA Notice: The following files contain runtime text relocations
> * Text relocations force the dynamic linker to perform extra
> * work at startup, waste system resources, and may pose a security
> * risk. On some architectures, the code may not even function
> * properly, if at all.
> * For more information, see http://hardened.gentoo.org/pic-fix-guide.xml
> * Please include the following list of files in your report:
> * TEXTREL usr/lib32/libx264.so.120
>
>
>>>> Installing (1 of 1) app-emulation/emul-linux-x86-medialibs-20120520
>>>> Auto-cleaning packages...
>
>>>> No outdated packages were found on your system.
>
> * GNU info directory index is up-to-date.
> * Build finished correctly. Removing temporary files...
> * You can re-run revdep-rebuild to verify that all libraries and binaries
> * are fixed. Possible reasons for remaining inconsistencies include:
> * orphaned files
> * deep dependencies
> * packages installed outside of portage's control
> * specially-evaluated libraries
>
>
> It keeps complaining about libavdevice.so and them re-emerges
> app-emulation/emul-linux-x86-medialibs-20120520.
>
>
> When I would re-run it right now, it would again complain about libavdevice and
> would again re-emerge app-emulation/emul-linux-x86-medialibs..
>
> Has anyone any idea how to fix this?
>
> Thanks in advance,
> Christian.
>
>
This is bug: https://bugs.gentoo.org/show_bug.cgi?id=416751
Bugzilla+search is your friend ;)
next prev parent reply other threads:[~2012-05-25 12:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 12:41 [gentoo-user] revdep-rebuild keeps repeating the same steps 1126
2012-05-25 12:47 ` Markos Chandras [this message]
2012-05-25 13:32 ` 1126
2012-05-25 12:47 ` Alan McKinnon
2012-05-25 13:33 ` 1126
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAG2jQ8hPLfuohZ+VRRf8eHNNk3WUj+Ey4iSw_Fc+gUV9Vgn3KA@mail.gmail.com \
--to=hwoarang@gentoo.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox