[Bug 2095011] Re: [BPO] sphinxcontrib-globalsubs/0.1.2-2 from plucky

2025-01-15 Thread Luca Boccassi
In my experience SRUs tend to get stonewalled and end up going nowhere, backports are much easier and actually end up happening. It's entirely fine for our use case for this to be in backports, so I'm ok with this. -- You received this bug notification because you are a member of Ubuntu Backporte

[Bug 2095011] Re: [BPO] sphinxcontrib-globalsubs/0.1.2-2 from plucky

2025-01-15 Thread Sebastien Bacher
Reviewing the request, any reason to go for a backport rather than a SRU? The rational makes sense and it seems a SRU would be more appropriate there since it would make it easier for developers to get the package (new packages are fine to SRU according to https://canonical-sru-docs.readthedocs- ho

[Bug 2095011] [NEW] [BPO] sphinxcontrib-globalsubs/0.1.2-2 from plucky

2025-01-15 Thread Launchpad Bug Tracker
You have been subscribed to a public bug by Luca Boccassi (bluca): [Impact] This is a new package providing a sphinx extension available in Plucky. It will be necessary to build the manpages for systemd in the near future after this upstream PR is merged: https://github.com/systemd/systemd/pull/3