Emerging samba4 fails - Githubissues

olegstepura commented 13 years ago

Hi!

I'm trying to emerge it on a clean PC and get this error:

* Call stack:
*     ebuild.sh, line   91:  Called pkg_postrm
*   environment, line 3106:  Called python_mod_cleanup 'samba'
*   environment, line 4605:  Called _python_check_python_pkg_setup_execution
*   environment, line  579:  Called die
* The specific snippet of code:
*           die "python_pkg_setup() not called";
*
* If you need support, post the output of 'emerge --info =net-fs/samba-4.0.0_alpha17-r2',
* the complete build log and the output of 'emerge -pqv =net-fs/samba-4.0.0_alpha17-r2'.
* This ebuild is from a repository named 'samba4'
* The complete build log is located at '/tmp/portage/._unmerge_/net-fs/samba-4.0.0_alpha17-r2/temp/build.log'.
* The ebuild environment file is located at '/tmp/portage/._unmerge_/net-fs/samba-4.0.0_alpha17-r2/temp/environment'.
* S: '/tmp/portage/._unmerge_/net-fs/samba-4.0.0_alpha17-r2/work/samba-4.0.0_alpha17'

I did a reattempt to reinstall the whole system, rebuilding the world and running revdep-rebuild and python-updater but the problem persists and is the same.

Actually it even is installed and seem to be working, also appearing in the list of installed software but the error prevents me from being able to rebuild the world for example. Also I cannot tell everything is totally ok .

I used this guide for installing: http://en.gentoo-wiki.com/wiki/Samba4_as_Active_Directory_Server (using heidmal instead of mit-krb)

Here are the complete logs and everything that portage asks to provide: https://gist.github.com/1316180

Is there anything I'm doing wrong?

Thanks!

olegstepura commented 13 years ago

server # emerge -V Portage 2.1.10.31 (default/linux/amd64/10.0, gcc-4.5.3, glibc-2.13-r4, 3.0.7-gentoo x86_64)

ekohl commented 13 years ago

What actually goes wrong here is that I failed to call python_pkg_setup so postrm refuses to work. I've pushed a newer version, but since it fails on removal I'm unsure if it actually uses the new one. If it doesn't work, try:

cp /var/lib/layman/samba4/net-fs/samba/samba-4.0.0_alpha17-r2.ebuild /var/db/pkg/net-fs/samba-4.0.0_alpha17-r2/samba-4.0.0_alpha17-r2.ebuild

That should solve your issue.

olegstepura commented 13 years ago

Neither layman -f && emerge -v samba not cp-ing as you mentioned helped. =( So I am still experiencing the same issue.

ekohl commented 13 years ago

layman -f should be layman -S.

olegstepura commented 13 years ago

Ooops. Started again

olegstepura commented 13 years ago

Fantastic! rm /var/db/pkg/net-fs/samba-4.0.0_alpha17-r2/samba-4.0.0_alpha17-r2.ebuild layman -S emerge -v samba

Worked like a sharm. Thank you!

ekohl commented 13 years ago

You're welcome

olegstepura commented 13 years ago

I am not sure, but this could be related to the problem I had before (since both are python-related)

Running provision produces the error:

Traceback (most recent call last):
  File "/usr/sbin/provision", line 33, in <module>
    import samba
  File "/usr/lib64/python2.7/site-packages/samba/__init__.py", line 50, in <module>
    from samba._ldb import Ldb as _Ldb
ImportError: liberrors.so: cannot open shared object file: No such file or directory

Can you please help?

ekohl commented 13 years ago

I can reproduce the error and it feels like a bug to me. I'll look into it.

olegstepura commented 13 years ago

Thanks! This issue should be reopened than I suppose ;)

olegstepura commented 13 years ago

Cool! Will be waiting for it to be fixed.

ekohl / samba4

Emerging samba4 fails #4