Am 18.07.24 um 12:36 schrieb Íñigo Huguet:
but more important, the new release (1.12.0) requires NetworkManager >=
1.46.2 explicitly!
https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/blob/main/NEWS
There is no problem here. I did the fixes upstream, and I backported
them to RHEL 9.4 (via NM 1.46.0-11). So in the upstream
NetworkManager, the fix is available only from 1.46.2, but in RHEL it
is available in 1.46.0-11.
Ah, I see, then everything is clear and fine. Thanks for the backport.
So, correct me if I am wrong but for RHEL9.4 (via EPEL9) it can not be
shipped BUT for CentOS Stream 9 (via EPEL9-NEXT) if you want ...
I backported the patches with the hope of being available for RHEL
9.4. The only real problem that I still see is that "it's not common
to include the release number in the requires statements". As I said,
I will trust others' opinions about this.
Using a NEVR is valid but I do not see it that much, and with the
mentioned patch obviously necessary.
Not sure how to include it in epel-next, though, I don't see any
`epel*-next` branch in NetworkManager-openvpn dist-git. I will need to
read the docs, I guess.
Well, with the upcoming release (1.46.0-11) its not necessary ...
--
Leon
--
_______________________________________________
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
