[gentoo-user] revdep-rebuild problem

[gentoo-user] revdep-rebuild problem

[John P. Burkett]

Doing revdep-rebuild on an amd64 machine, I received a response
the included the following lines:
* All prepared. Starting rebuild
emerge --oneshot  app-text/xpdf:0
gnome-base/gnome-panel:0
kde-base/kdegraphics:3.5
mail-client/-MERGING-evolution:2.0
media-plugins/gst-plugins-faad:0.8
media-plugins/xmms-alsa:0
media-plugins/xmms-vorbis:0
media-video/totem:0
..........
Calculating dependencies... done!
emerge: there are no ebuilds to satisfy
"mail-client/-MERGING-evolution:2.0".

After doing emerge -C evolution, I redid revdep-rebuild but got the same
response. After doing emerge evolution, I again redid revdep-rebuild,
with the same results.

Suggestions for how to successfully run revdep-rebuild would be most
welcome.  I'm willing to sacrifice evolution if that would help.

-- 
John P. Burkett
Department of Economics
University of Rhode Island
Kingston, RI 02881-0808
USA

phone (401) 874-9195

Re: [gentoo-user] revdep-rebuild problem

[Nick Fortino]

John P. Burkett wrote:
> Doing revdep-rebuild on an amd64 machine, I received a response
> the included the following lines:
> * All prepared. Starting rebuild
> emerge --oneshot  app-text/xpdf:0
> gnome-base/gnome-panel:0
> kde-base/kdegraphics:3.5
> mail-client/-MERGING-evolution:2.0
> media-plugins/gst-plugins-faad:0.8
> media-plugins/xmms-alsa:0
> media-plugins/xmms-vorbis:0
> media-video/totem:0
> ..........
> Calculating dependencies... done!
> emerge: there are no ebuilds to satisfy
> "mail-client/-MERGING-evolution:2.0".
>
> After doing emerge -C evolution, I redid revdep-rebuild but got the same
> response. After doing emerge evolution, I again redid revdep-rebuild,
> with the same results.
>
> Suggestions for how to successfully run revdep-rebuild would be most
> welcome.  I'm willing to sacrifice evolution if that would help.
>
>   
Hmm, somehow portage got the idea there is a package named
mail-client/-MERGING-evolution, which is false. If you are lucky:
emerge -avC mail-client/-MERGING-evolution

Although that could fail, as package names aren't supposed to start with
-, so who knows what portage does with it. Next shot, clear out anything
you don't need (make sure to check the output, although these days this
command is safe unless you have done something strange).
emerge -av --depclean

Final shot is to play around in /var/db/pkg. This is where portage keeps
track of what is installed, and how, so messing around here is
inherently unsafe. I have my suspicions as to the correct thing to do
here, but I won't post it since I'm not terribly sure. Someone with more
expertise could help here, but I suspect either method 1 or 2 will work.

Nick

Re: [gentoo-user] revdep-rebuild problem

[John P. Burkett]

Nick Fortino wrote:
> John P. Burkett wrote:
>> Doing revdep-rebuild on an amd64 machine, I received a response
>> the included the following lines:
>> * All prepared. Starting rebuild
>> emerge --oneshot  app-text/xpdf:0
>> gnome-base/gnome-panel:0
>> kde-base/kdegraphics:3.5
>> mail-client/-MERGING-evolution:2.0
>> media-plugins/gst-plugins-faad:0.8
>> media-plugins/xmms-alsa:0
>> media-plugins/xmms-vorbis:0
>> media-video/totem:0
>> ..........
>> Calculating dependencies... done!
>> emerge: there are no ebuilds to satisfy
>> "mail-client/-MERGING-evolution:2.0".
>>
>> After doing emerge -C evolution, I redid revdep-rebuild but got the same
>> response. After doing emerge evolution, I again redid revdep-rebuild,
>> with the same results.
>>
>> Suggestions for how to successfully run revdep-rebuild would be most
>> welcome.  I'm willing to sacrifice evolution if that would help.
>>
>>   
> Hmm, somehow portage got the idea there is a package named
> mail-client/-MERGING-evolution, which is false.
Nick, thank you for the diagnosis.
 If you are lucky:
> emerge -avC mail-client/-MERGING-evolution
The systems's response to this was
>>> These are the packages that would be unmerged:
--- Couldn't find 'mail-client/-MERGING-evolution' to unmerge.
>>> No packages selected for removal by unmerge


> 
> Although that could fail, as package names aren't supposed to start with
> -, so who knows what portage does with it. Next shot, clear out anything
> you don't need (make sure to check the output, although these days this
> command is safe unless you have done something strange).
> emerge -av --depclean
To see what this might do, I tried emerge --pretend -av --depclean.
The response identified 163 packages to be removed, none of which appear
to be related to mail-client/-MERGING-evolution:2.0.

> 
> Final shot is to play around in /var/db/pkg. This is where portage keeps
> track of what is installed, and how, so messing around here is
> inherently unsafe. I have my suspicions as to the correct thing to do
> here, but I won't post it since I'm not terribly sure. Someone with more
> expertise could help here, but I suspect either method 1 or 2 will work.
In /var/db/pkg I found a directory mail-client/-MERGING-evolution-2.12.1
containing the following files
CATEGORY  COUNTER      FEATURES   LICENSE  SLOT
repository
CBUILD    CXXFLAGS     HOMEPAGE   NEEDED   SRC_URI
CFLAGS    DEPEND       INHERITED  PDEPEND  USE
CHOST     DESCRIPTION  IUSE       PF       environment.bz2
CONTENTS  EAPI         KEYWORDS   RDEPEND  evolution-2.12.1.ebuild

Unsure what to do next, I'd be grateful for suggestions.

-John

> 
> Nick
> 
> 


-- 
John P. Burkett
Department of Economics
University of Rhode Island
Kingston, RI 02881-0808
USA

phone (401) 874-9195

[gentoo-user] Re: revdep-rebuild problem

[ABCD]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John P. Burkett wrote:
> Doing revdep-rebuild on an amd64 machine, I received a response
> the included the following lines:
> * All prepared. Starting rebuild
> emerge --oneshot  app-text/xpdf:0
> gnome-base/gnome-panel:0
> kde-base/kdegraphics:3.5
> mail-client/-MERGING-evolution:2.0
> media-plugins/gst-plugins-faad:0.8
> media-plugins/xmms-alsa:0
> media-plugins/xmms-vorbis:0
> media-video/totem:0
> ..........
> Calculating dependencies... done!
> emerge: there are no ebuilds to satisfy
> "mail-client/-MERGING-evolution:2.0".
> 
> After doing emerge -C evolution, I redid revdep-rebuild but got the same
> response. After doing emerge evolution, I again redid revdep-rebuild,
> with the same results.
> 
> Suggestions for how to successfully run revdep-rebuild would be most
> welcome.  I'm willing to sacrifice evolution if that would help.
> 

A directory named "$(portageq vdb_path)"/*/-MERGING-* (where $(portageq
vdb_path) is usually /var/db/pkg) is created when portage is installing
a new version of a package/a new package.  It is then moved to the same
name without the -MERGING- part after the old version (if any) is
removed.  The only way that that directory would be able to exist in
normal usage is if either 1) you are in the middle of a merge, or 2)
emerge suddenly quit in the middle of an operation.  Usually, when I've
had this happen, and didn't catch it right away, I would `emerge -C
package`, then mv /var/db/pkg/cat/-MERGING-pkg-ver
/var/db/pkg/cat/pkg-ver, then `emerge -C package` again, to ensure a
clean system.  Then all that would remain is `emerge -1 package` to get
it back on the system.  This might not be the best way to do it, but
I've found it to work.

- --
ABCD
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAknYi5sACgkQOypDUo0oQOqFfgCcDOqwbMHbA7oGOuKX0T7Y5nS7
hlcAnA2bnew6N7B6x1X0uzDWXtfgBega
=tYX3
-----END PGP SIGNATURE-----

Re: [gentoo-user] Re: revdep-rebuild problem

[John P. Burkett]

ABCD wrote:
> John P. Burkett wrote:
>> Doing revdep-rebuild on an amd64 machine, I received a response
>> the included the following lines:
>> * All prepared. Starting rebuild
>> emerge --oneshot  app-text/xpdf:0
>> gnome-base/gnome-panel:0
>> kde-base/kdegraphics:3.5
>> mail-client/-MERGING-evolution:2.0
>> media-plugins/gst-plugins-faad:0.8
>> media-plugins/xmms-alsa:0
>> media-plugins/xmms-vorbis:0
>> media-video/totem:0
>> ..........
>> Calculating dependencies... done!
>> emerge: there are no ebuilds to satisfy
>> "mail-client/-MERGING-evolution:2.0".
> 
>> After doing emerge -C evolution, I redid revdep-rebuild but got the same
>> response. After doing emerge evolution, I again redid revdep-rebuild,
>> with the same results.
> 
>> Suggestions for how to successfully run revdep-rebuild would be most
>> welcome.  I'm willing to sacrifice evolution if that would help.
> 
> 
> A directory named "$(portageq vdb_path)"/*/-MERGING-* (where $(portageq
> vdb_path) is usually /var/db/pkg) is created when portage is installing
> a new version of a package/a new package.  It is then moved to the same
> name without the -MERGING- part after the old version (if any) is
> removed.  The only way that that directory would be able to exist in
> normal usage is if either 1) you are in the middle of a merge, or 2)
> emerge suddenly quit in the middle of an operation.  Usually, when I've
> had this happen, and didn't catch it right away, I would `emerge -C
> package`, then mv /var/db/pkg/cat/-MERGING-pkg-ver
> /var/db/pkg/cat/pkg-ver, then `emerge -C package` again, to ensure a
> clean system.  Then all that would remain is `emerge -1 package` to get
> it back on the system.  This might not be the best way to do it, but
> I've found it to work.
Your suggestions worked perfectly.  Thank you very much!
-John