[gentoo-user] /usr/local/portage does not seem to have a valid PORTDIR structure.

[gentoo-user] /usr/local/portage does not seem to have a valid PORTDIR structure.

[Norberto Bensa]

Hello list,

I'm trying to make an ebuild for kbfx 
(http://kde-apps.org/content/show.php?content=24898) but when I do:

sudo ebuild ./kbfx-0.4.8beta.ebuild digest

I get:

Appending /usr/local/portage to PORTDIR_OVERLAY...
!!! /usr/local/portage does not seem to have a valid PORTDIR structure.

This seems new in portage-2.0.53rc7. What is it and how do I fix this?


Many thanks in advance,
-- 
Norberto Bensa
4544-9692
Ciudad de Buenos Aires, Argentina
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] /usr/local/portage does not seem to have a valid PORTDIR structure.

[Holly Bostick]

Norberto Bensa schreef:
> Hello list,
> 
> I'm trying to make an ebuild for kbfx 
> (http://kde-apps.org/content/show.php?content=24898) but when I do:
> 
> sudo ebuild ./kbfx-0.4.8beta.ebuild digest
> 
> I get:
> 
> Appending /usr/local/portage to PORTDIR_OVERLAY... !!!
> /usr/local/portage does not seem to have a valid PORTDIR structure.
> 
> This seems new in portage-2.0.53rc7. What is it and how do I fix
> this?
> 
> 
> Many thanks in advance,

I'm not sure if this is the answer, since I've not seen that error, but
I have had many errors based on the fact that my overlay ebuild was not
placed in the same tree structure as Portage -- and it does rather sound
like that's what this error is saying.

For example, let's say you make an alternative ebuild for... (make
something up)... mplayer.

The overlay ebuild would have to be placed in (assuming your overlay is
/usr/local/portage)

/usr/local/portage/media-video/mplayer/mplayer-whatever.ebuild

If you placed it in
/usr/local/portage/media-video/mplayer-whatever.ebuild, or
/usr/local/portage/mplayer/mplayer-whatever.ebuild you would get an
error, because the Portage tree structure is

/portage/directory/category/packagename/package-ver.sion.ebuild

Any other format will not be recognized, and you will get one of a
variety of errors.

So I would first suggest that you make sure your ebuild is correctly
placed in the correct tree structure, and then I would digest it by full
path, rather than from within the directory, as you seem to be doing.

Afaik, the syntax of the ebuild command requires the full path, even if
you're at the correct location.

Hope this helps,
Holly
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] /usr/local/portage does not seem to have a valid PORTDIR structure.

[Rumen Yotov]

[-- Attachment #1: Type: text/plain, Size: 1092 bytes --]

On Sun, 2005-11-06 at 13:10 -0300, Norberto Bensa wrote:
> Hello list,
> 
> I'm trying to make an ebuild for kbfx 
> (http://kde-apps.org/content/show.php?content=24898) but when I do:
> 
> sudo ebuild ./kbfx-0.4.8beta.ebuild digest
> 
> I get:
> 
> Appending /usr/local/portage to PORTDIR_OVERLAY...
> !!! /usr/local/portage does not seem to have a valid PORTDIR structure.
> 
> This seems new in portage-2.0.53rc7. What is it and how do I fix this?
> 
> 
> Many thanks in advance,
> -- 
> Norberto Bensa
> 4544-9692
> Ciudad de Buenos Aires, Argentina
Hi,
Digest files (for ebuilds) stay in portage - the main one or in the
overlay. Assume you want to make a digest in some HOME dir, won't work.
Try this instead:
"$sudo ebuild /usr/local/portage/kde-apps/kbfx-0.4.8beta.ebuild digest"
substituting 'kde-apps' with appropriate category. Before that put the
ebuild there.
Portage structure in /usr/local/portage mirrors the main tree.
Unless you run the above from within portage-overlay.
PS: check if PORTAGE_OVERLAY= var is set in /etc/make.conf.
HTH.Rumen

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] /usr/local/portage does not seem to have a valid PORTDIR structure.

[Norberto Bensa]

Holly Bostick wrote:
> Norberto Bensa schreef:
> > sudo ebuild ./kbfx-0.4.8beta.ebuild digest
> >
> > I get:
> >
> > Appending /usr/local/portage to PORTDIR_OVERLAY... !!!
> > /usr/local/portage does not seem to have a valid PORTDIR structure.
>
> So I would first suggest that you make sure your ebuild is correctly
> placed in the correct tree structure, and then I would digest it by full
> path, rather than from within the directory, as you seem to be doing.
>

nbensa@zeddmore /usr/local/portage/kde-misc/kbfx $ sudo ebuild /usr/local/portage/kde-misc/kbfx/kbfx-0.4.8beta.ebuild digest
Password:
Appending /usr/local/portage to PORTDIR_OVERLAY...
!!! /usr/local/portage does not seem to have a valid PORTDIR structure.


$ grep OVERLAY /etc/make.conf
PORTDIR_OVERLAY=/usr/local/portage


I don't know. Perhaps one of those (stupid) security settings somewhere for latest portage :(

Thank you Holly and Rumen.

Best regards,
Norberto
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] /usr/local/portage does not seem to have a valid PORTDIR structure.

[Holly Bostick]

Norberto Bensa schreef:
> Holly Bostick wrote:
> 
>> Norberto Bensa schreef:
>> 
>>> sudo ebuild ./kbfx-0.4.8beta.ebuild digest
>>> 
>>> I get:
>>> 
>>> Appending /usr/local/portage to PORTDIR_OVERLAY... !!! 
>>> /usr/local/portage does not seem to have a valid PORTDIR 
>>> structure.
>> 
>> So I would first suggest that you make sure your ebuild is 
>> correctly placed in the correct tree structure, and then I would 
>> digest it by full path, rather than from within the directory, as 
>> you seem to be doing.
>> 
> 
> 
> nbensa@zeddmore /usr/local/portage/kde-misc/kbfx $ sudo ebuild 
> /usr/local/portage/kde-misc/kbfx/kbfx-0.4.8beta.ebuild digest 
> Password: Appending /usr/local/portage to PORTDIR_OVERLAY... !!! 
> /usr/local/portage does not seem to have a valid PORTDIR structure.
> 
> 
> $ grep OVERLAY /etc/make.conf PORTDIR_OVERLAY=/usr/local/portage
> 
> 
> I don't know. Perhaps one of those (stupid) security settings 
> somewhere for latest portage :(
> 
> Thank you Holly and Rumen.
> 

Now, now; not so hasty.... what I notice is that this is a *very*
explicit error message. So if we assume that it means exactly what it
says, where does that get us?

/usr/local/portage does not seem to have a valid PORTDIR structure

very clearly says that the overlay must have a structure identical to
PORTDIR; your portdir *is* /usr/portage, is it not?

Assuming that it is, then you have replicated this structure in
/usr/local/portage for this ebuild-- but there are three possible holes
in this 'theory' such as it is.

One is that you are trying to digest the ebuild from within the
directory, rather than from, say, /usr/local. It is remotely possible
that this is not a good idea, since the overlay tree should possibly not
be the current working directory (as I suggested before).

Second is that you're using sudo. I find many anomolies in sudo; mostly
revolving around it not being a 'real' login shell, but some kind of
weird spawned shell process that doesn't necessarily transfer all
variables and/or permissions, depending on settings. You might try
again, using su - -c instead of sudo to get root privileges.

Third is that there's a problem with your ebuild, which also uses the
PORTDIR variable. It is possilbe that your ebuild is incorrectly using
this variable and not using a 'valid' PORTDIR. I'm not much of an ebuild
writer, but you might want to go over it with a fine-toothed comb to
make sure that this error isn't reporting an anomaly in the ebuild it's
trying to read, rather than Portage, and is just poorly expressing that
(it happens).


HTH,
Holly
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] /usr/local/portage does not seem to have a valid PORTDIR structure.

[Norberto Bensa]

Holly Bostick wrote:
> Norberto Bensa schreef:
> > nbensa@zeddmore /usr/local/portage/kde-misc/kbfx $ sudo ebuild
> > /usr/local/portage/kde-misc/kbfx/kbfx-0.4.8beta.ebuild digest
> > Password: Appending /usr/local/portage to PORTDIR_OVERLAY... !!!
> > /usr/local/portage does not seem to have a valid PORTDIR structure.
>
> very clearly says that the overlay must have a structure identical to
> PORTDIR; your portdir *is* /usr/portage, is it not?

Yup.


> you're using sudo. I find many anomolies in sudo; 

Why does people hate sudo so much?

$ su -
password:
# ebuild /usr/local/portage/kde-misc/kbfx/kbfx-0.4.8beta.ebuild digest
Appending /usr/local/portage to PORTDIR_OVERLAY...
!!! /usr/local/portage does not seem to have a valid PORTDIR structure.

:(


> there's a problem with your ebuild, which also uses the
> PORTDIR variable. 

I've found the problem. Portage doesn't like packge-0.0.1beta. Instead you 
must name it like package-0.0.1_beta. Now I need to do some magic inside the 
ebuild to s/_// 

>
> HTH,
> Holly

Many thanks!

-- 
Norberto Bensa
4544-9692
Ciudad de Buenos Aires, Argentina
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] /usr/local/portage does not seem to have a valid PORTDIR structure.

[Holly Bostick]

Norberto Bensa schreef:
> Holly Bostick wrote:
> 
>> you're using sudo. I find many anomolies in sudo;
> 
> 
> Why does people hate sudo so much?
> 
Actually, I don't hate sudo at all; I use it all the time, and it saves
a lot of difficulty. I just get annoyed because I, in my ignorance,
generally expect it to act like a "super su", and it doesn't-- in fact,
it's something else by design, but I don't know enough about the
underlying design and the reasons for it, to not fall into the mistaken
assumption if I attempt to use sudo "on the fly", as it were.

Which ultimately means that I have to either set sudo up very carefully,
or pay very close attention when using it on the fly, or use an
alternative, and two out of three of those choices obviate my reason for
using sudo, which is to be able to perform certain root functions
*quickly*, without breaking stride in the overall operation I'm performing.

For example, I get the mail saying what updated packages I have
available, I run a --pretend emerge, am not happy with the USE flags,
and so want to change them, meaning I have to edit root-only files. I
can run nano using either su or sudo, but either way I have to input a
password (under normal circumstances), and the passwords aren't the
same, meaning I have to think about something else (am I running su or
sudo, and which one uses which password), which is a distraction from
the job at hand.

So unless I set sudo (and in fact ~/.bashrc) up to not interrupt the
flow of my main activity (which I have taken some pains to do), sudo is
no better than su -- and the fact that sudo does not do some things that
su - does (unless explicitly set up to do them), just makes the
situation worse.

But I assume that this is most likely because I'm using sudo for
purposes that it can handle, but are not strictly within its design
parameters.... naturally the fit is not perfect. I'm sure that if I was
a server admin, using sudo to manage root access privileges in defined
areas for defined groups, it would be a much smoother ride.

The fact that a coin can unscrew a screw, but is not the best or most
comfortable tool to do so, is no reflection on the coin, nor the screw.
In fact, I'm just glad that the coin can do double-duty. What a waste of
time and energy it would be to hate such a tool, for taking advantage of
a bit of luck in both designs.

> 
>> there's a problem with your ebuild, which also uses the PORTDIR 
>> variable.
> 
> 
> I've found the problem. Portage doesn't like packge-0.0.1beta. 
> Instead you must name it like package-0.0.1_beta. Now I need to do 
> some magic inside the ebuild to s/_//
> 
> Many thanks!

Well, I'm sure you can handle that bit of ebuild magic. Glad to have
been of help in finding the problem.

Holly




-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] /usr/local/portage does not seem to have a valid PORTDIR structure.

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 433 bytes --]

On Sun, 6 Nov 2005 15:01:27 -0300, Norberto Bensa wrote:

> I've found the problem. Portage doesn't like packge-0.0.1beta. Instead
> you must name it like package-0.0.1_beta. Now I need to do some magic
> inside the ebuild to s/_// 

Something along the lines of
 
My_P=$(P/beta/_beta}

and use ${My_P} instead of ${P} throughout the ebuild.


-- 
Neil Bothwick

FINE: Tax for doing wrong. Tax: fine for doing fine.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] /usr/local/portage does not seem to have a valid PORTDIR structure.

[Nagatoro]

Neil Bothwick wrote:
> On Sun, 6 Nov 2005 15:01:27 -0300, Norberto Bensa wrote:
> 
> 
>>I've found the problem. Portage doesn't like packge-0.0.1beta. Instead
>>you must name it like package-0.0.1_beta. Now I need to do some magic
>>inside the ebuild to s/_// 
> 
> 
> Something along the lines of
>  
> My_P=$(P/beta/_beta}
> 
> and use ${My_P} instead of ${P} throughout the ebuild.
> 
> 

Or better look at
http://dev.gentoo.org/~plasmaroo/devmanual/ebuild-writing/

since _beta is a recogniced suffix there should be built in methods to 
deal with it.

-- 
Naga
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] /usr/local/portage does not seem to have a valid PORTDIR structure.

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 546 bytes --]

On Mon, 07 Nov 2005 11:24:19 +0100, Nagatoro wrote:

> > Something along the lines of
> >  
> > My_P=$(P/beta/_beta}
> > 
> > and use ${My_P} instead of ${P} throughout the ebuild.
> > 
> > 
> 
> Or better look at
> http://dev.gentoo.org/~plasmaroo/devmanual/ebuild-writing/
> 
> since _beta is a recogniced suffix there should be built in methods to 
> deal with it.

_beta is a recognised suffix, beta is not. Actually, the above line
should be

MyP=${P/_beta/beta}


-- 
Neil Bothwick

Virtue is it's own punishment.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] /usr/local/portage does not seem to have a valid PORTDIR structure.

[Norberto Bensa]

Neil Bothwick wrote:
>
> MyP=${P/_beta/beta}

Actually, I did it like this:

MY_P=${P/_/}


Thank everyone!

Norberto
-- 
gentoo-user@gentoo.org mailing list