#47709 package issue in 389-ds-base
Closed: wontfix Opened by nhosoi.

Description of problem:
There are file conflicts on multilib installation.

There are multiple problems with the package:
1) bad packaging - *.py[co] files in /usr/share while package is not noarch
2) 389-ds-base got multilib due to versioned libs in the RPM:
/usr/lib/dirsrv/libns-dshttpd.so
/usr/lib/dirsrv/libns-dshttpd.so.0
/usr/lib/dirsrv/libns-dshttpd.so.0.0.0
consider moving them to 389-ds-base-libs, that should prevent the package from being multilib.


Description: Following the package guideline, moving pytyon binaries
to the architecture aware location and libns-dshttpd.so* from 389-ds-base
to 389-ds-base-devel and 389-ds-base-libs.

You have added pythonexec to the configure.ac and Makefile.am, but it is not used anywhere?

I don't think libns-dshttpd.so needs to be in the devel package.

git patch file (master; take 2) -- 389-ds-base.spec; moved libns-dshttpd.so* to libs
0001-Added-arch-aware-python-dir-moved-libns-dshttpd.so-t.patch

{{{
-e 's,@pythonpath\@,$(pythondir),g' \
}}}

Is @pythonpath@ used anywhere?

git patch file (master; take 3) -- Makefile.am, configure.ac; removed unused pythonexec
0001-Ticket-47709-package-issue-in-389-ds-base.patch

git patch file (master; take 3) -- Makefile.in, configure
0002-Ticket-47709-package-issue-in-389-ds-base.patch

Reviewed by Rich (Thank you!!)

Pushed to master:
16386dd..b7e9f9f master -> master
commit b7e9f9f3c35e7b3e964378a5606594942cf44b5f
commit a32b2a9ddc5764d449b051c20077643585e81def

Pushed to 389-ds-base-1.3.2:
e9dd44b..3700e92 389-ds-base-1.3.2 -> 389-ds-base-1.3.2
commit 3700e92464d4673d8477a39d2667282c8b3c89bf
commit 011385ad8cb8afc42611b57a3a88600eb1d56932

Pushed to 389-ds-base-1.3.1:
8772ea1..99d5d3e 389-ds-base-1.3.1 -> 389-ds-base-1.3.1
commit 99d5d3e59827c132ba2666c67f9e22bd62aaacab
commit f1bbfe2ff0768128b10903ca1262302313b74ad6


spec file:
master:
9775d04..66d6780 master -> master
commit 66d67802e39f57f6bc14b8468dd91723cfdc1f30

f20:
da63032..7339b45 f20 -> f20
commit 66d67802e39f57f6bc14b8468dd91723cfdc1f30

f19:
5885254..96ed904 f19 -> f19
commit 96ed904ed99fe4ac7c7da1f269ac101fd08c4265

git patch file (master) -- fixing rpm/389-ds-base.spec.in
0001-Ticket-47709-package-issue-in-389-ds-base.2.patch

git patch file (master) -- fixing rpm/389-ds-base.spec.in

Pushed to master:
b7e9f9f..f7c5dc2 master -> master
commit f7c5dc2b9b7fb9bc0b836322565218b53953bb7b

Pushed to 389-ds-base-1.3.2:
3700e92..c3cc56b 389-ds-base-1.3.2 -> 389-ds-base-1.3.2
commit c3cc56b75830b419b882610f1b1a743922a74458

Pushed to 389-ds-base-1.3.1:
99d5d3e..d6a57ad 389-ds-base-1.3.1 -> 389-ds-base-1.3.1
commit d6a57ad5d520227b1c7b464f76f021a2fbdae55d

Metadata Update from @rmeggins:
- Issue assigned to nhosoi
- Issue set to the milestone: 1.3.1.18

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 issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/1044

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

Metadata