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.
There are a lot of bugfixes and improvements. Also kinda needed for yum4 (one of next versions). Even we don't ship yum4 in RHEL7, we still try to make it simple to ship it in CentOS/EPEL.
Igor,
Could you please summarize, or provide a link to details, of the changes or impact of the rebase. We simply need to understand any negative impact to anything that might already be using libsolv.
(In reply to Terry Bowling from comment #1)
> Igor,
>
> Could you please summarize, or provide a link to details, of the changes or
> impact of the rebase. We simply need to understand any negative impact to
> anything that might already be using libsolv.https://github.com/openSUSE/libsolv/blob/master/NEWS
There were no breakages from current version, so nothing should break. Only new features and bugfixes.
⋊> ~/P/r/r/libsolv on rhel-7.5 ⨯ abipkgdiff libsolv-0.6.26-2.el7.x86_64.rpm libsolv-0.6.33-1.el7.x86_64.rpm --devel1 libsolv-devel-0.6.26-2.el7.x86_64.rpm --devel2 libsolv-devel-0.6.33-1.el7.x86_64.rpm --d1 libsolv-debuginfo-0.6.26-2.el7.x86_64.rpm --d2 libsolv-debuginfo-0.6.33-1.el7.x86_64.rpm
================ changes of 'libsolv.so.0'===============
Functions changes summary: 2 Removed, 1 Changed (69 filtered out), 5 Added functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
2 Removed functions:
'function void solver_disableproblem(Solver*, Id)' {solver_disableproblem@@SOLV_1.0}
'function void solver_enableproblem(Solver*, Id)' {solver_enableproblem@@SOLV_1.0}
5 Added functions:
'function void map_invertall(Map*)' {map_invertall@@SOLV_1.2}
'function void pool_best_solvables(Pool*, Queue*, int)' {pool_best_solvables@@SOLV_1.1}
'function void pool_set_whatprovides(Pool*, Id, Id)' {pool_set_whatprovides@@SOLV_1.2}
'function void selection_subtract(Pool*, Queue*, Queue*)' {selection_subtract@@SOLV_1.2}
'function void solver_get_cleandeps(Solver*, Queue*)' {solver_get_cleandeps@@SOLV_1.1}
1 function with some indirect sub-type change:
[C]'function void policy_filter_unwanted(Solver*, Queue*, int)' at policy.c:1312:1 has some indirect sub-type changes:
parameter 1 of type 'Solver*' has sub-type changes:
in pointed to type 'typedef Solver' at solver.h:214:1:
underlying type 'struct _Solver' at solver.h:29:1 changed:
type size hasn't changed
1 data member deletion:
'int _Solver::dupmap_all', at offset 7296 (in bits) at solver.h:171:1
3 data member insertions:
'Id _Solver::bestrules_up', at offset 1344 (in bits) at solver.h:71:1
'int _Solver::process_orphans', at offset 7136 (in bits) at solver.h:171:1
'int _Solver::dupinvolvedmap_all', at offset 7424 (in bits) at solver.h:174:1
6 data member changes (1 filtered):
'Id _Solver::bestrules_end' offset changed from 1344 to 1376 (in bits) (by +32 bits)
'Map _Solver::dupinvolvedmap' offset changed from 7360 to 7296 (in bits) (by -64 bits)
'int _Solver::dup_allowdowngrade' offset changed from 7488 to 7456 (in bits) (by -32 bits)
'int _Solver::dup_allownamechange' offset changed from 7520 to 7488 (in bits) (by -32 bits)
'int _Solver::dup_allowarchchange' offset changed from 7552 to 7520 (in bits) (by -32 bits)
'int _Solver::dup_allowvendorchange' offset changed from 7584 to 7552 (in bits) (by -32 bits)
================ end of changes of 'libsolv.so.0'===============
The removal of 2 symbols should not be a problem because they were not in any headers and no one could really use them.
Comment 5Valentina Mukhamedzhanova
2018-04-03 11:49:39 UTC
*** Bug 1561340 has been marked as a duplicate of this bug. ***
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/RHEA-2018:3234