I want to unretire tmuxinator, as it is a tool I use and I was surprised to find it is currently retired. Searching through the mailing list, it appears to have been retired simply due to being orphaned.
I have a copr repo, https://copr.fedorainfracloud.org/coprs/jimtahu/tmuxinator/, which I have personally been using. And have now created a review request https://bugzilla.redhat.com/show_bug.cgi?id=1891335
The new version needs rubygem-xdg, I found a previous review that didn't make it into the repos here https://bugzilla.redhat.com/show_bug.cgi?id=1654426, so I created a separate request https://bugzilla.redhat.com/show_bug.cgi?id=1891335
The new version also needs an update to rubygem-thor (1.0.1) which I found has an existing ticket https://bugzilla.redhat.com/show_bug.cgi?id=1783465 with matching pull request https://src.fedoraproject.org/rpms/rubygem-thor/pull-request/1
On Sun, Oct 25, 2020 at 8:05 PM Micah Shennum jimtahu@gmail.com wrote:
I want to unretire tmuxinator, as it is a tool I use and I was surprised to find it is currently retired. Searching through the mailing list, it appears to have been retired simply due to being orphaned.
When it got retired, it was also stuck on an old version that didn't work well with the tmux version of the time.
I have a copr repo, https://copr.fedorainfracloud.org/coprs/jimtahu/tmuxinator/, which I have personally been using. And have now created a review request https://bugzilla.redhat.com/show_bug.cgi?id=1891335
The new version needs rubygem-xdg, I found a previous review that didn't make it into the repos here https://bugzilla.redhat.com/show_bug.cgi?id=1654426, so I created a separate request https://bugzilla.redhat.com/show_bug.cgi?id=1891335
The new version also needs an update to rubygem-thor (1.0.1) which I found has an existing ticket https://bugzilla.redhat.com/show_bug.cgi?id=1783465 with matching pull request https://src.fedoraproject.org/rpms/rubygem-thor/pull-request/1
I have also have a copr repository where I had to prepare the same set of packages:
https://copr.fedorainfracloud.org/coprs/dridi/tmuxinator/packages/
Feel free to compare our specs, I believe I followed the ruby packaging guidelines correctly at the time. I'm not actively maintaining the packages myself because I don't have time and I'm not a ruby developer so I don't feel confident taking bug reports. But if you don't find a reviewer in a week, I will find time to review your submissions. I will CC myself to the 2 bugzilla tickets.
Thanks!
Dridi
Thank you, I will be sure to compare specs. On a related note, I am of course also open to co-maintainership.
On 10/26/20 12:37 AM, Dridi Boukelmoune wrote:
On Sun, Oct 25, 2020 at 8:05 PM Micah Shennum jimtahu@gmail.com wrote:
I want to unretire tmuxinator, as it is a tool I use and I was surprised to find it is currently retired. Searching through the mailing list, it appears to have been retired simply due to being orphaned.
When it got retired, it was also stuck on an old version that didn't work well with the tmux version of the time.
I have a copr repo, https://copr.fedorainfracloud.org/coprs/jimtahu/tmuxinator/, which I have personally been using. And have now created a review request https://bugzilla.redhat.com/show_bug.cgi?id=1891335
The new version needs rubygem-xdg, I found a previous review that didn't make it into the repos here https://bugzilla.redhat.com/show_bug.cgi?id=1654426, so I created a separate request https://bugzilla.redhat.com/show_bug.cgi?id=1891335
The new version also needs an update to rubygem-thor (1.0.1) which I found has an existing ticket https://bugzilla.redhat.com/show_bug.cgi?id=1783465 with matching pull request https://src.fedoraproject.org/rpms/rubygem-thor/pull-request/1
I have also have a copr repository where I had to prepare the same set of packages:
https://copr.fedorainfracloud.org/coprs/dridi/tmuxinator/packages/
Feel free to compare our specs, I believe I followed the ruby packaging guidelines correctly at the time. I'm not actively maintaining the packages myself because I don't have time and I'm not a ruby developer so I don't feel confident taking bug reports. But if you don't find a reviewer in a week, I will find time to review your submissions. I will CC myself to the 2 bugzilla tickets.
Thanks!
Dridi _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
On Tue, Oct 27, 2020 at 1:35 AM Micah Shennum jimtahu@gmail.com wrote:
Thank you, I will be sure to compare specs. On a related note, I am of course also open to co-maintainership.
I wish I could say the same, but the reason why I'm currently using tmuxinator via my copr repository is precisely that I don't have time to do anything but the bare minimum for Fedora these days.
On Sun, Oct 25, 2020 at 3:05 PM Micah Shennum jimtahu@gmail.com wrote:
I want to unretire tmuxinator, as it is a tool I use and I was surprised to find it is currently retired. Searching through the mailing list, it appears to have been retired simply due to being orphaned.
I have a copr repo, https://copr.fedorainfracloud.org/coprs/jimtahu/tmuxinator/, which I have personally been using. And have now created a review request https://bugzilla.redhat.com/show_bug.cgi?id=1891335
The new version needs rubygem-xdg, I found a previous review that didn't make it into the repos here https://bugzilla.redhat.com/show_bug.cgi?id=1654426, so I created a separate request https://bugzilla.redhat.com/show_bug.cgi?id=1891335
The new version also needs an update to rubygem-thor (1.0.1) which I found has an existing ticket https://bugzilla.redhat.com/show_bug.cgi?id=1783465 with matching pull request https://src.fedoraproject.org/rpms/rubygem-thor/pull-request/1
Hopefully someone's already picked up on the fact that you need a sponsor, however it may be a good idea to write a separate email to the devel list with NEEDSPONSOR in the subject. I would sponsor you but I mostly maintain C/C++ packages (and a few python ones) and know zero about Ruby.
Thanks, Richard