Bodhi 4 in EPEL 7

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

 



Greetings!

Fedora Infrastructure recently deployed Bodhi 4.0.0 to production,
which included quite a few backwards incompatible changes[0]. Some of
the changes have resulted in older Bodhi clients (less than 4.0.0) not
being compatible with the new version of the server.

In Fedora, FESCo decided to allow the Bodhi 4.0.0 update to go to
Fedora 29 and 30, and for us to add a bodhi3 compat client package in
case there were any users counting on using the bodhi3 client with a
non-Fedora Bodhi server[1] (believe it or not, there are other Bodhi
deployments out there!)

EPEL 7 currently has a fairly old Bodhi version (2.11.0). This version
is also not compatible with the Bodhi 4 server.

What do you think about upgrading Bodhi in EPEL 7 as well?

There are a few things I'd like to highlight for consideration here:

* Bodhi 4 is Python 3 only. Bodhi 2 is Python 2 only. So, upgrading to
  Bodhi 4 isn't just a switch to a newer Bodhi, it will also mean a
  switch in Python versions. This will affect dependencies (there are a
  few).
* I think we might be missing Python 3 dependencies for Bodhi 4.
* It might be good to consider dropping the Bodhi server as we do this.
  EPEL 7 has versions of some of Bodhi's server dependencies that are
  too old for Bodhi 4. I *think* the client should be OK with the
  client dependency versions, but of course you never know until you
  try.
* Would we want to maintain a bodhi2 compat package for EPEL 7,
  analagous to the bodhi3 compat package we made for Fedora?
* What about EPEL 6? It's still on Bodhi 0.9, and I have never seen or
  worked on that codebase. Unfortunately, it has Python 2.6 and not any
  verison of Python 3, to my knowledge.

Anything else you can think of?


[0] https://bodhi.fedoraproject.org/docs/user/release_notes.html#v4-0-0
[1] https://pagure.io/fesco/issue/2137

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx

[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