On Wed, 2008-03-05 at 14:11 -0600, Allen Rohner wrote:
%packages @base x86info postgresql-server python-sqlalchemy ruby ruby-irb rubygem-rails mod_python %end
Running with the rawhide repository gives the exact same error.
This is a very small package set, you need at least a kernel, the anaconda packages and a few other things. See the 'compose needs' section on the shipped kickstart file.
Right now, pungi doesn't separate the "things we need to compose" from "things we want in the compose" so you need to add those things into the manifest.
Thanks for the help. I'm able to get farther now. It doesn't really make sense to me why the list is the way it is. Is that truly the minimal set of packages? Why do we need iscsi-initiator-utils and vncserver to build a working ISO? This process would be significantly easier if the (true) minimum set of packages was documented somewhere, or even better, if pungi warned that you are missing packages X,Y,Z necessary to get a working build. I would offer to make a patch, but I don't know what the set is.
Allen Rohner
On Wed, 2008-03-05 at 18:13 -0600, Allen Rohner wrote:
Thanks for the help. I'm able to get farther now. It doesn't really make sense to me why the list is the way it is. Is that truly the minimal set of packages? Why do we need iscsi-initiator-utils and vncserver to build a working ISO? This process would be significantly easier if the (true) minimum set of packages was documented somewhere, or even better, if pungi warned that you are missing packages X,Y,Z necessary to get a working build. I would offer to make a patch, but I don't know what the set is.
That depends on if you want to install to iscsi, or support vnc installs. Again, because pungi doesn't split out what you need to compose the install media vs what you have as install choices on the media, the media can get a bit bloaty. I just haven't come up with a good way of expressing one vs the other.
On Wed, 2008-03-05 at 20:49 -0500, Jesse Keating wrote:
On Wed, 2008-03-05 at 18:13 -0600, Allen Rohner wrote:
Thanks for the help. I'm able to get farther now. It doesn't really make sense to me why the list is the way it is. Is that truly the minimal set of packages? Why do we need iscsi-initiator-utils and vncserver to build a working ISO? This process would be significantly easier if the (true) minimum set of packages was documented somewhere, or even better, if pungi warned that you are missing packages X,Y,Z necessary to get a working build. I would offer to make a patch, but I don't know what the set is.
That depends on if you want to install to iscsi, or support vnc installs. Again, because pungi doesn't split out what you need to compose the install media vs what you have as install choices on the media, the media can get a bit bloaty. I just haven't come up with a good way of expressing one vs the other.
One way might be to use the support that now exists in buildinstall to point at a repository. Then you could be running buildinstall against the repository you're pulling from and then your pungi'd tree would just have the packages you care about
Jeremy
On Wed, 2008-03-05 at 21:05 -0500, Jeremy Katz wrote:
One way might be to use the support that now exists in buildinstall to point at a repository. Then you could be running buildinstall against the repository you're pulling from and then your pungi'd tree would just have the packages you care about
Yes, that definitely needs some testing. I'm thinking post-f9 though.
buildsys@lists.fedoraproject.org
-
Allen Rohner -
Jeremy Katz -
Jesse Keating -
Jesse Keating