The DVD's comps.xml does not include all the packages on the DVD.  19 are omitted, including anaconda-runtime, which causes buildinstall to fail (?). In any event, at "Building images...", upd-instroot, mk-images, and makestamp.py were missing, and later ".discinfo doesn't exist in the unified tree, not splitting".  Should those 19 packages have been in comps.xml?  Is there some way to add them to the process without writing a comps.xml?

A small question about pungi: Why used space in Volume name when build iso file ? Something like "%s-%s-%s-DVD" is not better ?

At 6:50 AM -0400 6/5/07, Jesse Keating wrote: > If you're using pungi on Fedora 7 No. The goal is to help people who can't use a DVD upgrade using CDs, so I and they will be using FC6 to split the F7 DVD with the Pungi from 6.

> comps is not used to determine what packages > get onto the media. The manifest file does. In the case of Fedora 7 there > is an /etc/pungi/f7-fedora.manifest file shipped, as well as > an /etc/pungi/f7-fedora.i386/x86_64/ppc file that can be slightly modified > to make CD isos. Just uncomment and lower the cdsize variable and increase > the discs variable. Where is this .manifest file shipped? There are no .manifest files on the DVD.

How so?  There seems to be a problem with the comps.xml file, which omits 20 packages, some of which are needed.  So far no one has addressed my questions, including that one.  Will there be other problems? Should those who needs F7 CDs install F7 first?  I don't suppose that's much more a slap in the face than having to use Pungi to create the images in the first place.

At 9:40 AM -0400 6/5/07, Jarod Wilson wrote: > Tony Nelson wrote: > I'd just use F7 to build > CDs, get the posted somewhere, and get a torrent going. Yes, please do! Many people who need to install from CDs will thank you for that!

I'm also not sure what you mean by "instructions on the pungi site", as I didn't see any instructions, only a vague plan on how pungi might end up being written.

Just a small note. As I was trying to compose my own set of packages, and (obviously) doing something wrong, I noticed that pungi somehow, somewhere, decided to use my system's yum, instead of through the config file specified with -c. I know, because my own system includes Livna, while my /etc/pungi/ has no mention of livna whatsover (and I don't want/need it on my own spin)

So for testing I created /etc/pungi/f7-fedora-minimal.i386, using the minimal.manifest and overnight that did successfully build the entire tree including ISO images. I haven't had time to debug my own package set configuration yet, I am picking that up later today. Revisor looks like an interesting tool, though it adds another laywer of confusion by using/needing its own pungi files, and comes with a disclaimer that you can only build for the arch that you are currently running (unfortunately, I am running x86_64 and need to build an i386 iso). I am not sure why this requirement is in revisor.

On Tuesday 05 June 2007 09:22:02 Tony Nelson wrote: > No. The goal is to help people who can't use a DVD upgrade using CDs, so I > and they will be using FC6 to split the F7 DVD with the Pungi from 6. The only way you can compose Fedora 7 from Fedora 6 is through mock, and the mock chroot would have to be populated with Fedora 7 content.

> >comps is not used to determine what packages > >get onto the media. The manifest file does. In the case of Fedora 7 > > there is an /etc/pungi/f7-fedora.manifest file shipped, as well as > >an /etc/pungi/f7-fedora.i386/x86_64/ppc file that can be slightly > > modified to make CD isos. Just uncomment and lower the cdsize variable > > and increase the discs variable. > > Where is this .manifest file shipped? There are no .manifest files on the > DVD. It's shipped in the Fedora 7 pungi package.

Content-Type: multipart/signed; boundary="nextPart2008544.aiEdq5Lhs6"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit On Tuesday 05 June 2007 10:44:26 Tony Nelson wrote: > Pungi doesn't just use the comps.xml list of packages and the given repo to > make the install images? It gets some of its content from the running OS? > Perhaps what Pungi gets from the running OS could be added to the > documentation when that gets written. Pungi reads a manifest file that is of kickstart syntax to determine what to "download". It then has to run some anaconda tools on what it downloads to make them installable. Those anaconda tools must match the version of anaconda that is in the distribution. So you need Fedora 7 anaconda tools to compose Fedora 7, and those tools need other parts of Fedora 7, and so on. I do believe this is documented at https://hosted.fedoraproject.org/projects/pungi but maybe not clear enough, I'm not a docs writer. > >> >comps is not used to determine what packages > >> >get onto the media. The manifest file does. In the case of Fedora 7 > >> > there is an /etc/pungi/f7-fedora.manifest file shipped, as well as > >> >an /etc/pungi/f7-fedora.i386/x86_64/ppc file that can be slightly > >> > modified to make CD isos. Just uncomment and lower the cdsize > >> > variable and increase the discs variable. > >> > >> Where is this .manifest file shipped? There are no .manifest files on > >> the DVD. > > > >It's shipped in the Fedora 7 pungi package. > > And apparantly can't be used by a Pungi that runs on FC6. Too bad. > Perhaps I'll be able to make do with the comps.xml file on the DVD. (If it > won't work, it would help to say how it won't work, because it seems to > work.) The resulting iso set will fail. You'll have an install environment of Fedora 7 packages built with Fedora 6 tools that are incompatible.

On Tuesday 05 June 2007 11:23:57 Tony Nelson wrote: > OK. I'll give up now. No F7 CDs from me. You do realize that the Fedora 7 i686 LiveCD is installable right?