Re: RFC: Proposing incompatible upgrade of python-asgiref from 3.4.1 to 3.7.2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dear all,

On 4/11/24 16:25, Michel Lind wrote:
Dear all,

Django 4.2 (the only currently supported LTS series) requires asgiref >=
3.6, so I would like to propose updating python-asgiref in EPEL 9 at
least to 3.6.0, but ideally to 3.8.1 for future proofing.

The affected packages (maintainers bcc:ed) are python-django3 (which I
maintain, and has just reached EOL) and python-opentelemetry

❯ fedrq whatrequires 'python3dist(asgiref)' -b epel9
python-django3-3.2.20-3.el9.src
python-opentelemetry-1.12.0-8.el9.src

❯ fedrq pkgs --src -P python-django3 -F requires -b epel9 | grep asgi
python3dist(asgiref) >= 3.3.2
(python3dist(asgiref) < 4~~ with python3dist(asgiref) >= 3.3.2)

❯ fedrq pkgs --src -P python-opentelemetry -F requires -b epel9 | grep asgi
(python3dist(asgiref) >= 3 with python3dist(asgiref) < 4)


The latest python-django3 and python-opentelemetry epel9 commits have been rebuilt
successfully in COPR against F39's asgiref 3.7.2, all rebuilt for both epel9 and epel9-next.

https://copr.fedorainfracloud.org/coprs/salimma/asgiref-3.7/packages/

I'll confirm whether we can go ahead with updating this at the EPEL meeting tomorrow, or we
should wait a full week per https://tdawson.fedorapeople.org/epel-docs/public/epel/epel-policy-incompatible-upgrades/
since this blocks the packaging of python-django4.2, and Django 3 is already EOL.

(per private discussion with the opentelemetry maintainer, music greenlit the upgrade provided opentelemetry scratch-rebuilds
fine as is)

Best regards,

--
 _o) Michel Lind (né Salim)
_( ) identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2

Attachment: OpenPGP_0x8B229D2F7CCC04F2.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

--
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-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/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux