#1978 translated man pages are not picked up when building in parallel build
Closed: wontfix 2 years ago by pbrezina. Opened 9 years ago by jhrozek.

Me and Stephen noticed this bug when working on ticket #1510. It seems that the translated man pages are only correctly generated when building in the same directory where the sources are present. Parallel builds don't work correctly.

Minor priority -- as far as I know the bug has always been there and there is an easy workaround. Moreover, normally only the upstream performs releases where the translations are prepared, so this is not affecting users in general.

milestone: NEEDS_TRIAGE => SSSD 1.12
priority: major => minor

internal build system issue. No clone.

rhbz: => 0

Fields changed

mark: => 0
milestone: SSSD 1.13 => SSSD 1.14 beta

This ticket was opened 3 years ago and so far the maintainers were able to cope up with this defect..patches welcome.

milestone: SSSD 1.14 beta => SSSD Deferred
sensitive: => 0

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD Patches welcome

5 years ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

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

2 years ago

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

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/3020

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.

Login to comment on this ticket.