Bug 1871467 - F34FailsToInstall: cpu-x
Summary: F34FailsToInstall: cpu-x
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: cpu-x
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Artem
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F34FailsToInstall
TreeView+ depends on / blocked
 
Reported: 2020-08-23 17:22 UTC by Igor Raits
Modified: 2020-09-25 16:57 UTC (History)
1 user (show)

Fixed In Version: cpu-x-4.0.1-4.fc34 cpu-x-4.0.1-5.fc33
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-02 08:57:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Igor Raits 2020-08-23 17:22:37 UTC
Hello,

Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (ignatenkobrain).

Your package (cpu-x) Fails To Install in Fedora 34:

can't install cpu-x:
  - nothing provides libprocps.so.7()(64bit) needed by cpu-x-4.0.1-3.fc33.x86_64
  - nothing provides libprocps.so.7(LIBPROCPS_0)(64bit) needed by cpu-x-4.0.1-3.fc33.x86_64
  
If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.


If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks.

P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors.

P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/rawhide-gating/multi-builds/

Thanks!

Comment 1 Igor Raits 2020-08-31 09:01:37 UTC
Hello,

This is the first reminder (step 3 from https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs).

If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.

Comment 2 Fedora Update System 2020-09-02 08:57:18 UTC
FEDORA-2020-89fe2fb4b7 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 3 Fedora Update System 2020-09-12 15:42:25 UTC
FEDORA-2020-e743c78aeb has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-e743c78aeb

Comment 4 Fedora Update System 2020-09-13 18:30:57 UTC
FEDORA-2020-e743c78aeb 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-e743c78aeb`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-e743c78aeb

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

Comment 5 Fedora Update System 2020-09-14 15:11:15 UTC
FEDORA-2020-7e858a52f3 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-7e858a52f3`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-7e858a52f3

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

Comment 6 Fedora Update System 2020-09-25 16:57:07 UTC
FEDORA-2020-7e858a52f3 has been pushed to the Fedora 33 stable repository.
If problem still persists, 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.