I am building an auto install iso for some repeated, specialized deployments and I have run into a problem. I am building them with pungi and using the latest packages from fedora 11, but a bug in the 2.6.30 kernel seems to be preventing me from installing from cdrom. Anaconda fails to find the cdrom drive on the hardware I am using (IBM hs22 bladecenter). The problem is fixed by using a 2.6.29 kernel. So I was hoping that I could build my installer iso with pungi, and the updates repository, but exclude the latest kernel so a 2.6.29 kernel is used. Is this possible without maintaining a modified local copy of the updates repository?
-Tom Hatch
On 09/23/2009 10:24 PM, Thomas S Hatch wrote:
I am building an auto install iso for some repeated, specialized deployments and I have run into a problem. I am building them with pungi and using the latest packages from fedora 11, but a bug in the 2.6.30 kernel seems to be preventing me from installing from cdrom. Anaconda fails to find the cdrom drive on the hardware I am using (IBM hs22 bladecenter). The problem is fixed by using a 2.6.29 kernel. So I was hoping that I could build my installer iso with pungi, and the updates repository, but exclude the latest kernel so a 2.6.29 kernel is used. Is this possible without maintaining a modified local copy of the updates repository?
Pungi does not support selecting exact package nevra in the %packages manifest of a kickstart, but Revisor does; use --kickstart-nevra
-- Jeroen
Thanks, I found another workaround for now, but if it comes up again I will look into revisor.
On Sat, Sep 26, 2009 at 3:47 PM, Julian Aloofi < julian.fedoralists@googlemail.com> wrote:
Am Samstag, den 26.09.2009, 23:26 +0200 schrieb Jeroen van Meeuwen:
Pungi does not support selecting exact package nevra in the %packages manifest of a kickstart, but Revisor does; use --kickstart-nevra
-- Jeroen
I guess you mean --kickstart-exact-nevra, or is this equivalent?
-- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
On 09/26/2009 11:47 PM, Julian Aloofi wrote:
Am Samstag, den 26.09.2009, 23:26 +0200 schrieb Jeroen van Meeuwen:
Pungi does not support selecting exact package nevra in the %packages manifest of a kickstart, but Revisor does; use --kickstart-nevra
I guess you mean --kickstart-exact-nevra, or is this equivalent?
Oops, yes, I mean --kickstart-exact-nevra.
-- Jeroen
buildsys@lists.fedoraproject.org