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.
A rebase of udisks2 will pick up a great deal of work on modularity and stability, including the work done under the storaged fork.
AFAIK this rebase would enable the cockpit team to drop the cockpit-storaged package.
New dependencies: libblockdev (in fedora since F18 or so, used by blivet/anaconda since then)
(new) udisks2 upstream: https://github.com/storaged-project/udisks/
libblockdev upstream: https://github.com/storaged-project/libblockdev/
Comment 11Yaakov Selkowitz
2017-12-19 15:26:36 UTC
(In reply to Sandro Bonazzola from comment #10)
> Moving back to assigned and failing QE again.
How so exactly?
> changing the package which was requiring storaged doesn't fix a wrong spec
> file in udisks2.
It does, because...
> Please see
> https://fedoraproject.org/wiki/Packaging:Guidelines#Renaming.
> 2FReplacing_Existing_Packages
Which explicitly says:
"If a package supersedes/replaces an existing package without being a sufficiently compatible replacement as defined above, use only the Obsoletes: line from the above example."
I believe this is such a case.
Comment 12Sandro Bonazzola
2017-12-21 08:45:50 UTC
(In reply to Yaakov Selkowitz from comment #11)
> "If a package supersedes/replaces an existing package without being a
> sufficiently compatible replacement as defined above, use only the
> Obsoletes: line from the above example."
>
> I believe this is such a case.
Ok, fir enough, moving back to QE
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-2018:0868