Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rear2.3 asking for :genisoimage for RHEL 5.8 #1837

Closed
nirmal21s opened this issue Jun 21, 2018 · 10 comments
Closed

Rear2.3 asking for :genisoimage for RHEL 5.8 #1837

nirmal21s opened this issue Jun 21, 2018 · 10 comments

Comments

@nirmal21s
Copy link

nirmal21s commented Jun 21, 2018

Relax-and-Recover (ReaR) Issue Template

Fill in the following items before submitting a new issue
(quick response is not guaranteed with free support):

  • ReaR version ("/usr/sbin/rear -V"): 2.3

  • OS version ("cat /etc/rear/os.conf" or "lsb_release -a" or "cat /etc/os-release"):RHEL 5.8
    Arch : i686

  • Brief description of the issue:
    When trying to install the REAR 2.3 rpm for RHEL 5 its not getting installed .
    It requires Genisoimage.
    There is no package genisoimage available for RH5.
    Is there any workaround available to make it work.

geniso_error.txt

excerpts:

yum install rear-2.3-185.git.0.d642b65.unknown.el5.i386.rpm 
...
Error: Missing Dependency: genisoimage is needed by package rear-2.3-185.git.0.d642b65.unknown.el5.i386 (/rear-2.3-185.git.0.d642b65.unknown.el5.i386)
 You could try using --skip-broken to work around the problem
@jsmeix
Copy link
Member

jsmeix commented Jun 21, 2018

I am not a RHEL user but I would ignore that yum error
(i.e. force yum to install it nevertheless).

What you need is a 'genisoimage' compatible program
on your RHEL system installed but it does not matter
from which RPM package name it comes.

A 'genisoimage' compatible program is ususually called during
"rear mkrescue/mkbackup" when the ReaR recovery system
ISO image is made (i.e in case of OUTPUT=ISO).

You can specify your particular 'genisoimage' compatible program
via ISO_MKISOFS_BIN (see its description in default.conf).

@jsmeix jsmeix added the minor bug An alternative or workaround exists label Jun 21, 2018
@jsmeix jsmeix added this to the ReaR future milestone Jun 21, 2018
@jsmeix
Copy link
Member

jsmeix commented Jun 21, 2018

Since
#1192
and its
a3bf4b6
there is in
https://github.com/rear/rear/blob/master/packaging/rpm/rear.spec

### On RHEL/Fedora the genisoimage packages provides mkisofs
%if %{?centos_version:1}%{?fedora:1}%{?rhel_version:1}0
Requires: crontabs
Requires: iproute
#Requires: mkisofs
Requires: genisoimage
#Requires: redhat-lsb
%endif

which is probably incompatible with RHEL5.

@jsmeix
Copy link
Member

jsmeix commented Jun 21, 2018

@nirmal21s
what is the RPM package name on RHEL5
that provides the 'genisoimage' compatible program?

From the above rear.spec excerpt I guess in RHEL5
the 'genisoimage' compatible program is 'mkisofs'
and its RPM package name is also 'mkisofs'
but we need to be sure what there actually is on RHEL5
(I assume no ReaR developer still uses that somewhat old system).

@gdha
Copy link
Member

gdha commented Jun 21, 2018

@nirmal21s @jsmeix Indeed in RHEL5 it was mkisofs that was required.
To get rear installed on RHEL5 do not use yum, but first download (using wget) the rpm and then use the command:

rpm -Uvh --nodeps rear-2.3-185.git.0.d642b65.unknown.el5.i386.rpm

@gdha gdha added support / question and removed minor bug An alternative or workaround exists labels Jun 21, 2018
@gdha
Copy link
Member

gdha commented Jun 21, 2018

A last comment about RHEL5 - it is unsupported by RedHat since March 2017, so do not expect any fixes in our rear.spec file for it anymore. You can still use the latest rear version, but you need to install it via the work-around given above.
Therefore, I remove the label 'minor bug' and replace it with 'support/question'

@jsmeix
Copy link
Member

jsmeix commented Jun 21, 2018

@gdha
but ReaR still supports RHEL5 because current
https://github.com/rear/rear/blob/master/doc/rear-release-notes.txt
reads (excerpts):

ReaR-2.4 is supported on the following Linux based operating systems:
...
* RHEL 5, 6 and 7
...
ReaR-2.4 dropped officially support for the following Linux based operating systems:
...
* RHEL 3 and 4

Perhaps we should drop official support for RHEL 5 in Rear 2.4?

@gdha
Copy link
Member

gdha commented Jun 21, 2018

@jsmeix We will kick it out in ReaR 2.5 as it is still usable with the work-around to given above. We can add it in the release notes (as an add-on).

@jsmeix
Copy link
Member

jsmeix commented Jun 21, 2018

@gdha
anything about RHEL is o.k. for me
(because I am not a RHEL user ;-)

FYI:
I had dropped official support for SLES 10 ReaR 1.17
regardless that even current ReaR should still work with it
because I do not want to get "officially blamed" in any way
if by some change ReaR may no longer work with SLES10, cf.
#1765 (comment)

@jsmeix
Copy link
Member

jsmeix commented Jun 21, 2018

I assume with
#1837 (comment)
this issue can be considered as sufficiently "fixed/solved/done".

@nirmal21s
Copy link
Author

@gdha
I tried this option "rpm -Uvh --nodeps rear-2.3-185.git.0.d642b65.unknown.el5.i386.rpm"
It got installed and created ISO image.
But not yet tested.
Hope this works!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants