Bug 2056646 - non needed dependencies set in s390x package
Summary: non needed dependencies set in s390x package
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: rear
Version: 9.0
Hardware: s390x
OS: Linux
unspecified
low
Target Milestone: rc
: 9.0
Assignee: Pavel Cahyna
QA Contact: David Jež
URL:
Whiteboard:
Depends On: 2032266
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-21 17:17 UTC by Pavel Cahyna
Modified: 2022-05-17 14:18 UTC (History)
5 users (show)

Fixed In Version: rear-2.6-11.el9
Doc Type: No Doc Update
Doc Text:
Clone Of: 2032266
Environment:
Last Closed: 2022-05-17 14:17:50 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-112943 0 None None None 2022-02-21 17:30:11 UTC
Red Hat Product Errata RHBA-2022:2691 0 None Waiting on Customer container macvlan communication not working if VMs located on same compute node 2022-06-15 12:45:41 UTC

Description Pavel Cahyna 2022-02-21 17:17:25 UTC
+++ This bug was initially created as a clone of Bug #2032266 +++

It appears that for s390x, creating iso is not possible (or optionnal ?), but the following dependencies are set none the less in the rear package:

   libburn
   libisoburn
   libisofs
   xorriso or genisoimage

Would it be possible not to have those set in the final rear package ?

--- Additional comment from Pavel Cahyna on 2021-12-14 09:58:20 UTC ---

Thanks for the report, I will have a look at addressing this in the next update. In the long term though I believe creating ISOs might be actually useful on S/390x (for booting LPARs). What do you think? Would that be an useful feature to add?

--- Additional comment from Pierre Amadio on 2021-12-17 10:14:39 UTC ---

i just spoke with the customer behind ticket#03104120.
Being able to create iso on s390x might be interesting (so he has an other way of installing things) but is not something he is currently formally requesting.

--- Additional comment from Pavel Cahyna on 2021-12-17 10:25:06 UTC ---

Thanks. Is the customer using ReaR on a LPAR?

Note that if we add the ability to create ISOs, those dependencies will stay on the package, because they will not be unneeded anymore. Would that be a problem?

--- Additional comment from Pierre Amadio on 2021-12-17 11:48:22 UTC ---

Yes, he is using Rear to backup/restore LPAR. 
Having the dependencies kept if they are actually used (in case a create iso features exist) is ok.

Comment 7 errata-xmlrpc 2022-05-17 14:17:50 UTC
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 (new packages: rear), 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-2022:2691


Note You need to log in before you can comment on or make changes to this bug.