Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1605204 - python-fedora3 conflicts with python-fedora2
Summary: python-fedora3 conflicts with python-fedora2
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: python-fedora
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Nils Philippsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1608068 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-20 12:42 UTC by Jakub Čajka
Modified: 2020-12-02 08:36 UTC (History)
9 users (show)

Fixed In Version: python-fedora-1.1.0-2.fc33 python-fedora-1.1.0-2.fc32
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-06 01:14:50 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1604882 0 unspecified CLOSED moose: FTBFS in Fedora rawhide 2022-05-16 11:32:56 UTC

Internal Links: 1604882 1903289

Description Jakub Čajka 2018-07-20 12:42:34 UTC
Description of problem:
python-fedora3 conflicts with python-fedora2 resulting in no update path and broken dnf transaction.

Version-Release number of selected component (if applicable):
I guess python2-fedora-0.10.0-5.fc29.noarch fedora-0.10.0-3.fc28.noarch

How reproducible:
Always

Steps to Reproduce:
1. dnf update on rawhide machine with both python2-fedora and python3-fedora

Actual results:
.
.
.
[SKIPPED] python2-fedora-0.10.0-5.fc29.noarch.rpm: Already downloaded                                                                                                                                             
Running transaction check
Transaction check succeeded.
Running transaction test
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Transaction check error:
  file /usr/share/locale/ca/LC_MESSAGES/python-fedora.mo from install of python2-fedora-0.10.0-5.fc29.noarch conflicts with file from package python3-fedora-0.10.0-3.fc28.noarch
  file /usr/share/locale/cs/LC_MESSAGES/python-fedora.mo from install of python2-fedora-0.10.0-5.fc29.noarch conflicts with file from package python3-fedora-0.10.0-3.fc28.noarch
  file /usr/share/locale/da/LC_MESSAGES/python-fedora.mo from install of python2-fedora-0.10.0-5.fc29.noarch conflicts with file from package python3-fedora-0.10.0-3.fc28.noarch
  file /usr/share/locale/de/LC_MESSAGES/python-fedora.mo from install of python2-fedora-0.10.0-5.fc29.noarch conflicts with file from package python3-fedora-0.10.0-3.fc28.noarch
  file /usr/share/locale/el_GR/LC_MESSAGES/python-fedora.mo from install of python2-fedora-0.10.0-5.fc29.noarch conflicts with file from package python3-fedora-0.10.0-3.fc28.noarch
  file /usr/share/locale/es/LC_MESSAGES/python-fedora.mo from install of python2-fedora-0.10.0-5.fc29.noarch conflicts with file from package python3-fedora-0.10.0-3.fc28.noarch
  file /usr/share/locale/fr/LC_MESSAGES/python-fedora.mo from install of python2-fedora-0.10.0-5.fc29.noarch conflicts with file from package python3-fedora-0.10.0-3.fc28.noarch
  file /usr/share/locale/hu/LC_MESSAGES/python-fedora.mo from install of python2-fedora-0.10.0-5.fc29.noarch conflicts with file from package python3-fedora-0.10.0-3.fc28.noarch
  file /usr/share/locale/it/LC_MESSAGES/python-fedora.mo from install of python2-fedora-0.10.0-5.fc29.noarch conflicts with file from package python3-fedora-0.10.0-3.fc28.noarch
  file /usr/share/locale/ja/LC_MESSAGES/python-fedora.mo from install of python2-fedora-0.10.0-5.fc29.noarch conflicts with file from package python3-fedora-0.10.0-3.fc28.noarch
  file /usr/share/locale/nl/LC_MESSAGES/python-fedora.mo from install of python2-fedora-0.10.0-5.fc29.noarch conflicts with file from package python3-fedora-0.10.0-3.fc28.noarch
  file /usr/share/locale/pl/LC_MESSAGES/python-fedora.mo from install of python2-fedora-0.10.0-5.fc29.noarch conflicts with file from package python3-fedora-0.10.0-3.fc28.noarch
  file /usr/share/locale/pt/LC_MESSAGES/python-fedora.mo from install of python2-fedora-0.10.0-5.fc29.noarch conflicts with file from package python3-fedora-0.10.0-3.fc28.noarch
  file /usr/share/locale/pt_BR/LC_MESSAGES/python-fedora.mo from install of python2-fedora-0.10.0-5.fc29.noarch conflicts with file from package python3-fedora-0.10.0-3.fc28.noarch
  file /usr/share/locale/ru/LC_MESSAGES/python-fedora.mo from install of python2-fedora-0.10.0-5.fc29.noarch conflicts with file from package python3-fedora-0.10.0-3.fc28.noarch
  file /usr/share/locale/sv/LC_MESSAGES/python-fedora.mo from install of python2-fedora-0.10.0-5.fc29.noarch conflicts with file from package python3-fedora-0.10.0-3.fc28.noarch
  file /usr/share/locale/th/LC_MESSAGES/python-fedora.mo from install of python2-fedora-0.10.0-5.fc29.noarch conflicts with file from package python3-fedora-0.10.0-3.fc28.noarch
  file /usr/share/locale/tr/LC_MESSAGES/python-fedora.mo from install of python2-fedora-0.10.0-5.fc29.noarch conflicts with file from package python3-fedora-0.10.0-3.fc28.noarch
  file /usr/share/locale/uk/LC_MESSAGES/python-fedora.mo from install of python2-fedora-0.10.0-5.fc29.noarch conflicts with file from package python3-fedora-0.10.0-3.fc28.noarch
  file /usr/share/locale/zh_CN/LC_MESSAGES/python-fedora.mo from install of python2-fedora-0.10.0-5.fc29.noarch conflicts with file from package python3-fedora-0.10.0-3.fc28.noarch
  file /usr/share/locale/zh_TW/LC_MESSAGES/python-fedora.mo from install of python2-fedora-0.10.0-5.fc29.noarch conflicts with file from package python3-fedora-0.10.0-3.fc28.noarch

Error Summary
-------------

Expected results:
Clear update path without any conflict.

Comment 1 Miro Hrončok 2018-07-20 12:59:32 UTC
Since both python2-fedora and python3-fedora lsit the same lang files, explicit conflicts need to be added:



%package -n python2-fedora
Conflicts: python3-fedora < %{version}-%{release}


%package -n python3-fedora
Conflicts: python2-fedora < %{version}-%{release}


I also suggest not to have those files in both packages, as it is very fragile and against the guidelines.

https://fedoraproject.org/wiki/Packaging:Guidelines#Duplicate_Files

Comment 2 Miro Hrončok 2018-07-20 13:04:32 UTC
s/lsit/list/

Comment 3 Kevin Fenzi 2018-07-22 19:55:24 UTC
Odd. I am not seeing this here?

✗ rpm -q python2-fedora python3-fedora                                                         
python2-fedora-0.10.0-5.fc29.noarch
python3-fedora-0.10.0-5.fc29.noarch

Your python3-fedora in the above output is 'python3-fedora-0.10.0-3.fc28.noarch' ?

Do you have something excluded somewhere? Can you try updating them at the same time to the same version?

Comment 4 Jakub Čajka 2018-07-23 09:57:48 UTC
Host that this is happening is rawhide probably since the time of f27 although regularly updated.

Yes I'm updating them both at the same time have same result. Allowerasing best or x doesn't help as it end in the same conflict or leads to removal of "half of distro".

Comment 5 Jakub Čajka 2018-07-23 10:09:09 UTC
For the record "dnf update" on the fedora:rawhide container have:
Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
 python3                                                     x86_64                                 3.7.0-3.fc29                                                     rawhide                                  40 k
 python3-libs                                                x86_64                                 3.7.0-3.fc29                                                     rawhide                                 8.0 M

I haven't seen this issue there.

Comment 6 Kevin Fenzi 2018-07-23 17:45:05 UTC
Well, the report in comment1 shows them as different versions... 

can you provide the output of just: 

dnf update python2-fedora python3-fedora

and 

rpm -q python2-fedora python3-fedora 

?

Comment 7 Jan Kurik 2018-08-14 11:04:06 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.

Comment 8 Zbigniew Jędrzejewski-Szmek 2018-08-28 12:49:07 UTC
*** Bug 1608068 has been marked as a duplicate of this bug. ***

Comment 9 Zbigniew Jędrzejewski-Szmek 2018-08-28 12:53:25 UTC
I'm getting the same traceback from dnf.

Comment 10 Zbigniew Jędrzejewski-Szmek 2018-08-28 14:12:00 UTC
It turns out that in my case the initial problem was caused by unupgradeable python3-moose package (see the bug linked in see-also). But there can be other causes, for example external packages or packages that were not rebuilt for F29 and so on. Current situation where the conflict is detected during transaction is very bad user experience. If python{2,3}-fedora cannot be made installable in different versions, then they should have Conflicts as suggested in comment #c1.

Comment 11 Ben Cotton 2019-10-31 20:43:13 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 12 Miro Hrončok 2019-10-31 22:36:21 UTC
This has been fixed on rawhide by removing python2-fedora. However still valid bug up until f31.

Comment 13 Adam Williamson 2020-01-28 15:17:51 UTC
It has not been 'fixed' on Rawhide either, because there is no Obsoletes: python2-fedora anywhere. This means you still cannot upgrade a system with python2-fedora installed unless --allowerasing is using. An explicit Obsoletes: needs to be added to python3-fedora or fedora-obsolete-packages.

Comment 14 Fedora Update System 2020-11-03 14:17:16 UTC
FEDORA-2020-0ddf0c668b has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-0ddf0c668b

Comment 15 Fedora Update System 2020-11-03 14:17:40 UTC
FEDORA-2020-265e46f745 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-265e46f745

Comment 16 Ben Cotton 2020-11-03 16:50:53 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 17 Fedora Update System 2020-11-04 02:46:09 UTC
FEDORA-2020-0ddf0c668b has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-0ddf0c668b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-0ddf0c668b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 18 Fedora Update System 2020-11-04 03:00:30 UTC
FEDORA-2020-265e46f745 has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-265e46f745`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-265e46f745

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 19 Fedora Update System 2020-11-06 01:14:50 UTC
FEDORA-2020-265e46f745 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 20 Fedora Update System 2020-11-10 01:29:38 UTC
FEDORA-2020-0ddf0c668b has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 21 Miro Hrončok 2020-11-17 17:09:47 UTC
The update introduced a regression: bz1898498.

And the Fedora 31 problem was not actually fixed (I think that's fine at this point).

Comment 22 Tomáš Hozza 2020-12-01 18:51:06 UTC
This change just unfortunately broke system upgrade from F31 to F32 - Please see bug #1903289

Comment 23 Miro Hrončok 2020-12-01 20:25:56 UTC
Yes, that's what I said one comment above.

Comment 24 Tomáš Hozza 2020-12-01 20:40:58 UTC
(In reply to Miro Hrončok from comment #23)
> Yes, that's what I said one comment above.

Your comment is about the issue not being fixed in F31, while mine is about the issue being present in F32 repos. So no...

Comment 25 Miro Hrončok 2020-12-01 20:55:00 UTC
"The update introduced a regression: bz1898498" is the fist sentence of my comment.

Comment 26 Miro Hrončok 2020-12-01 21:08:16 UTC
s/fist/first/

Comment 27 Tomáš Hozza 2020-12-02 08:36:15 UTC
(In reply to Miro Hrončok from comment #25)
> "The update introduced a regression: bz1898498" is the fist sentence of my
> comment.

Fair enough ;)


Note You need to log in before you can comment on or make changes to this bug.