Bug 1778004

Summary: python3-caja conflicts with python2-caja (nextcloud-client dependency)
Product: [Fedora] Fedora Reporter: Basil Mohamed Gohar <me>
Component: python-cajaAssignee: Wolfgang Ulbrich <raveit65.sun>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 30CC: patrick, raveit65.sun
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-29 03:38:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dnf upgrade output when upgrade includes both nextcloud-client-caja and python3-caja none

Description Basil Mohamed Gohar 2019-11-28 23:55:13 UTC
Created attachment 1640540 [details]
dnf upgrade output when upgrade includes both nextcloud-client-caja and python3-caja

Description of problem:
Cannot finish dnf upgrade due to conflicts between python3-caja and python2-caja

Version-Release number of selected component (if applicable):


How reproducible:
Every time

Steps to Reproduce:
1. Have nextcloud-client-caja installed previously
2. Attempt to do dnf-upgrade where python3-caja is going to be upgraded/installed
3. many files conflicting between python2-caja and python3-caja break the upgrade

Actual results:

Upgrade fails due to conflicting files

Expected results:

dnf upgrade works seamlessly

Additional info:

Output included in attachment

Comment 1 Patrick Monnerat 2019-11-29 01:40:32 UTC
python2-caja is not provided anymore since Fedora 29.
Your problem probably comes from and upgrade from Fedora <= 28 --> Fedora 30. Please confirm.

The easiest solution is to uninstall python2-caja and packages depending on it before upgrade, then reinstall the latter after the upgrade is successful.

Comment 2 Basil Mohamed Gohar 2019-11-29 03:38:22 UTC
(In reply to Patrick Monnerat from comment #1)
> python2-caja is not provided anymore since Fedora 29.
> Your problem probably comes from and upgrade from Fedora <= 28 --> Fedora
> 30. Please confirm.
> 
> The easiest solution is to uninstall python2-caja and packages depending on
> it before upgrade, then reinstall the latter after the upgrade is successful.

Your proposed fix worked for me, and your described scenario is a likely case.  I've marked the bug as "closed/notabug" for that reason.

Still not sure why this is only happening now, since I've run many updates in this version of Fedora.  Did python2-caja/python3-caja not get any updates this whole time?

Comment 3 Patrick Monnerat 2019-11-29 04:18:48 UTC
> Did python2-caja/python3-caja not get any updates this whole time?
Yes they did, but that's not the problem.

The real problem you had was:
- python2-caja was installed within a Fedora < 29 release. It remained installed without updates after you upgraded to Fedora >= 29.
- Until now, you did not have any problems because python3-caja was not needed.
- The nextcloud-client-caja update caused the problem, because version 2.6.1 requires the python3 version at last (See https://src.fedoraproject.org/rpms/nextcloud-client/c/4118141c95be136e5215ade9fceb84ed044e9955?branch=f30) :-( Both python-caja versions cannot be installed at the same time (conflicts, but also caja does not know which one to use!).

Thanks for your report.