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:
One patch of libmspack is being fully applied.
Version-Release number of selected component (if applicable):
0.7-0.1.alpha.el8.3
Additional info:
The backported version of upstream commit 8759da8db6ec9e866cb8eb143313f397f925bb4f
is not being fully applied on RHEL8's libmspack version.
Comment 2Richard W.M. Jones
2019-08-02 07:59:29 UTC
I see what's happening here. The patches were cherry picked (by me) in the
wrong order.
The order that I cherry picked them was:
commit date
c04c748cc922561d4461b2929cbf1b3c1ccd42a3 Wed Oct 17 11:33:35 2018 +0100
a68e54542c6f83eb2ee95a88482badbf36840049 Wed Oct 17 11:29:03 2018 +0100
86cca984516664267a3f783dcdf84ac918494a02 Sat May 12 10:51:34 2018 +0100
but in fact they should have been cherry picked in the reverse order.
Comment 3Richard W.M. Jones
2019-08-02 08:39:06 UTC
Sorry the commit hashes in the previous message referred to my cherry-picked
commits. The upstream hashes are:
commit date
40ef1b4093d77ad3a5cfcee1f5cb6108b3a3bcc2 Wed Oct 17 11:33:35 2018 +0100
8759da8db6ec9e866cb8eb143313f397f925bb4f Wed Oct 17 11:29:03 2018 +0100
72e70a921f0f07fee748aec2274b30784e1d312a Sat May 12 10:51:34 2018 +0100
Comment 4Richard W.M. Jones
2019-08-02 08:59:53 UTC
I've done the change locally but need PM and QA ACKs before I can push it.
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/RHSA-2020:1686