Hello, On Wed, Mar 13, 2019 at 3:37 PM Stephen John Smoogen <smooge@xxxxxxxxx> wrote: > > Over the last 5 days, Troy Dawson, Jeroen van Meeuwen, Carl W George, > and several helpers have gotten nearly all of the python34 packages > moves over to python36 in EPEL-7. They are being included in 6 Bodhi > pushes because of a limitation in Bodhi for the text size of packages > in an include. I was about to start a thread about this, so it saves me a fair amount of time. I have been working on this today, so this is very fresh: https://github.com/varnishcache/pkg-varnish-cache/pull/124 My complaint is that the current packages for python34-{sphinx,docutils} don't seem to have provides with a "python3-" prefix. So while I can live with that fact, I'm not happy with the prospect of having to break the continuity soon and have to move my BuildRequires to a python36- prefix. One more thing about those two specific packages, they also don't provide binaries suffixed with "-3" so that means having to change packaging again so that configures picks up rst2man-3.6 instead of rst2man-3.4 and that's not a comfortable place to be in downstream. > The current day for these package groups to move into EPEL regular is > April 2nd. We would like to have all tests we find in the next week or > so also added so that the updates can occur in a large group without > too much breakage. > > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-f2d195dada > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-9e9f81e581 I'm a bit confused because it seems the update above contains both builds for the packages I'm interested in, and seems to keep building the 3.4 variant of the package in addition to the new 3.6 builds. That means I should not worry about having to move away from today's work, right? And I guess cohabitation would explain why I don't get a shiny python3-foo package and foo-3 binaries? If so, feel free to redirect my grumpiness to /dev/null :) > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-0d62608bce > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-5be892b745 > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-0f4cca7837 > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-ed3564d906 > > Please heavily test them by doing the following: > Stage 1 Testing > Install RHEL, CentOS, or Scientific Linux 7 onto a TEST system. > Install or enable the EPEL repository for this system > Install various packages you would normally use > yum --enablerepo=epel-testing update > Report problems to epel-devel@xxxxxxxxxxxxxxxxxxxxxxx > Stage 2 Testing > Check for any updated testing instructions on this blog or EPEL-devel list. > Install RHEL, CentOS, or Scientific Linux 7 onto a TEST system. > Install or enable the EPEL repository for this system > yum install python34 > yum --enablerepo=epel-testing update > Report problems to epel-devel@xxxxxxxxxxxxxxxxxxxxxxx > Stage 3 Testing > Check for any updated testing instructions on this blog or EPEL-devel list. > Install RHEL, CentOS, or Scientific Linux 7 onto a TEST system. > Install or enable the EPEL repository for this system > yum install python36 > yum --enablerepo=epel-testing update > Report problems to epel-devel@xxxxxxxxxxxxxxxxxxxxxxx > This should cover the three most common scenarios. Other scenarios > exist and will require some sort of intervention to work around. We > will outline them as they come up. > > Many Many Thanks go to Troy, Jeroen, Carl, and the many people on the > python team who made a copr and did many of the initial patches to > make this possible. Amazing timing! Dridi _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 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/devel@xxxxxxxxxxxxxxxxxxxxxxx
