Hide Forgot
Description of problem: grub2-mkrescue requires xorriso Version-Release number of selected component (if applicable): 1.99 How reproducible: Always Steps to Reproduce: 1. grub2-mkrescue -o test.img 2. 3. Actual results: Enabling BIOS support ... /usr/bin/grub2-mkrescue: line 310: xorriso: command not found Expected results: grub2-mkrescue -o test.img Enabling BIOS support ... xorriso 1.1.8 : RockRidge filesystem manipulator, libburnia project. Drive current: -outdev 'stdio:test.img' Media current: stdio file, overwriteable Media status : is blank Media summary: 0 sessions, 0 data blocks, 0 data, 31.9g free Added to ISO image: directory '/'='/tmp/tmp.FwTqI0iWEJ' xorriso : UPDATE : 196 files added in 1 seconds xorriso : UPDATE : 196 files added in 1 seconds xorriso : NOTE : Copying to System Area: 31750 bytes from file '/tmp/tmp.VKoWqXhxO1' xorriso : UPDATE : 100.00% done ISO image produced: 1114 sectors Written to medium : 1114 sectors at LBA 0 Writing to 'stdio:test.img' completed successfully. Additional info: 0) Installing xorriso (1.1.8-1.fc16) fixes this. (Installing xorriso will currently also pull in libisoburn (1.1.8-1.fc16) and, oddly, kde-filesystem (4-38.fc15).) 1) Running info grub2 "Invoking grub2-mkrescue" will show `--xorriso=FILE' Use FILE as the `xorriso' program, rather than the built-in default. That fragment is a bit confusing, since xorriso is not a grub2 builtin. 2) Usage of xorriso was new in 1.99, see https://bugzilla.redhat.com/show_bug.cgi?id=670323#c8 .
xorriso is not installed by default, so it would be unfortunate if it became a hard dependency for grub2-efi when used on live images. 0.5 MB is not much, but it might be too much to be worth it. The error message when xorriso is missing seems to be reasonable, so it might be reasonable to keep it the way it is and consider xorriso an optional dependency for grub2. Creating a separate subpackage for grub2-mkrescue would also be overkill.
(In reply to comment #1) > The error message when xorriso is missing seems to be reasonable, so it might > be reasonable to keep it the way it is and consider xorriso an optional > dependency for grub2. Do rpm or yum have the idea of "optional" dependencies? Anyhow, does anyone have a pointer to Fedora's packaging guidelines (or something of that nature)?
(In reply to comment #2) > Do rpm or yum have the idea of "optional" dependencies? No; that was an euphemism. What I meant was to accept the behaviour you describe: if xorriso is installed then it works, and if it isn't installed it fails with a reasonable error message. (In some places PackageKit is used to install stuff on demand, but that is far too heavy handed for this purpose.)
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.