Replies: 1 comment
-
|
Thanks, but using A |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Background
On Ubuntu the sphinx package is a part of the
maincomponent of the archive. By policy, packages inmainare officially supported by Canonical. Also by policy, for any package inmainits runtime dependencies must also be inmain. New open-source packages are initially added to theuniversecomponent and promoted tomainby the Ubuntu Main Inclusion Review (MIR) process, only if justified. The MIR process ensures that themaincomponent does not have redundant packages that provide similar functionality.For roman numeral support, Sphinx moved to using the roman-numerals project after the
romanpackage was removed fromdocutils.utils. Consequently, a new roman-numerals package has been introduced in Debian and Ubuntu.Problem
The new roman-numerals package is currently in the
universecomponent in Ubuntu. By policy, it needs to be promoted to themaincomponent (becausesphinxis inmain). However,mainalready has a very similar roman package for the roman project under PyPi. This makes it difficult to justify the promotion ofroman-numeralsto main!It is very much likely that roman-numerals was consciously chosen over roman. Would it be possible to move to using the latter in place of the former?
As an interim solution, I have proposed a patch to the sphinx package in Ubuntu. But Ubuntu prefers to maintain such patches only if there is no other resort.
Thank you for reading through!
Beta Was this translation helpful? Give feedback.
All reactions