I have updated it to the latest version and would like to see it back in Fedora.
I have built RPM's for my own use before, but never to submit to the official repositories. If there are things in my SPEC file which are not OK, I'm happy to fix them, but I might need some advice on it.
When do you need this? (YYYY/MM/DD) What about for the next release?
When is this no longer needed or useful? (YYYY/MM/DD) I have constantly used remind for the last 15 or even more years and intend to use it for many more years to come.
If we cannot complete your request, what is the impact? Well, I can compile it for my own purposes. But it's a pity if everybody intending to use this fine piece of software needs to roll their own compilation or go hunting for a pre-compiled package. A simple and clean dnf -y install remind is so much more useful.
dnf -y install remind
There are a few things that you need to ensure before getting ownership of this package. Make sure you are in the packagers group[1] and if the package is retired for more than 8 weeks, you need to file a Bugzilla ticket which is the package review tracking ticket that is required only for new or long retired packages[2].
[1] - https://docs.fedoraproject.org/en-US/package-maintainers/How_to_Get_Sponsored_into_the_Packager_Group/ [2] - https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#claiming
There are a few things that you need to ensure before getting ownership of this package...
OK. I've had a look at that information and quite honestly, I don't feel confident enough at all to take ownership of the package, sorry. I'll be happy to help keep the package up to date and fix problems as best as I can and learn the ropes around package maintaining along the way.
If somebody more experienced steps up and takes ownership I'll be happy to support them as best as I can.
You might post to the devel mailing list ( devel@lists.fedoraproject.org ) and/or discussion.fedoraproject.org and ask if any maintainers want to take it on... :)
Metadata Update from @phsmoura: - Issue tagged with: low-gain, low-trouble, ops
Original website does not exist anymore : https://www.roaringpenguin.com Hard to find latest source code.
Ah the original author has it on her website: https://dianne.skoll.ca/projects/remind/
And we have a GIT updated last week: https://git.skoll.ca/Skollsoft-Public/Remind
As mentioned on the mailing list, I will take over maintenance of this package. A re-review will be submitted shortly.
A re-review request has been opened here: https://bugzilla.redhat.com/show_bug.cgi?id=2246133
Should this releng request be closed and I open one with my own account? I'm not sure what (if any) automation is associated with these tickets.
Thanks, @neil, once the review gets fedora_review+ flag we will process the request and close this ticket with an update.
Hi @humaton - I was looking through my open issues and realized I accidentally filed a second un-retire request for remind recently, now that the re-review is completed.
https://pagure.io/releng/issue/11917
Commenting here so that we can close this or the other for the unretirement :)
The ticket opened by neil is processed and this can be closed thanks!
Metadata Update from @jnsamyak: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)