On 11 November 2023 8:31:25 am IST, Maytham Alsudany <maytha8the...@gmail.com> 
wrote:
>On Sat, 2023-11-11 at 02:31 +0530, Nilesh Patra wrote:
>> My personal experience is that maintainer maintained manpages are
>> seldom well-maintained and tend to get outdated with new versions
>> if the maintainer forgets to update these regularly.
>> Also, that manpages keep introducing new lintian warnings with new
>> version of troff/groff.
>> 
>> Since this package already requires some maintenance, I feel it would be
>> an additional burden on me and you. It is IMHO the best case scenario if
>> the upstream maintains a manpage themselves.
>
>Opened an issue upstream[1].

Since they said PRs are welcome, maybe we could send them a manpage and a 
script to recreate it everytime.
I think createmanpages script could be handy

<https://salsa.debian.org/med-team/community/helper-scripts/-/blob/master/createmanpages>

>Regarding the inconsistent shebangs in the Python files, I've opened an
>issue upstream regarding that[3].

Yep, and it seems to have been changed to "usr/bin/env python" instead in the 
fixing commit :-/

Seems like we will have to keep the `sed` call for a while.

>Regarding splitting up the kitty and kitten components, I've opened an
>issue upstream[2], but the upstream author promptly closed it, stating

Something similar happened with me when I forwarded

<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054633>

Upstream which I can reproduce and it was closed very quickly.

My impression is that the upstream is somewhat tricky to deal with - but I 
guess with time, we will manage somehow.

>that "the Go code depends on the rest of the code so splitting it is
>not going to happen."

I've added a comment there. Let's see if they consider to do something about it.

>I may open PRs for [1] and [3] to ensure they're fixed quickly.
>
>Would you like me to bump the version of the package to 0.31.0 now that
>0.30.1 has been uploaded to experimental?

Sure, if you have the time! :)

>[1]: https://github.com/kovidgoyal/kitty/issues/6808
>[2]: https://github.com/kovidgoyal/kitty/issues/6809
>[3]: https://github.com/kovidgoyal/kitty/issues/6810

Best,
Nilesh

Reply via email to