RHBZ ticket: https://bugzilla.redhat.com/show_bug.cgi?id=1740611 Old RHBZ ticket with countdown: https://bugzilla.redhat.com/show_bug.cgi?id=1733802 Mailing lists thread: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/DKSNXHDGZ6G43LS3G5H3B6EUX73U6MFV/
6 months ago I already followed non-responsive procedure for the same package, but after FESCo request (direct cc) maintainer appeared, build package and disappeared again. I think he is no longer interested in maintaining goldendict package or has no free time for it.
I asked him to give package to me multiple times (in FESCo ticket, in RHBZ and even in a separate ticket).
I'm asking FESCo to give goldendict package to me.
+1
Metadata Update from @churchyard: - Issue tagged with: nonresponsive maintainer
cc @moceap
+1 FTR
I've added @xvitaly as an admin to the goldendict package.
goldendict
Thanks. Update created for F30, F31 and Rawhide.
Thanks. This is now approved (+4,0,-0) and we will ping @moceap here for a while. Will make you the main admin and orphan the rest of @moceap's packages (if any) if there is no response by @moceap in 2 weeks.
Metadata Update from @churchyard: - Issue assigned to churchyard
Wow .. @xvitaly second call to make me Non-responsive maintainer !!!
You created a pull request https://src.fedoraproject.org/rpms/goldendict/pull-request/2 and I accepted it in the same time!!!
I think this second call also not really worth. Anyway you are comaintainer now.
Yes, because goldendict package was broken for 3 months and you did nothing to fix it and did not answer to RHBZ tickets.
and I accepted it in the same time!!!
But did not upload sources to Fedora SCM, did not build it and push updates to all Fedora branches.
Now I finally fixed goldendict package. It works.
@moceap Please don't make this personal. This is about a desperate packager wanting to fix things, not a personal attack on you.
Ok no problem.
My Fedora contribution not a hobby, the busyness just because University concerns.
Anyway I think no need to leave this bug opened.
Metadata Update from @churchyard: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
Metadata Update from @churchyard: - Assignee reset
Login to comment on this ticket.