Hey Mattias, On 1/5/22 09:39, Matthias Runge wrote: > Hey there, > > would it be too late to upgrade Django for Fedora 36 to version 4.0.x? > It may require some more package updates, not just Django itself. > > The releasenotes are here[1], We have version 3.2 in Fedora 35, which > is a long-term supported release (until 2024)[2]. > > Unfortunately, I am not able to answer the question of "what would > break?". However, not shipping a newer release would show Fedora as > outdated software. I can help you with assessing the impact, we do this routinely as a part of update workflow in the Python-maint team. The idea is to discover which packages depend on your package in the build time and then rebuild them on top of the changed package. For that, we use Copr. The process is described here (it may be a bit obscure for people not familiar with Copr): https://hackmd.io/81DXky5lRj-cUiSTeiag2A?view Feel free to reach me off list if you'd like any help with that. Those are packages that require python3-django in the build time: $ repoquery --repo=rawhide{,-source} --whatrequires python3-django --recursive | grep src$ | pkgname | sort | uniq ara bodhi monkeytype python3-openid python-authlib python-django-allauth python-django-appconf python-django-auth-ldap python-django-configurations python-django-contrib-comments python-django-debreach python-django-extensions python-django-filter python-django-formtools python-django-gravatar2 python-django-haystack python-django-ipware python-django-mailman3 python-django-markdownx python-django-picklefield python-django-prometheus python-django-pyscss python-djangoql python-django-redis python-django-uuslug python-environs python-hypothesis python-livereload python-odata-query python-opentelemetry python-pyscaffold python-pytest-django python-shortuuid python-whitenoise And there are also packages that pin Django to version lower than 4.x - those will stop building after the update and it would be good to work with the respective upstreams to have it unpinned on time. $ for pkg in $(repoquery -q --repo=rawhide{,-source} --whatrequires python3-django); do repoquery -q --repo=rawhide{,-source} --requires $pkg | grep -E '\bdjango\b' | grep '<' && echo -e "${pkg}\n"; done (python3.10dist(django) < 3.3~~ with python3.10dist(django) >= 2.2) hyperkitty-0:1.3.5-1.fc36.noarch (python3.10dist(django) < 3.3~~ with python3.10dist(django) >= 2.2) postorius-0:1.3.6-1.fc36.noarch (python3.10dist(django) < 3.3~~ with python3.10dist(django) >= 2.2) python3-django-mailman3-0:1.3.7-1.fc36.noarch (python3.10dist(django-picklefield) < 4~~ with python3.10dist(django-picklefield) >= 3.0.1) python3-django-q-0:1.3.9-2.fc36.noarch Karolina > > As hinted in the previous paragraph, I am not involved in any > development connected to Django for some time now. This is a cry for > help. The whole Django stack in Fedora could use more helping hands. > Upstream is very good at providing insights, timelines etc and also > keeps it secured. That also means, there are regular updates. > > Matthias > > > [1] https://www.djangoproject.com/weblog/2021/dec/07/django-40-released/ > [2] https://www.djangoproject.com/download/ _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
