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 1829163 - packages with broken dependencies(package python2-appindicator-12.10.0-25.fc31.x86_64 requires libappindicator = 12.10.0-25.fc31, but none of the providers can be installed)
Summary: packages with broken dependencies(package python2-appindicator-12.10.0-25.fc3...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libappindicator
Version: 31
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Eduardo Echeverria
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-29 04:56 UTC by Donald O'Dona
Modified: 2020-06-11 18:57 UTC (History)
6 users (show)

Fixed In Version: libappindicator-12.10.0-29.fc31
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-04 05:47:23 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github funnelfiasco copr-cherrytree issues 5 0 None closed package conflict Fedora 31(libappindicator) 2020-06-16 06:22:57 UTC

Description Donald O'Dona 2020-04-29 04:56:29 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
libappindicator-12.10.0-28.fc31.x86_64 and libappindicator-12.10.0-25.fc31.x86_64

How reproducible:
.dnf upgrade

Steps to Reproduce:
1.dnf upgrade
2.
3.

Actual results:
Dependencies resolved.

 Problem: libappindicator-12.10.0-25.fc31.i686 has inferior architecture
  - package python2-appindicator-12.10.0-25.fc31.x86_64 requires libappindicator = 12.10.0-25.fc31, but none of the providers can be installed
  - cannot install both libappindicator-12.10.0-28.fc31.x86_64 and libappindicator-12.10.0-25.fc31.x86_64
  - cannot install both libappindicator-12.10.0-25.fc31.x86_64 and libappindicator-12.10.0-28.fc31.x86_64
  - cannot install the best update candidate for package python2-appindicator-12.10.0-25.fc31.x86_64
  - cannot install the best update candidate for package libappindicator-12.10.0-25.fc31.x86_64
====================================================================================================================================
 Package                            Architecture              Version                              Repository                  Size
====================================================================================================================================
Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
 libappindicator                    x86_64                    12.10.0-28.fc31                      updates                     42 k

Transaction Summary
====================================================================================================================================
Skip  1 Package


Expected results:
no problems

Additional info:
Comment 1 Donald O'Dona 2020-04-29 21:29:49 UTC 
hours and one kernel update later nothing changed:

ast metadata expiration check: 0:16:26 ago on Wed 29 Apr 2020 11:11:45 PM CEST.
Dependencies resolved.

 Problem: libappindicator-12.10.0-25.fc31.i686 has inferior architecture
  - package python2-appindicator-12.10.0-25.fc31.x86_64 requires libappindicator = 12.10.0-25.fc31, but none of the providers can be installed
  - cannot install both libappindicator-12.10.0-28.fc31.x86_64 and libappindicator-12.10.0-25.fc31.x86_64
  - cannot install both libappindicator-12.10.0-25.fc31.x86_64 and libappindicator-12.10.0-28.fc31.x86_64
  - cannot install the best update candidate for package python2-appindicator-12.10.0-25.fc31.x86_64
  - cannot install the best update candidate for package libappindicator-12.10.0-25.fc31.x86_64
====================================================================================================================================
 Package                            Architecture              Version                              Repository                  Size
====================================================================================================================================
Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
 libappindicator                    x86_64                    12.10.0-28.fc31                      updates                     42 k

Transaction Summary
====================================================================================================================================
Skip  1 Package

Nothing to do.
Complete!
Comment 2 Adam Williamson 2020-04-29 22:54:52 UTC 
Why are you expecting anything would have changed? No-one said they fixed anything.

Most likely the package was removed in a later libappindicator build, but nothing was set to obsolete it. This is a packaging error, but you should be able to work around it simply by removing python2-appindicator, if nothing is using it.
Comment 3 Donald O'Dona 2020-05-01 11:53:50 UTC 
t isn't that simple, because a dnf remove python2-appindicator would
remove dependent package  cherrytree(@copr:copr.fedorainfracloud.org:bcotton:cherrytree)
Comment 4 Ben Cotton 2020-05-01 17:09:00 UTC 
Helping with the cherrytree package in https://github.com/funnelfiasco/copr-cherrytree/issues/5

Looks like the python2-appindicator subpackage was removed:
https://src.fedoraproject.org/rpms/libappindicator/blob/f31/f/libappindicator.spec#_230

Given the presence of things like the Fedora 32 rebuild in the f31 package's changelog, it seems like some commits were backported that perhaps should not have been?
Comment 5 Adam Williamson 2020-05-01 17:15:41 UTC 
yeah, that's a good point, python2 package retirements shouldn't be backported to stable releases; if we released F31 with a python2 subpackage, it should be kept.

If Eduardo doesn't reply soon I'll fix this with provenpackager powers (put the python2 subpackage back).
Comment 6 Eduardo Echeverria 2020-05-02 14:56:23 UTC 
I'll put the python2 subpackage back today for F31 (it was an error merging it, and I included F31), sorry for not answer before, I was busy in my daily work
Comment 7 Donald O'Dona 2020-05-03 08:07:51 UTC 
in fedora 32 things became even worser. See https://bugzilla.redhat.com/show_bug.cgi?id=1830488
Comment 8 Eduardo Echeverria 2020-05-03 23:07:30 UTC 
(In reply to Donald O'Dona from comment #7)
> in fedora 32 things became even worser. See
> https://bugzilla.redhat.com/show_bug.cgi?id=1830488

Fedora 32 is not shipped by default with python2 and is the reason because it was removed the subpackage for python2, Donald. 
Because the Ccherrytree cope packages require python2-appindicator https://github.com/funnelfiasco/copr-cherrytree/blob/master/cherrytree.spec#L27 is failing, not due that in F32 should exist
Comment 9 Fedora Update System 2020-05-03 23:20:27 UTC 
FEDORA-2020-2266ef5b09 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-2266ef5b09
Comment 10 Fedora Update System 2020-05-04 06:58:20 UTC 
FEDORA-2020-2266ef5b09 has been pushed to the Fedora 31 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-2266ef5b09`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-2266ef5b09

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 11 Ben Cotton 2020-05-04 13:30:35 UTC 
Correcting the close status to reflect that we took action to fix it.
Comment 12 Fedora Update System 2020-06-11 18:57:27 UTC 
libappindicator-12.10.0-29.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.