On Sat, 2023-11-11 at 02:31 +0530, Nilesh Patra wrote: > > If would be good to get a second pair of eyes on my commits, since I've made > > some decisive patches. > > I have removed all commits adding manpage. Furthermore you added a > compress command to dh_auto_test this would lead to installing different > manpage based on whether or not tests are run (for instance skipped via > nocheck). This is a bug, IMHO. Yep, that's my mistake, I meant to put it in dh_auto_build or dh_auto_install. > 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]. Regarding the inconsistent shebangs in the Python files, I've opened an issue upstream regarding that[3]. Regarding splitting up the kitty and kitten components, I've opened an issue upstream[2], but the upstream author promptly closed it, stating that "the Go code depends on the rest of the code so splitting it is not going to happen." 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? > [1]: https://github.com/kovidgoyal/kitty/issues/6808 [2]: https://github.com/kovidgoyal/kitty/issues/6809 [3]: https://github.com/kovidgoyal/kitty/issues/6810 Kind regards, Maytham
Attachment:
signature.asc
Description: This is a digitally signed message part