Hi, the take button does not work because the package is not only orphaned but retired.
Since the mysql package will be a different package than community-mysql you will require a re-review for the mysql.

Once you have completed the review for the new mysql package link the BZ review in here and we will process the request.

Hello,

The content of the package 'mysql' prior the retirement is coming form the same source as the content of the 'community-mysql' package. That is verifiable by the 'sources' hash of the last content commit of the package 'mysql':
https://src.fedoraproject.org/rpms/mysql/c/0ecd31ed99039ff3e93e5fd289d7870073d2e978?branch=rawhide
and the first content commit of the package 'community-mysql':
https://src.fedoraproject.org/rpms/community-mysql/c/7a5573ff98af717540949576ac1418364950f4fe?branch=rawhide

The package 'mysql' was renamed to the 'community-mysql' and now I want to revert this change and rename the 'community-mysql' package back to 'mysql'.
(for reasons further explained in the 'F40_MariaDB_MySQL_repackaging' Fedora Self-Contained Change linked in this ticket description)

Since the mysql package will be a different package than community-mysql you will require a re-review for the mysql.

So if we are talking content-wise, your statement is false.

The previously 'mysql', now 'community-mysql' and after this ticket 'mysql' again, is still the same package, just differently named.

I also prepared code update to reflect the change of the package name and virtual provides. The package 'community-mysql' now provides the 'mysql' names. After the rename, I'll apply a code update which will provide the 'community-mysql' names from the 'mysql' package.

I'm asking you to re-evalue your last statement @humaton.

After re-reading through the Fedora Packaging guidelines I changed my mind.

I will follow the:
https://docs.fedoraproject.org/en-US/package-maintainers/Package_Renaming_Process/

and then re-use the BZ ticket for the:
https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#claiming

After I successfully claim the 'mysql' package, and I will test the new combination of RPM relationship tags works, I will follow the:
https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/
for the 'community-mysql' package.

if the commit histories fully line up, when it is unretired, it'd be nice to merge the package histories back in.

After re-reading through the Fedora Packaging guidelines I changed my mind.

I will follow the:
https://docs.fedoraproject.org/en-US/package-maintainers/Package_Renaming_Process/

and then re-use the BZ ticket for the:
https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#claiming

After I successfully claim the 'mysql' package, and I will test the new combination of RPM relationship tags works, I will follow the:
https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/
for the 'community-mysql' package.

Apologies for not including the link to the rename, it is what I was thinking about.
Once the re-review is done please link it and I will process it.

Is this moot now with the addition of mysql8.0?

This request is not relevant anymore.

In the end, we used a different approach.

What we had:

active:
 - mariadb
 - community-mysql
retired:
 - mysql

We went for creating new, versioned, packages:

mariadb105
mariadb1011
mysql80

And when we realized our mistake, we retired them and created new set with the dots (to use the same format as in python)

mariadb10.5
mariadb10.11
mysql8.0

Into those repositories, we added the Git history from the previous packages.
Thanks Neil for the suggestion.

The unorphaning of package mysql was meant as an intermediate step in the process, but in the end we skipped it.

So this request is not relevant anymore.

We still have some cleaning up to do after us, but everything should be ready for the F40 Changes 100% Complete Deadline - Feb 27th