A week has passed and this bug is still in the NEW state and the package does not install.

Please fix this or indicate that you are working ona  fix by setting the state to ASSIGNED.

After 3 such reminders, this package may be orphaned.

https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Removing_non-installable_packages_from_the_distro

Thanks

In preparation for the Python 2 EOL, we are removing all non-installable Python 2 packages:
https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Removing_non-installable_packages_from_the_distro

This bug is still in the NEW state and the package does not install. Please indicate you are working on a fix by setting the state to ASSIGNED. When this bug is four weeks in the NEW state, the package may be orphaned.

Note that you don't have to actually fix this right now, setting the bug to ASSIGNED will just mark this as being worked on, so I'll know it is being taken care of. If this happens too quickly, feel free to reach to me any time for help (with specific problems).

(My previous comment might have come across a bit too aggressive. I'm sorry, that was not my intention.)

(If you know for sure this package shall be removed, consider doing it.)

Thank You!

This bug is still in the NEW state and the package does not install. Please indicate you are working on a fix by setting the state to ASSIGNED. When this bug is four weeks in the NEW state, the package may be orphaned.

This bug is still in the NEW state and the package does not install. Please indicate you are working on a fix by setting the state to ASSIGNED. When this bug is four weeks in the NEW state, the package may be orphaned.

So, I have a fix merged in fact that's waiting for a new release.
I'm trying to finish py3 support, and then I should have this released.

*** Bug 1675996 has been marked as a duplicate of this bug. ***

The package was retired.

I am confused -- I read py3 support is coming and then I read sigul is retired.  Is there an alternative to sigul for signing koji builds?

Here: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/

"A week before the mass branching, any packages which still have open FTBFS bugs from the previous release will be retired."

Once the package is ready to build again, it can be unretired.

The package wasn't installable, so not having it at all is not any worse.

Miro, thanks for responding!

I agree with the policy and rationale, but my understanding is that the Fedora Project uses (or used) sigul to sign its packages.  If FPO no longer uses sigul, I'd like to know what is used now or what alternatives exist since I need *something* to fill that role.

I am unaware of any other software that does this, but FPO *must* be using *something*.  I follow the rel-eng ML and haven't seen any discussion there about this nor do I get any hint with all the Google searches I've tried.  I asked on the devel ML once directly and didn't get a reply.  I was actually hoping sometime back that the FTBFS situation here would actually clear up some of these details, but it's almost as if they're being hidden, which seems very unlike the FPO or RH that I've known for eons.  Basically, I'm lost in the woods and can't find the next trail marker.

Unfortunately, I don't really know anything about sigul deployment. Since it doesn't install, I guess that either the signing doesn't happen on recent Fedora versions (aka rawhide packages are not signed with sigul running on rawhide) or the team has osme extra packages in the repo.

I'd help you if I knew this kind of things, but I don't. I'm sorry.