[SOLVED] ebuild failing to handle redirects

[pingtoo]

First apologize if this post appear in wrong place. This is my first time try to post.

Back to the subject, I notice you tried two different methods for the process.
First you run "ebuild sc-im-0.8.2.ebuild manifest", this lead to a problem, "No write access to /var/cache/distfiles". So it appear the userID used for the command does not have write permission to /var/cache/distfiles directory.
Second time you ran "sudo ebuild sc-im-0.8.2.ebuild manifest". This time the error is about no permission to crate the manifest file as "root" (because you use sudo) in /home/ari/coding/resources_/dinolay/app-office/sc-im/ directory

So it may appear to be permission problem but it is two different permission, first one is your own userID not able to write to a directory (/var/cache/distfiles) usually own by UID/GID "portage/portage". This can be fix by place your ID in to "portage" group. Second one you use "sudo", however "root" does not have permission to write in to your project dir(/home/ari/Ari/coding/resources_/dinolay/app-office/sc-im), this can be fix by chmod 777 to /home/ari/Ari/coding/resources_/dinolay/app-office/sc-im.

So bottom line, you used two different methods to perform same process, however due to effect UID, you have two different problems, Although both problems have same permission errors, those are two different problems.

[Tony0945]

Sorry. Got old eyes, they miss details.
Here is another guess.
1. Install pkgcheck if you haven't already.
2. Go to the directory where the ebuild is.
3. Run "pkgcheck scan"

If you don't see any obvious errors post the results.
Some of the errors may be nitpicking, some may be problems. pkgcheck is used by the dev's on the official tree. It is like "repoman scan" but even more picky.
IIRC, it is color coded. red errors are bad. orange are warnings. maybe bad. Maybe not.

EDIT:
Even if this shows nothing, pkgcheck is a handy tool to have.

[cboldt]

The problem isn't the ebuild, per se. The ebuild works.

The problem is a some factor of location of the ebuild and permission train for portage to get there, and permisisons or similar for the distfiles directory.

I put the ebuild starting from the /var/db/repos/local space, ownership root.root, chmod 755

The /etc/portage/repos.conf/repos.conf file has a suitable entry for this repository.

distfilles are saved in /var/cache/distfiles, directory owned by root.portage, chmod 775

I've never tried to set up a repository starting from my user home directory, so I'm no help on that front, other than portage needs to be able to write to the directory where the ebuild is (to write the Manifest).

[Hu]

[Tony0945]

[Hu]

[Ari_archer]

[Ari_archer]

It's finally solved! all it took is for me to add myself to the portage group....

Sorry for this much hassle. but now it works flawlessly.

I will make this post as [SOLVED] now, thank you
_________________
regards,
ari

[pjp]