| 1 |
Today I had quite a bit of issues while creating a local overlay to |
| 2 |
modify samba. Got through all of them, but there were the following |
| 3 |
issues which I wanted to bring up, because I am not sure whether I have |
| 4 |
done anything wrong: |
| 5 |
|
| 6 |
- I had created the overlay under "/root/overlay", but this is causing |
| 7 |
"permission denied" errors from ebuild when creating the Manifest file: |
| 8 |
|
| 9 |
====================================================================== |
| 10 |
/usr/lib64/portage/bin/ebuild.sh: line 545: |
| 11 |
/root/overlay/net-fs/samba/samba-3.6.18.ebuild: Permission denied |
| 12 |
* ERROR: net-fs/samba-3.6.18::myoverlay failed (depend phase): |
| 13 |
* error sourcing ebuild |
| 14 |
* |
| 15 |
* Call stack: |
| 16 |
* ebuild.sh, line 545: Called die |
| 17 |
* The specific snippet of code: |
| 18 |
* source "$EBUILD" || die "error sourcing ebuild" |
| 19 |
* |
| 20 |
* If you need support, post the output of `emerge --info |
| 21 |
'=net-fs/samba-3.6.18::myoverlay'`, |
| 22 |
* the complete build log and the output of `emerge -pqv |
| 23 |
'=net-fs/samba-3.6.18::myoverlay'`. |
| 24 |
* Working directory: '/usr/lib64/portage/pym' |
| 25 |
* S: '/var/tmp/portage/net-fs/samba-3.6.18/work/samba-3.6.18' |
| 26 |
====================================================================== |
| 27 |
|
| 28 |
After trying many different things without luck, I tried using |
| 29 |
/usr/local/portage as the overlay folder and the problem went away! So |
| 30 |
my first question is, does ebuild have a special security feature which |
| 31 |
prevents it from processing overlays under /root ? |
| 32 |
|
| 33 |
- The second issue is eclass related. After I moved net-fs/samba under |
| 34 |
/usr/local/portage, I got the following error during Manifest creation: |
| 35 |
|
| 36 |
====================================================================== |
| 37 |
bonsai samba # ebuild samba-3.6.18.ebuild manifest |
| 38 |
* ERROR: net-fs/samba-3.6.18::myoverlay failed (depend phase): |
| 39 |
* pam.eclass could not be found by inherit() |
| 40 |
* |
| 41 |
* Call stack: |
| 42 |
* ebuild.sh, line 545: Called source |
| 43 |
'/usr/local/portage/net-fs/samba/samba-3.6.18.ebuild' |
| 44 |
* samba-3.6.18.ebuild, line 7: Called inherit 'pam' 'versionator' |
| 45 |
'multilib' 'eutils' 'systemd' |
| 46 |
* ebuild.sh, line 257: Called die |
| 47 |
* The specific snippet of code: |
| 48 |
* [[ -z ${location} ]] && die "${1}.eclass could not be |
| 49 |
found by inherit()" |
| 50 |
* |
| 51 |
* If you need support, post the output of `emerge --info |
| 52 |
'=net-fs/samba-3.6.18::myoverlay'`, |
| 53 |
* the complete build log and the output of `emerge -pqv |
| 54 |
'=net-fs/samba-3.6.18::myoverlay'`. |
| 55 |
* Working directory: '/usr/lib64/portage/pym' |
| 56 |
* S: '/var/tmp/portage/net-fs/samba-3.6.18/work/samba-3.6.18' |
| 57 |
====================================================================== |
| 58 |
|
| 59 |
To resolve this, I just copied /usr/portage/eclass to |
| 60 |
/usr/local/portage/eclass. Is this a proper solution? |
| 61 |
|
| 62 |
-- |
| 63 |
Timur Aydin |
Archives