Hide Forgot
Description of problem: rubygem-virt-p2v is only available in the i686 repository for F16, not in x86_64 (or any other one)
I comment in the spec file indicates that this is intentional: http://pkgs.fedoraproject.org/gitweb/?p=rubygem-virt-p2v.git;a=blob;f=rubygem-virt-p2v.spec;h=f21580503e28bdc6e344865fd3709575d922dd7c;hb=HEAD # We only build virt-p2v for i686 as we need it to run on the widest possible # set of hardware from a single boot image. ExclusiveArch: i686 However I agree that if the i686 package doesn't appear in the yum repos on an x86_64 machine, that's a problem, because most users will not be able to use it to build the (32 bit) p2v ISO.
However, the virt-p2v-image-builder (created from this package) is also only available in 32bit repos even though it can run on an x86_64 install (it simply pulls down the 32bit repo packages as it builds). I know this is more of a limitation of Koji in that it doesn't support (AFAIK from my use) cherry-picking a single output RPM for a different tag. This took me a while to figure out why I couldn't find the image builder package, eventually I found it and installed it from the 32bit repo.
This package has many issues. :-( Even after installing from the 32-bit repo, it won't run due to the same error in 819672. After downgrading pykickstart as described, it still fails because it wants ruby 1.8, not 1.9. The src RPM rubygem-virt-p2v-0.8.3-2.fc17.src.rpm cannot be built on F17 because it depends on ruby 1.8. The rpm was obviously not rebuilt after the ruby 1.9 upgrade went in otherwise the failure would have been detected. Since the boot image is hardwired to 32-bit, I do not understand the need for the restriction for 686 only in the spec file.
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.