Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
rpmdiff found some problems with the recent release. Most notable are:
File usr/share/doc/e2fsprogs/RELEASE-NOTES became a dangling symlink (to doc/RelNotes/v1.44.6.txt) on all architectures
File usr/lib/libss.so.2.0 built-by changed from 'gcc 8.2.1 20180905' to 'gcc 8.3.1 20190507' on i686
Figure out what's going on and fix it.
-Lukas
Hi Eric, thanks I already spoke with security and they told me that they can't do anything. Waiting for the rpmdiff developers to do something about it.
-Lukas
Ok, Fabio Olive Leite seemed to be more willing in #security, I guess we'll see what happens to my request.
If it can't be waived then there is nothing we can do until rpmdiff is fixed for this and apparently other errata as well.
TEST PASS.
The only problem in e2fsprogs side is "File usr/share/doc/e2fsprogs/RELEASE-NOTES became a dangling symlink (to doc/RelNotes/v1.44.6.txt) on all architectures"
Reproduced with e2fsprogs-1.44.6-2.el8
---
[root@ci-vm-10-0-137-111 ~]# ls -l /usr/share/doc/e2fsprogs/RELEASE-NOTES
lrwxrwxrwx. 1 root root 24 Mar 5 15:11 /usr/share/doc/e2fsprogs/RELEASE-NOTES -> doc/RelNotes/v1.44.6.txt
[root@ci-vm-10-0-137-111 ~]# # dangling symlink here ^^^
[root@ci-vm-10-0-137-111 ~]# rpm -q e2fsprogs
e2fsprogs-1.44.6-2.el8.x86_64
---
Verified with e2fsprogs-1.44.6-3.el8
---
[root@ci-vm-10-0-137-135 ~]# ls /usr/share/doc/e2fsprogs/RELEASE-NOTES
ls: cannot access '/usr/share/doc/e2fsprogs/RELEASE-NOTES': No such file or directory
[root@ci-vm-10-0-137-135 ~]# rpm -q e2fsprogs
e2fsprogs-1.44.6-3.el8.x86_64
---
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2019:3581