What should be done if requests for a new package version are not answered?

Example: 1977025 – kitty-0.24.1 is available

The last packaged version was released on Jun 27, 2021 and there have been several upstream versions since then.

As a user, what else could/should one do to help bring about an update to such a package?

1 Like

We have this policy

https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/

2 Likes

Other options:

  • open a pull request to help the maintainer (maintainers are volunteers and often get busy with dayjobs and life, and have to limit their volunteering time).

If you’re not a package maintainer, you’ll have to use these instructions:

https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Package_Maintainers/

  • apply for co-maintainership so you can help maintain the package.
2 Likes

As a long term goal, measure the time and effort needed to submit an update for review, and simplify the process.

There’s a lot of work on-going to simplify packaging already, but there’s no substitute for understanding the build system etc.

Chiming in on posts saying “you should do this” doesn’t help. It’s all very well to say “do this”, but it’s always preferable in the community to say “I think this can be improved, so I’ll go ahead and work on it”. So if you have concrete ideas of improvement, please work on implementing them to help the community. Even just starting a discussion on the the correct channels with ideas would be a good step to take :+1:

Says “you should do this” post.

1 Like