Hi,
[ honouring Reply-To as set ]
I might have missed many nuances in the situation but from what I've
read, here's what I observe.
On Thu, Feb 23, 2023 at 11:23:26AM +0900, John Crawley wrote:
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901245
This is the "right" bug for your issue. I also note it's quite old, and
hasn't seen much attention.
I was unsure whether to post a new bug report or append to the existing
one, but did the latter [4].
That was the correct course of action.
The issue is fixed by an upstream git commit [5] easily applied by a patch
(confirmed), which would make the package fit for release. (Other maintainer
options could be to drop the claim to provide x-terminal-emulator or drop the
package itself.)
I notice that the package source is maintained in git here
<https://salsa.debian.org/python-team/packages/terminator>
Debian Python Team maintain a huge number of packages (>2,000). Things
can very easily slip through the cracks.
If you want to make it as easy as possible for someone with sufficient
privileges to upload a fix, you could fork/clone that repository, make
the necessary changes to the packaging source to include the patch (put
it in debian/patches, make any other necessary changes), and raise a
"Merge Request" on Salsa, pointing back at the Debian bug. Then the work
required to integrate the fix is as small as possible.
My question: I'm in doubt whether the maintainer (Debian Python Team) will notice the
issue in time for the Bookworm release - would posting a new bug report be seen as
"nagging"?
I'm not sure about "nagging" but it would not be helpful, because a bug
describing the problem already exists. Your problem is getting anyone to
take notice of it. The solution is to raise awareness (this mail to the
user list, for example, is one way); another is to reduce the friction
for fixing it for those who have the ability to do so (outlined above).
Have you tried emailing the python packaging maintainers? They're listed
as Debian Python Team <team+pyt...@tracker.debian.org>, although I'm not
sure where that mail goes. You could try that and if you hear nothing,
consider one of the Uploaders named on the package: they're the actual
humans who have looked after it.
Is there a polite way to push the severity up from its current "normal"?
How important is breaking Debian Policy?
It can be a release blocker.
You could consider adjusting the bug's Severity. Is the
relevant bit of Debian Policy that is violated described as a "must" or
"required" directive (or similar)? In which case raising the bug
severity to "serious" would be appropriate, and also cause the package
to be flagged for dropping from Bookworm unless the bug is resolved
(that's one way to get attention!)
<https://www.debian.org/Bugs/Developer#severities>
Should I just leave it as it is? (I don't personally care all that much about
Terminator itself.)
I'm curious therefore what is it about this particular bug that has
grabbed your attention?
Also: is this the right mailing list to ask such questions?
Not really. It doesn't hurt though! The question might be more on-topic
on debian-devel.
--
Please do not CC me for listmail.
👱🏻 Jonathan Dowland
✎ j...@debian.org
🔗 https://jmtd.net
