Bug 1598717 - deepin-system-monitor-1.5.2 is available
Summary: deepin-system-monitor-1.5.2 is available
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: deepin-system-monitor
Version: 28
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: sensor.wen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-06 09:54 UTC by Artem
Modified: 2019-05-28 19:00 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-28 19:00:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Artem 2018-07-06 09:54:06 UTC
Description of problem:
Installation of 'deepin-system-monitor' not possible in Fedora 28 due package conflicts.

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

How reproducible:
Try install 'deepin-system-monitor' package.

Steps to Reproduce:
1. sudo dnf install deepin-system-monitor

Actual results:
Problem: conflicting requests
  - nothing provides libprocps.so.4()(64bit) needed by deepin-system-monitor-1.3.7-3.fc28.x86_64

Expected results:
Succeful installation of 'deepin-system-monitor'.

Comment 1 sensor.wen 2018-08-27 11:16:32 UTC
https://copr.fedorainfracloud.org/coprs/mosquito/deepin/build/784184/

Is it working right now? I haven't updated it in F28. I am working on rawhide, F28 will be update later.

Comment 2 Artem 2018-08-27 11:54:04 UTC
Doesn't work in F28. Same issue.

Comment 3 Random User 2018-09-30 17:59:40 UTC
As I'm trying to install Veyon computer monitoring from https://veyon.io (current version veyon-4.1.2.fc27.x86_64.rpm), I have found that it is affected by the same bug, with exactly identical results--nothing provides libprocps.so.4()(64bit). libprocps.so.4 is provided by procps-ng which is confirmed as installed. I tried deepin-system-monitor and have the same error.

That said, it would seem to be less about deepin-system-monitor and more about the component (procps-ng) not being properly registered and/or recognized by the system. Whether one does dnf install or rpm -ivh, the installation fails the same way.
=====================
dnf install veyon-4.1.2.fc27.x86_64.rpm 

Error: 
 Problem: conflicting requests
  - nothing provides libprocps.so.4()(64bit) needed by veyon-4.1.2-1.x86_64
=====================
rpm -ivh veyon-4.1.2.fc27.x86_64.rpm 
error: Failed dependencies:
	libprocps.so.4()(64bit) is needed by veyon-4.1.2-1.x86_64
	libprocps.so.4(LIBPROCPS_0)(64bit) is needed by veyon-4.1.2-1.x86_64
=====================

Comment 4 Random User 2018-09-30 22:32:11 UTC
(In reply to Random User from comment #3)
> As I'm trying to install Veyon computer monitoring from https://veyon.io
> (current version veyon-4.1.2.fc27.x86_64.rpm), I have found that it is
> affected by the same bug, with exactly identical results--nothing provides
> libprocps.so.4()(64bit). libprocps.so.4 is provided by procps-ng which is
> confirmed as installed. I tried deepin-system-monitor and have the same
> error.
> 
> That said, it would seem to be less about deepin-system-monitor and more
> about the component (procps-ng) not being properly registered and/or
> recognized by the system. Whether one does dnf install or rpm -ivh, the
> installation fails the same way.
> =====================
> dnf install veyon-4.1.2.fc27.x86_64.rpm 
> 
> Error: 
>  Problem: conflicting requests
>   - nothing provides libprocps.so.4()(64bit) needed by veyon-4.1.2-1.x86_64
> =====================
> rpm -ivh veyon-4.1.2.fc27.x86_64.rpm 
> error: Failed dependencies:
> 	libprocps.so.4()(64bit) is needed by veyon-4.1.2-1.x86_64
> 	libprocps.so.4(LIBPROCPS_0)(64bit) is needed by veyon-4.1.2-1.x86_64
> =====================

Following up to my own comment ... this is 64-bit Fedora 28.

Comment 5 Ben Cotton 2019-05-02 19:22:04 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 6 Ben Cotton 2019-05-02 20:46:40 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 7 Upstream Release Monitoring 2019-05-23 07:03:19 UTC
Latest upstream release: 1.5.1 Current version/release in rawhide: 1.4.8.1-1.fc30 URL: https://github.com/linuxdeepin/deepin-system-monitor Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoringPlease keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.Based on the information from anitya: https://release-monitoring.org/project/18873/

Comment 8 Upstream Release Monitoring 2019-05-23 07:03:20 UTC
Skipping the scratch build because an SRPM could not be built: ['git', 'clone', 'https://src.fedoraproject.org/cgit/rpms/deepin-system-monitor.git', '/var/tmp/thn-w2gv5gm9'] returned 128: b"Cloning into '/var/tmp/thn-w2gv5gm9'...\nfatal: repository 'https://src.fedoraproject.org/cgit/rpms/deepin-system-monitor.git/' not found\n"

Comment 9 Upstream Release Monitoring 2019-05-23 11:01:47 UTC
Latest upstream release: 1.5.2 Current version/release in rawhide: 1.4.8.1-1.fc30 URL: https://github.com/linuxdeepin/deepin-system-monitor Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoringPlease keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.Based on the information from anitya: https://release-monitoring.org/project/18873/

Comment 10 Upstream Release Monitoring 2019-05-23 11:01:48 UTC
Skipping the scratch build because an SRPM could not be built: ['git', 'clone', 'https://src.fedoraproject.org/cgit/rpms/deepin-system-monitor.git', '/var/tmp/thn-1mi_rish'] returned 128: b"Cloning into '/var/tmp/thn-1mi_rish'...\nfatal: repository 'https://src.fedoraproject.org/cgit/rpms/deepin-system-monitor.git/' not found\n"

Comment 11 Ben Cotton 2019-05-28 19:00:32 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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