PyPI Release: django-fsm-log Received "500: INTERNAL SERVER ERROR"

[ticosax]

The release action is failing without proper insights of what is wrong.

Checking dist/django_fsm_log-4.0.2-py3-none-any.whl: PASSED
Checking dist/django_fsm_log-4.0.2.tar.gz: PASSED
Uploading distributions to https://jazzband.co/projects/django-fsm-log/upload
Uploading django_fsm_log-4.0.2-py3-none-any.whl
WARNING  Received "500: INTERNAL SERVER ERROR"                                  
         Package upload appears to have failed. Retry 1 of 5.                   
Uploading django_fsm_log-4.0.2-py3-none-any.whl
WARNING  Received "500: INTERNAL SERVER ERROR"                                  
         Package upload appears to have failed. Retry 2 of 5.                   
Uploading django_fsm_log-4.0.2-py3-none-any.whl
WARNING  Received "500: INTERNAL SERVER ERROR"                                  
         Package upload appears to have failed. Retry 3 of 5.                   
Uploading django_fsm_log-4.0.2-py3-none-any.whl
WARNING  Received "500: INTERNAL SERVER ERROR"                                  
         Package upload appears to have failed. Retry 4 of 5.                   
Uploading django_fsm_log-4.0.2-py3-none-any.whl
WARNING  Received "500: INTERNAL SERVER ERROR"                                  
         Package upload appears to have failed. Retry 5 of 5.                   
WARNING  Error during upload. Retry with the --verbose option for more details. 
ERROR    HTTPError: 500 Internal Server Error from                              
         https://jazzband.co/projects/django-fsm-log/upload                     
         INTERNAL SERVER ERROR                                                  
0s

https://github.com/jazzband/django-fsm-log/actions/runs/12669866525/job/35308263329

We do not know what to do to solve this issue as we were able to make releases in the past.

[jezdez]

Can you try again?

[ticosax]

Can you try again?

Sure thing, Thanks for checking it.

[ticosax]

@jezdez It is still failing with the same behavior. https://github.com/jazzband/django-fsm-log/actions/runs/15585104148/job/43889245741

[bittner]

The output in the build steps before the failure shows deprecation warnings about the license metadata field. I'd suggest to address those. It's not guaranteed that it will fix the issue, but according to my experience the transition to enforcing the license field with setuptools and PyPI is somewhat a bumpy road. It certainly won't harm.

Suggested Changes

 [project]
-license = { file = "LICENSE" }
+license = "MIT"
+license-files = ["LICENSE"]
 description = "Transition's persistence for django-fsm"

 [build-system]
-requires = ["setuptools>=64", "setuptools_scm>=8"]
+requires = ["setuptools>=80", "setuptools_scm>=8"]
 build-backend = "setuptools.build_meta"

I'd also suggest to move the [build-system]section to the top of the file, because this is common practice, IMHO.

The empty [tool.setuptools_scm] section also makes me uneasy, and to cancel out potential issues that may have come along the way I'd either remove it or move it to the end of the file, preferably together with the [tool.setuptools] section. (If you sort the sections alphabetically this all comes for free.)

[ticosax]

Thanks @bittner I will give it a try