Bug 2170463 - update libproc dependency
Summary: update libproc dependency
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: lxqt-session
Version: 39
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 2170465
TreeView+ depends on / blocked
 
Reported: 2023-02-16 12:47 UTC by Jan Rybar
Modified: 2024-11-27 21:04 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-11-27 21:04:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jan Rybar 2023-02-16 12:47:22 UTC
Description of problem:
FTBFS
procps-ng changed its library, including ABI and filename.
former /usr/lib64/libprocps.so
chaged to /usr/lib64/libproc2.so

New procps-ng-4.0.2 is not in rawhide compose yet.
A copr build has been created for the purpose of work on this update.

https://copr.fedorainfracloud.org/coprs/jrybar/procps-ng-4.0.2_rebase/

Please let me know when your work is finished, so we can set up a side-tag for a bodhi update.

Thank you.

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


How reproducible:
always during build with procps-ng-4.0.x

Actual results:
build fails on dependency 'libprocps'

Expected results:
build succeeds with depenency 'libproc2'

Additional info:

Comment 1 Zamir SUN 2023-02-16 13:38:40 UTC
Upstream support for procps-ng-4.0.x not merged yet.
https://github.com/lxqt/lxqt-session/pull/456/commits/0d16e9e007794320b219eb4bf002fc38a45f107b

I believe I'm ready for the update.
https://copr.fedorainfracloud.org/coprs/zsun/procps-ng-4.0.2/build/5533822/

In my copr build, x86_64 and ppc64le already succeed. Failure on aarch64 is caused by repo error so it should be fine later when we start the actual work. Build for s390x did not start yet, but I don't think there are people running desktop environments on a mainframe s390x, so I consider it good to go.

Comment 2 Jan Rybar 2023-05-31 18:06:44 UTC
Hello, 

Finally, I created another side-tag for the newest upstream release of procps-ng-4.0.3: 
f39-build-side-68440

Please, feel free to build your package within the side-tag. 
The Bodhi update deploying the new procps-ng and all dependent packages will be created on **June 16**.

Thanks! And sorry for the delay.

Comment 3 Fedora Release Engineering 2023-08-16 07:07:07 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

Comment 4 Aoife Moloney 2024-11-08 10:46:31 UTC
This message is a reminder that Fedora Linux 39 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-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
'version' of '39'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 39 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 5 Aoife Moloney 2024-11-27 21:04:52 UTC
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26.

Fedora Linux 39 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

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.