#50085 Issue 50037 - lib389 fails to install in venv under non-root user
Closed 3 years ago by spichugi. Opened 5 years ago by vashirov.
vashirov/389-ds-base 50037  into  master

file modified
+5
@@ -225,3 +225,8 @@ 

  src/lib389/dist/

  src/lib389/man/

  src/libsds/target/

+ dist

+ venv

+ .idea

+ src/cockpit/389-console/cockpit_dist/

+ src/cockpit/389-console/node_modules/

file modified
+3 -3
@@ -46,9 +46,9 @@ 

          'Intended Audience :: Developers',

          'Operating System :: POSIX :: Linux',

          'Programming Language :: Python :: 3',

-         'Programming Language :: Python :: 3.4',

          'Programming Language :: Python :: 3.5',

          'Programming Language :: Python :: 3.6',

+         'Programming Language :: Python :: 3.7',

          'Topic :: Software Development :: Libraries',

          'Topic :: Software Development :: Quality Assurance',

          'Topic :: Software Development :: Testing'],
@@ -58,14 +58,14 @@ 

  

      # find lib389/clitools -name ds\* -exec echo \''{}'\', \;

      data_files=[

-         ('/usr/sbin/', [

+         ('sbin/', [

              'cli/dsctl',

              'cli/dsconf',

              'cli/dscreate',

              'cli/dsidm',

              'cli/dscontainer',

              ]),

-         ('/usr/share/man/man8', [

+         ('share/man/man8', [

              'man/dsctl.8',

              'man/dsconf.8',

              'man/dscreate.8',

file modified
+1 -1
@@ -1,5 +1,5 @@ 

  [tox]

- envlist = py27, py34, py35, py36

+ envlist = py35, py36, py37

  

  [testenv]

  deps = -rrequirements.txt

Bug description:
Some files were installed using absolute path, preventing installation
under non-root user.

Fix description:
Change paths to be relative to the current prefix.
Update .gitignore to exlcude venv.
Update tox.ini to the current supported Python versions.

https://pagure.io/389-ds-base/issue/50037

Reviewed by: ???

If that would be beneficial for venv installation, could we simply install using scripts and move the files into /usr/sbin after running setup.py (probably both in Makefile.am and the SPEC file).

Anyway, building from SPEC file does not work for me as manpages are now installed into /usr/man/man8 instead of /usr/share/man/man8 (%{_mandir} macro in SPEC file expands to /usr/share/man).

I mean, we should probably respect the way of setup.py and post-adjust as required.

rebased onto 964eacfa112acb5647d762c76647d078904a2888

5 years ago

I've adjusted setup.py to fix rpm build.

This looks good to me, but I have not run rpm build.

Is it still relevant? Could you please rebase so we can test it and probably merge?

rebased onto c4a2eb4

4 years ago

@spichugi, yes it's still relevant. I've updated the patch.

Pull-Request has been merged by vashirov

4 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This pull request has been cloned to Github as issue and is available here:
- https://github.com/389ds/389-ds-base/issues/3144

If you want to continue to work on the PR, please navigate to the github issue,
download the patch from the attachments and file a new pull request.

Thank you for understanding. We apologize for all inconvenience.

Pull-Request has been closed by spichugi

3 years ago