I will need to reproduce this bug. I am going out of town for a office meeting tomorrow. I will be back on Wednesday. I will look into it after that. If any one wants to work on it in between, you are welcome :)

One thing for this is that in pkgdb only package administrators can orphan a package and groups are not administrators, they are only used to provide commits to a group of people.

So we would have to decide if we want to change this.

Note this relates to #103

I'd like to retire python3-dateutil, where I'm only admin and a group is POC.
It fails with:

$ pkgdb-cli orphan --retire python3-dateutil master
No output returned by https://admin.fedoraproject.org/pkgdb/api/package/retire/

Is this the expected output, when I'm not allowed to retire it? Or a bug in the server?

Would it be possible to let admins retire the package, if a group is the POC? This would be at least the expected solution in this case. I don't know if anyone from the group should be able to retire it or if one still requires an admin.
That would solve at least this issue until #103 is solved.

You're supposed to retire a package via fedpkg retire, does it make any difference?

I tried that first and then manually with pkgdb-cli after it failed. Running it again, I get the same output:

$ fedpkg retire "python3-dateutil is now a subpackage of python-dateutil again (#1126521)"
dead.package found, package probably already retired - will not remove files from git or overwrite existing dead.package file
Everything up-to-date
Could not retire package: No output returned by https://admin.fedoraproject.org/pkgdb//api/package/retire/

I think I found a couple of bugs in the process of replicating the issue.
I addressed them here: #161

#161 has been merged and I pushed a bugfix release with these changes.

We already fixed python3-dateutil so I'll keep this ticket opened until we can find out if the patches are working as expected.

The F22 branch also needed to be retired and it worked just fine.
Thanks for the fix.