#51110 Fix ASAN ODR errors
Closed: wontfix 3 years ago by mreynolds. Opened 3 years ago by mreynolds.

Issue Description

There are quite a few ODR (one define rule) warnings comign from an ASAN build which prevents the server from starting


Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

3 years ago

Commit 251cef9 relates to this ticket

Commit 251cef9 relates to this ticket

6102669..0478929 389-ds-base-1.4.3 -> 389-ds-base-1.4.3

a267875..09832ae 389-ds-base-1.4.2 -> 389-ds-base-1.4.2

8c8b1aa..963cdf8 389-ds-base-1.4.1 -> 389-ds-base-1.4.1

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

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

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)

3 years ago

Login to comment on this ticket.

Metadata
Related Pull Requests