File in manifest not found portage-2.2_rc10.ebuild [Solved]

[joe3]

I don't know whats up with this. But I wanted to install a couple of things today. One of which, the krusader filemanager who's web page suggested that it could be emerged on gentoo, wasn't found by equo search. So I did an 'emerge --sync && layman -S' on my 64 bit laptop which told me I should emerge portage, after which I emerged krusader without a hitch. Then I tried to repeat the process with my 32 bit desktop... the sync appeared to to have the same results, and it likewise wants me to emerge portage. But when I try I get an error message:

!!! A file listed in the Manifest could not be found: /usr/portage/sys-apps/portage/portage-2.2_rc10.ebuild

I don't know what caused the problem, but if I can't make emerge current, then I'm not so sure I should try to "emerge" krusader...

1) Is this a known problem with a known fix so I can use emerge?

2) What do I have to do so that equo would find krusader???

I suspect it might be a difference in repository settings, But I've never changed either one from the defaults they were installed with...

Thanks

--
joe3

[wolfden]

moved to correct forum

try:

Code: Select all

# ebuild /usr/portage/sys-apps/portage/portage-2.2_rc10.ebuild digest

than

Code: Select all

# emerge portage

[joe3]

J(tWdy)P -> /home/jtwdyp/com/dnlo
> su -c mc
Password:
UnderTree =-> ebuild /usr/portage/sys-apps/portage/portage-2.2_rc10.ebuild digest
'/usr/portage/sys-apps/portage/portage-2.2_rc10.ebuild' does not exist.
UnderTree =->
UnderTree =-> cd /usr/portage/sys-apps/portage/
UnderTree =-> ls
ChangeLog metadata.xml portage-2.1.4.4.ebuild portage-2.2_rc9.ebuild
files portage-2.0.51.22-r3.ebuild portage-2.1.5.6.ebuild
Manifest portage-2.1.1-r2.ebuild portage-2.2_rc8.ebuild
UnderTree =->

How do I get the correct ebuild?
Shouldn't "emerge portage" have downloaded it automaticaly?

[wolfden]

have you tried to sync?

emerge --sync

[joe3]

Yes, As I said in the original message, it was the sync that told me I needed to emerge portage...

But just for chucks and giggles I repeated the process today...

This time after the sync emerge portage wanted portage-2.2_rc11 instead of portage-2.2_rc10

And _THIS_ time it worked... Thanks

--
joe3

[wolfden]

I know what you said in the first post that is why I asked to emerge --sync

sometimes when you sync, it can fail for whatever reason and than if you emerge --sync again it will correct it.

Glad it's working

[joe3]

Me too.

But now I can't get gnucash to open a file without crashing... and re-emerging fails. There seams to be a problem with the mask or some such thing...

It is after all a gnome program I've been running in kde...

But since THIS sabayon is loop 2 I suspect I'm better off migrating to my new sabayon 3.5 stable install (Now that I've got x working again after equo world updated the ati driver to one that no longer supports an old rage 128 {different thread).) Then if I quickly equo or emerge everthing i want working before the portage tree changes too much I should be able to gett it all running there... If not I'll ask some more dumb questions.

Thanks for the advise.

--
joe3