nonresponsive maintainer bug: https://bugzilla.redhat.com/show_bug.cgi?id=2087774

I believe this should be https://bugzilla.redhat.com/show_bug.cgi?id=2088744

nonresponsive maintainer bug: https://bugzilla.redhat.com/show_bug.cgi?id=2087774

I believe this should be https://bugzilla.redhat.com/show_bug.cgi?id=2088744

You're right, thanks :)

+1

@madko Are you still interested in maintaining Fedora packages?

@aekoroglu You are now a co-maintainer of glances.

APPROVED (+1,0,-0)

Assigned glances to @aekoroglu.

madko is main admin of rpms/darktable
  madko is no longer the main admin of rpms/darktable
madko is main admin of rpms/libnss-pgsql
  madko is no longer the main admin of rpms/libnss-pgsql
madko is watching rpms/pam_mysql
  madko is no longer watching rpms/pam_mysql
madko is watching rpms/pystatgrab
  madko is no longer watching rpms/pystatgrab

Announced: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/S26Y3HFGRK2EWDO6FDCTSCGHMJY54ZXZ/

Hello, I am the person that actually maintained darktable since 2015. Can you please set me as main admin of the package?
Thank you

Also, for the future, before setting a package to orphan you really should check if the package is being maintained by other package admins/committers

We're talking about improving the policy here:
https://pagure.io/fesco/issue/2855

In the meantime: While the end result is obviously not the one you wanted, your status with respect to the darktable package has not changed, has it? I suspect that if you ask the new "main admin", he'd gladly step aside and make you the main maintainer, given that you've been the person who was actually taking care of the package for the last few years (and your ACL just didn't reflect that fact well enough).

I changed the settings for darktable, thank you @decathorpe and @germano