On Wed, Jul 3, 2024 at 5:25 PM John Snow wrote:
> To be clear I mean offline, isolated RPM builds under RHEL9 where I don't
> think we can utilize PyPI at all; and vendoring Sphinx is I think not a
> practical option due to the number of dependencies and non-pure Python deps.
>
> It's not a prob
On Wed, Jul 3, 2024 at 8:12 AM Paolo Bonzini wrote:
> On Wed, Jul 3, 2024 at 2:06 PM John Snow wrote:
> > On Wed, Jul 3, 2024, 4:00 AM Paolo Bonzini wrote:
> >> On 7/2/24 21:59, John Snow wrote:
> >> > With RHEL 8 support retired (It's been two years today since RHEL 9
> >> > came out), our ver
On Wed, Jul 3, 2024 at 2:06 PM John Snow wrote:
> On Wed, Jul 3, 2024, 4:00 AM Paolo Bonzini wrote:
>> On 7/2/24 21:59, John Snow wrote:
>> > With RHEL 8 support retired (It's been two years today since RHEL 9
>> > came out), our very oldest build platform version of Sphinx is now
>> > 3.4.3; and
On Wed, Jul 3, 2024, 4:00 AM Paolo Bonzini wrote:
> On 7/2/24 21:59, John Snow wrote:
> > With RHEL 8 support retired (It's been two years today since RHEL 9
> > came out), our very oldest build platform version of Sphinx is now
> > 3.4.3; and keeping backwards compatibility for versions as old a
On 7/2/24 21:59, John Snow wrote:
With RHEL 8 support retired (It's been two years today since RHEL 9
came out), our very oldest build platform version of Sphinx is now
3.4.3; and keeping backwards compatibility for versions as old as v1.6
when using domain extensions is a lot of work we don't ne
With RHEL 8 support retired (It's been two years today since RHEL 9
came out), our very oldest build platform version of Sphinx is now
3.4.3; and keeping backwards compatibility for versions as old as v1.6
when using domain extensions is a lot of work we don't need to do.
This patch is motivated b
