dogtagpki

#3197 pki server and x86 machines
Closed: invalid by slev. Opened by slev.

Closed: invalid
Reopen Issue

DogtagPKI is heavily tied to 389-ds since it is the only supported LDAP backend.

389-ds dropped support for x86 architecture 2 years ago:
https://fedoraproject.org/wiki/Changes/389-ds-base-remove-686

There is no possibility to spawn 389-ds instance on such platforms, thus, it's impossible
to do pkispawn too.

My proposals:
1) split all binary packages into server and client ones, then build for x86 only client packages, otherwise, server+client ones;
2) stop build for x86 at all

389-DS and Dogtag can be installed on separate servers. There is no need to install Dogtag on the same machine.

Metadata Update from @cheimes:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None

Indeed, I was inattentive while reading docs. Thank you.

Metadata Update from @slev:
- Issue close_status updated to: invalid
- Issue status updated to: Closed (was: Open)

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/3314

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, and we apologize for any inconvenience.
Metadata
None
None
None
None
None
None
None
None
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.