Re: EPEL-ANNOUNCE EPEL: Python34 moving to Python36

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

 



On 3/25/19 10:18 AM, Stephen John Smoogen wrote:
> On Mon, 25 Mar 2019 at 13:07, Miro Hrončok <mhroncok@xxxxxxxxxx> wrote:
>>
>> On 13. 03. 19 15:30, Stephen John Smoogen 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.
>>>
>>> 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.
>>
>> A problem was pointed out in
>> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-f2d195dada#comment-914787
>>
>> If you have 3rd party software using /usr/bin/python3 and you have python34
>> installed, updating your system will remove that symlink and your software breaks.
>>
>> However we cannot obsolete python34 form python36, because that breaks software
>> that actually wants and uses /usr/bin/python3.4 and possibly make python34
>> uninstallable (not sure).
>>
>> So arguably, the update should update both python34 and install python36,
>> keeping both Pythons available, the user/admin could than remove the one that is
>> not needed.
>>
>> AFAIK The only thing that would make this happen is to require python36 from
>> python34. And that seems like a huge ugly workaround with unwanted side affects.
>>
> 
> Here is a hair-brained idea. have them both require
> python3-versioned-command which puts in the alternatives logic and
> sets it to 1 of 3 options?
> 1. python34
> 2. python36
> 3. you didn't install a python silly

I think that could be confusing (not that the alternatives are much
else. ;)

But we talked about this a lot on IRC.

Just make python36 obsolete the old version of python34 that had
/usr/bin/python3. This causes yum to install the new python34 and pull
in python36 for /usr/bin/python3.

It does mean people with 3rd party software are now using python36
instead of 34, but if they only speficied /usr/bin/python3, it should
just run with any python3 version right?

kevin


Attachment: 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://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