Attempts to upgrade python34-six fail with an unexpected file conflict.
 I didn't see any Conflicts: or Obsoletes: tags in the spec file, so I'm
not sure where this conflict is coming from.

# yum --enablerepo epel-testing-upstream upgrade python34-six
Loaded plugins: langpacks, priorities
164 packages excluded due to repository priority protections
Resolving Dependencies
--> Running transaction check
---> Package python34-six.noarch 0:1.11.0-1.el7 will be updated
---> Package python34-six.noarch 0:1.11.0-2.el7 will be an update
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package          Arch       Version            Repository
   Size
================================================================================
Updating:
 python34-six     noarch     1.11.0-2.el7       epel-testing-upstream
   32 k

Transaction Summary
================================================================================
Upgrade  1 Package

Total download size: 32 k
Is this ok [y/d/N]: y
Downloading packages:
python34-six-1.11.0-2.el7.noarch.rpm                       |  32 kB
00:00
Running transaction check
Running transaction test


Transaction check error:
  file /usr/lib/python3.4/site-packages/six-1.11.0-py3.4.egg-info from
install of python34-six-1.11.0-2.el7.noarch conflicts with file from
package python34-six-1.11.0-1.el7.noarch


--Wart

On 3/13/19 9:30 AM, 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.
> 
> 
> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-f2d195dada
> https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-9e9f81e581
> 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@lists.fedoraproject.org
> 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@lists.fedoraproject.org
> 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@lists.fedoraproject.org
> 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.
> 
_______________________________________________
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org

Reply via email to