| 1 |
On Sat, 17 Nov 2007 00:17:26 -0500, de Almeida, Valmor F. wrote: |
| 2 |
|
| 3 |
> How do I find out why apr-0.9.12 and apr-util-0.9.12 are pulled back |
| 4 |
> when using revdep-rebuild? |
| 5 |
[snip] |
| 6 |
> Here is the result from revdep-rebuild. |
| 7 |
|
| 8 |
> ------------------------------------------------------------------ |
| 9 |
> ->revdep-rebuild --pretend --verbose |
| 10 |
> Configuring search environment for revdep-rebuild |
| 11 |
> |
| 12 |
> Checking reverse dependencies... |
| 13 |
> |
| 14 |
> Packages containing binaries and libraries broken by a package update |
| 15 |
> will be emerged. |
| 16 |
> |
| 17 |
> ....... snip |
| 18 |
> |
| 19 |
> All prepared. Starting rebuild... |
| 20 |
> emerge --oneshot --pretend --verbose =dev-libs/apr-util-0.9.12 |
| 21 |
> |
| 22 |
> These are the packages that would be merged, in order: |
| 23 |
> |
| 24 |
> Calculating dependencies... done! |
| 25 |
> [ebuild NS ] dev-libs/apr-0.9.12 USE="-ipv6 -urandom" 0 kB |
| 26 |
> [ebuild NS ] dev-libs/apr-util-0.9.12 USE="berkdb gdbm -ldap" 0 kB |
| 27 |
|
| 28 |
It looks like you still have the temporary files from a previous |
| 29 |
revdep-rebuild run, so you don't get to see the list of broken packages. Add --ignore to the command. |
| 30 |
|
| 31 |
|
| 32 |
-- |
| 33 |
Neil Bothwick |
| 34 |
|
| 35 |
Failure is not an option. It comes bundled with your Microsoft product. |
Archives