This bug is part of the non-responsive maintainer procedure for atim, following https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/. Please respond if you are still active in Fedora and want to maintain kitty.
Hello. I am still and if you want to help with update and maintaining i could add you as co-maintainer. Currently new versions requires new python modules. Some already packaged: ipython-sphinx, sphinx-copybutton, sphinx-inline-tabs. Need to package: sphinxext.opengraph. Would you like to help with packaging this missing modules?
Good to hear that you're still active in Fedora! Hmm, but do we really need to build the documentation from source? Looking at the Arch [1] and Gentoo [2] packages for kitty, it looks like there is pre-built documentation that they use, which Fedora should also be able to use, from the signed source tarball release (in the docs/_build directory in [3]). I don't know about being a maintainer, but I think what could be done is: * Remove kitty-no_sphinx.patch * Replace the upstream URL with https://github.com/kovidgoyal/kitty/releases/download/v%{version}/%{name}-%{version}.tar.xz * Edit the spec file to only include the pre-built documentation when using the doc package [1] https://github.com/archlinux/svntogit-community/blob/packages/kitty/trunk/PKGBUILD [2] https://gitweb.gentoo.org/repo/gentoo.git/tree/x11-terms/kitty/kitty-0.24.1.ebuild [3] https://github.com/kovidgoyal/kitty/releases/download/v0.24.1/kitty-0.24.1.tar.xz
@Alex good day. I found one person who also willing to help with update and maintaining package and there only one left package which need to package: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2049095. So once new package repo will be created then we can update Kitty. Without scarifying building documentations from sources. Also if you interesting in co-maintainership just let me know.
FEDORA-2022-1cb8eddfac has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-1cb8eddfac
FEDORA-2022-1cb8eddfac has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-1cb8eddfac` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-1cb8eddfac See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-1a55584f6a has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-1a55584f6a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-1a55584f6a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-9a18554791 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-9a18554791` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-9a18554791 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle. Changing version to 36.
FEDORA-2022-cd34d54495 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.