| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
John P. Burkett wrote: |
| 5 |
> Doing revdep-rebuild on an amd64 machine, I received a response |
| 6 |
> the included the following lines: |
| 7 |
> * All prepared. Starting rebuild |
| 8 |
> emerge --oneshot app-text/xpdf:0 |
| 9 |
> gnome-base/gnome-panel:0 |
| 10 |
> kde-base/kdegraphics:3.5 |
| 11 |
> mail-client/-MERGING-evolution:2.0 |
| 12 |
> media-plugins/gst-plugins-faad:0.8 |
| 13 |
> media-plugins/xmms-alsa:0 |
| 14 |
> media-plugins/xmms-vorbis:0 |
| 15 |
> media-video/totem:0 |
| 16 |
> .......... |
| 17 |
> Calculating dependencies... done! |
| 18 |
> emerge: there are no ebuilds to satisfy |
| 19 |
> "mail-client/-MERGING-evolution:2.0". |
| 20 |
> |
| 21 |
> After doing emerge -C evolution, I redid revdep-rebuild but got the same |
| 22 |
> response. After doing emerge evolution, I again redid revdep-rebuild, |
| 23 |
> with the same results. |
| 24 |
> |
| 25 |
> Suggestions for how to successfully run revdep-rebuild would be most |
| 26 |
> welcome. I'm willing to sacrifice evolution if that would help. |
| 27 |
> |
| 28 |
|
| 29 |
A directory named "$(portageq vdb_path)"/*/-MERGING-* (where $(portageq |
| 30 |
vdb_path) is usually /var/db/pkg) is created when portage is installing |
| 31 |
a new version of a package/a new package. It is then moved to the same |
| 32 |
name without the -MERGING- part after the old version (if any) is |
| 33 |
removed. The only way that that directory would be able to exist in |
| 34 |
normal usage is if either 1) you are in the middle of a merge, or 2) |
| 35 |
emerge suddenly quit in the middle of an operation. Usually, when I've |
| 36 |
had this happen, and didn't catch it right away, I would `emerge -C |
| 37 |
package`, then mv /var/db/pkg/cat/-MERGING-pkg-ver |
| 38 |
/var/db/pkg/cat/pkg-ver, then `emerge -C package` again, to ensure a |
| 39 |
clean system. Then all that would remain is `emerge -1 package` to get |
| 40 |
it back on the system. This might not be the best way to do it, but |
| 41 |
I've found it to work. |
| 42 |
|
| 43 |
- -- |
| 44 |
ABCD |
| 45 |
-----BEGIN PGP SIGNATURE----- |
| 46 |
Version: GnuPG v2.0.11 (GNU/Linux) |
| 47 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 48 |
|
| 49 |
iEYEARECAAYFAknYi5sACgkQOypDUo0oQOqFfgCcDOqwbMHbA7oGOuKX0T7Y5nS7 |
| 50 |
hlcAnA2bnew6N7B6x1X0uzDWXtfgBega |
| 51 |
=tYX3 |
| 52 |
-----END PGP SIGNATURE----- |
Archives