cat /etc/redhat-release Fedora release 24 (Twenty Four) rpm -qa | grep freeipa freeipa-common-4.3.2-4.fc24.noarch freeipa-admintools-4.3.2-4.fc24.noarch freeipa-debuginfo-4.4.90.201610260421GIT91920e7-0.fc24.x86_64 freeipa-python-compat-4.3.2-4.fc24.noarch freeipa-client-common-4.3.2-4.fc24.noarch freeipa-client-4.3.2-4.fc24.x86_64 freeipa-server-4.3.2-4.fc24.x86_64 freeipa-server-common-4.3.2-4.fc24.noarch ipa-server-install Traceback (most recent call last): File "/usr/local/sbin/ipa-server-install", line 23, in from ipaserver.install import ipa_server_install ImportError: cannot import name ipa_server_install
cat /etc/redhat-release Fedora release 24 (Twenty Four) rpm -qa | grep freeipa freeipa-common-4.3.2-4.fc24.noarch freeipa-admintools-4.3.2-4.fc24.noarch freeipa-debuginfo-4.4.90.201610260421GIT91920e7-0.fc24.x86_64 freeipa-python-compat-4.3.2-4.fc24.noarch freeipa-client-common-4.3.2-4.fc24.noarch freeipa-client-4.3.2-4.fc24.x86_64 freeipa-server-4.3.2-4.fc24.x86_64 freeipa-server-common-4.3.2-4.fc24.noarch
ipa-server-install Traceback (most recent call last): File "/usr/local/sbin/ipa-server-install", line 23, in from ipaserver.install import ipa_server_install ImportError: cannot import name ipa_server_install
After building ipa from source.
ipa-server-install picks the ipa-server-install script from /usr/local/sbin/
But when ipa server installed from repo, nothing is present in /usr/local/sbin. Hence it picks ipa-server-install script from /usr/sbin.
Bug is: Both of these methods produces different scripts(ipa-server-install): 1. Building ipa from source present in /usr/local/sbin/ 2. Installing ipa from repo, script present in /usr/sbin/ Opened a separate ticket for this [https://pagure.io/freeipa/issue/6728]
workaround: # cp /usr/sbin/ipa-server-install /usr/local/sbin/ipa-server-install
If you would build 'make rpms', you'd get the same packages as with repo.
It is expected that spec file contains commands that define install paths to be consistent with the system you are building for. When you are building yourself, without using a package management tool, you are responsible to define correct options to configure to set proper paths.
For Linux systems a general set of paths is defined by FHS: http://www.pathname.com/fhs/pub/fhs-2.3.html, but each distribution has own rules that are applied on top of FHS. Autoconf also defaults to a subset of paths from FHS, namely to 'local hierarchy' name space. This is because unless you are making a packaged software build, your installation should not overlap with the packaged software for your operating system.
In other words, I do not see any bug here and I think your ticket is invalid. Let me know if you think otherwise after reading FHS.
It is not clear what branch you are building. I retested shippen packages in F24 and it works for me.
If you are building master branch then please use F25 with dependencies from @freeipa/freeipa-master CORP repository.
If you are trying to build ipa-4-3 branch on F24, then use command make rpms for building and then install the rpms. ipa-4-3 branch doesn't support make install
make rpms
make install
Anyway, closing as invalid.
Metadata Update from @pvoborni: - Issue close_status updated to: invalid - Issue status updated to: Closed (was: Open)