Bug 2056646

Summary:	non needed dependencies set in s390x package
Product:	Red Hat Enterprise Linux 9	Reporter:	Pavel Cahyna <pcahyna>
Component:	rear	Assignee:	Pavel Cahyna <pcahyna>
Status:	CLOSED ERRATA	QA Contact:	David Jež <djez>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	djez, ovasik, pamadio, pcahyna, rhel-cs-system-management-subsystem-qe
Target Milestone:	rc	Keywords:	Triaged
Target Release:	9.0	Flags:	pm-rhel: mirror+
Hardware:	s390x
OS:	Linux
Whiteboard:
Fixed In Version:	rear-2.6-11.el9	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:	2032266	Environment:
Last Closed:	2022-05-17 14:17:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2032266
Bug Blocks:

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