Hi all.

In order to automatically install the gnome-commander (still not in portage) I had to add soor-overlay.
After that I experience a problem.
On emerge -DNuav world I get
These are the packages that would be merged, in order:

Calculating dependencies... done!

emerge: there are no ebuilds to satisfy "x11-misc/emacs-desktop".
(dependency required by "app-editors/emacs-git-23.0.9999" [ebuild])
(dependency required by "app-emacs/emacs-common-gentoo-1.2" [installed])
(dependency required by "app-editors/emacs-23.1" [installed])
(dependency required by "emacs" [argument])

So the problem is understandable - the new overlay has a "newer" version of emacs which wants to be updated. The version from the overlay requires the emacs-desktop package, which is not included on the overlay itself and seems to be removed from the main repository.
Googling did not give me any ideas.

So, what is the most elegant and wise solution that will not break the future fully-automated updates?


Thanks.
Gene

I found quite odd that a file manager depends on such a beast like emacs, so I added the overlay myself and tried to emerge gnome-commander. It certainly doesn't require emacs, and looking at the ebuild here it's not listed as a dependency either:

http://gentoo-overlays.zugaina.org/s....3.0.99.ebuild

Whatever your problem is, it's not in gnome-commander, look at the rest of the overlays you have installed (and if you don't want to go insane, try to keep them at a minimum). Do you really need the git branck of emacs or is just so update paranoia? Dealing with git software, specially big packages like emacs, can be quite tedious, overall if the quality of the overlay is not optimal.

Your best bet is to report this to the people that maintain these overlay. They surely know better than anyway what's going on. At first sight, I only can tell you that a package that should be there is not there, which produces an inconsistency which can't be solved by portage in any way. A dependency is missing.

Thank you for your reply. Unfortunately, nothing new in it.
Of course the gnome-commander does not depend on the emacs package.
I have emacs installed itself. What is the problem, as I understand, is that _the same overlay_ provided the newer version of emacs, which (with my ~amd64 system) wanted to be re-emerged.
But this version also depends on the package emacs-desktop, not provided in any of my overlays, nor in the portage main tree.

So may be I have to mask the specific emacs-git package and try again.


Hmm. And more details: emacs-git is not actually installed/recorded in the world file.
But the emacs-git ebuild is definitely from the newly added soor-overlay.
So the question is - _why_ was it pulled for the upgrade.

Okay, I have solved the problem by adding one more overlay - the emacs one. No the emacs upgrade is not required, nor the emacs-desktop package

I have no idea why was it pulled, I am not familiar with this overlay. But in my opinion, any overlay should be self-contained, so the user don't need to go fishing ebuilds in the net. In any case, this might help in the future to search for ebuilds in overlays if this happens again:

http://gentoo.zapto.org/

Okay, it was more theoretic question than practical )
In any case, thanks again