Customize Fedora 21 ISO

[Brooks Hu]

Hi Guys,

I am trying to customize F21 ISO and have done some attempts but failed.
Here are some details:

1. I replace some packages in "Packages" directory, then run "createrepo
--update Packages", but it generated a new directory "repodata" under
"Packages". Is that correct?

2. I update .treeinfo with newly calculated sha256sum value for repomd.xml.

When i installed with PXEboot, it gave following errors:

Starting package installation process



An unknown error has occured, look at the /tmp/anaconda-tb* file(s) for
more details



===============================================================================

An unknown error has occurred

===============================================================================

anaconda 21.48.21-1 exception report

Traceback (most recent call first):

  File
"/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py",
line 1112, in _selectYumGroup

    raise NoSuchGroup(groupid, required=required)

  File
"/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py",
line 1227, in _applyYumSelections

    self._selectYumGroup("core")

  File
"/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py",
line 1281, in checkSoftwareSelection

    self._applyYumSelections()

  File
"/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py",
line 1370, in preInstall

    self.checkSoftwareSelection()

  File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py", line
223, in doInstall

    payload.preInstall(packages=packages, groups=payload.languageGroups())

  File "/usr/lib64/python2.7/threading.py", line 766, in run

    self.__target(*self.__args, **self.__kwargs)

  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line
227, in run

    threading.Thread.run(self, *args, **kwargs)

NoSuchGroup: core



What do you want to do now?

1) Report Bug

2) Debug

3) Run shell

4) Quit



Please make your choice from above:


Who can give some suggestions? Thanks a lot!


Regards,

Brooks

[Dennis Gilmore]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 15 Jan 2015 19:37:13 +0800
Brooks Hu <brooks.hu(a)gmail.com&gt; wrote:

>  Hi Guys,
>  
>  I am trying to customize F21 ISO and have done some attempts but
>  failed. Here are some details:
>  
>  1. I replace some packages in "Packages" directory, then run
>  "createrepo --update Packages", but it generated a new directory
>  "repodata" under "Packages". Is that correct?
>  
that is not correct.
you should run "createrepo --update ." you should also make sure to add
the comps file to the cli arguments

>  2. I update .treeinfo with newly calculated sha256sum value for
>  repomd.xml.
>  
you should never do that. you should run pungi to make a new install
tree.

>  When i installed with PXEboot, it gave following errors:
>  
>  Starting package installation process
>  
>  
>  
>  An unknown error has occured, look at the /tmp/anaconda-tb* file(s)
>  for more details
>  
>  
>  
>  ===============================================================================
>  
>  An unknown error has occurred
>  
>  ===============================================================================
>  
>  anaconda 21.48.21-1 exception report
>  
>  Traceback (most recent call first):
>  
>    File
>  "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py",
>  line 1112, in _selectYumGroup
>  
>      raise NoSuchGroup(groupid, required=required)
>  
>    File
>  "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py",
>  line 1227, in _applyYumSelections
>  
>      self._selectYumGroup("core")
>  
>    File
>  "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py",
>  line 1281, in checkSoftwareSelection
>  
>      self._applyYumSelections()
>  
>    File
>  "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py",
>  line 1370, in preInstall
>  
>      self.checkSoftwareSelection()
>  
>    File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py",
>  line 223, in doInstall
>  
>      payload.preInstall(packages=packages,
>  groups=payload.languageGroups())
>  
>    File "/usr/lib64/python2.7/threading.py", line 766, in run
>  
>      self.__target(*self.__args, **self.__kwargs)
>  
>    File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py",
>  line 227, in run
>  
>      threading.Thread.run(self, *args, **kwargs)
>  
>  NoSuchGroup: core
>  
>  
>  
>  What do you want to do now?
>  
>  1) Report Bug
>  
>  2) Debug
>  
>  3) Run shell
>  
>  4) Quit
>  
>  
>  
>  Please make your choice from above:
>  
>  
>  Who can give some suggestions? Thanks a lot!
>  
That error is because you do not have any comps groups since you didn't
use the right options on createrepo.

you could just make your own repo and tell anaconda about it. which is
likely a simpler path to go down.

Dennis

> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iQIcBAEBAgAGBQJUt9KMAAoJEH7ltONmPFDRUPEQALAwGY7LMtGG1A3yOisl598i
> pD1DYtGR0REtiuO5s+JhxjOyOGM2wgn8lFx+loFuhBrjB4iEAiRtg/B08H1qkLaK
> 7PKGumsAslgRv5Zz8NArv1Jrn/se7gzeX1zSHKLl7IxQnRMGg/VkvBi0j/qD36Eu
> Z/fIBQ2AW2w9DEo49SSazuARw9SgXgAodX+ugV3C9N+Le1G4FUFG6rVB8T0sstLZ
> Dbvmqk6WKjti8qRZ3LK+11inkc5DCdUo+r0+Qfr2Rlp5rFQ2UG3wnY0qvjbtCld+
> J4ja7q8kDa9Zq16IVPyFt59MUFx3C2f+b2W4dlefwXTV1bR4k1NEB3WiJcPuBMz9
> tEZMCs9IeBng5vTIykKQGHAr6vOzFv7JUa7G46WSI86tkua6KJf2YYHWJ5TUs5JN
> 2t4ecVAdxNAqILuJvkIzj2ekwEiIgpkuFdy6017rwoYj9Rrl8EcIWRbYQU65Cx5a
> GrJEbkTvgo9c0gAfSwRqrTMLq6pGmGPlu8J6esDQ6jNU5KHUgatWM0bvdwvQBLa4
> AA4dL4hL5FDSwxBwE7q2H85fEXjSjA38FoPRz1Vt4Zj7tcRL6V1lMOatRi5UXjHw
> rW8yHhvuVH9eocNQo/+LTfM70D4VaaQO+C+3n5wQNhZ/7BSs3V3KB+u1rSulMq5X
> OIr50On4wMXyb6Ds+rbB
> =dVxB
> -----END PGP SIGNATURE-----
>

[Brooks Hu]

Thanks Dennis.

I did following experiment:

Mounted ISO onto a local directory, changed to the directory, did nothing,
run "createrepo --update .", but I found the files under repodata changed,
including the checksum in filename. Is that expected? I suppose they
shouldn't be changed.

I am readying the manual of pungi.

One more question: do you have any good links about customizing a ISO? I
found a few pages, but they seem not to work.

Regards,
Brooks


On Thu, Jan 15, 2015 at 10:45 PM, Dennis Gilmore <dennis(a)ausil.us&gt; wrote:

>  -----BEGIN PGP SIGNED MESSAGE-----
>  Hash: SHA1
>
>  On Thu, 15 Jan 2015 19:37:13 +0800
>  Brooks Hu <brooks.hu(a)gmail.com&gt; wrote:
>
>  > Hi Guys,
>  >
>  > I am trying to customize F21 ISO and have done some attempts but
>  > failed. Here are some details:
>  >
>  > 1. I replace some packages in "Packages" directory, then run
>  > "createrepo --update Packages", but it generated a new directory
>  > "repodata" under "Packages". Is that correct?
>  that is not correct.
>  you should run "createrepo --update ." you should also make sure to add
>  the comps file to the cli arguments
>
>  > 2. I update .treeinfo with newly calculated sha256sum value for
>  > repomd.xml.
>  you should never do that. you should run pungi to make a new install
>  tree.
>
>  > When i installed with PXEboot, it gave following errors:
>  >
>  > Starting package installation process
>  >
>  >
>  >
>  > An unknown error has occured, look at the /tmp/anaconda-tb* file(s)
>  > for more details
>  >
>  >
>  >
>  >
>  ===============================================================================
>  >
>  > An unknown error has occurred
>  >
>  >
>  ===============================================================================
>  >
>  > anaconda 21.48.21-1 exception report
>  >
>  > Traceback (most recent call first):
>  >
>  >   File
>  > "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py",
>  > line 1112, in _selectYumGroup
>  >
>  >     raise NoSuchGroup(groupid, required=required)
>  >
>  >   File
>  > "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py",
>  > line 1227, in _applyYumSelections
>  >
>  >     self._selectYumGroup("core")
>  >
>  >   File
>  > "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py",
>  > line 1281, in checkSoftwareSelection
>  >
>  >     self._applyYumSelections()
>  >
>  >   File
>  > "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py",
>  > line 1370, in preInstall
>  >
>  >     self.checkSoftwareSelection()
>  >
>  >   File "/usr/lib64/python2.7/site-packages/pyanaconda/install.py",
>  > line 223, in doInstall
>  >
>  >     payload.preInstall(packages=packages,
>  > groups=payload.languageGroups())
>  >
>  >   File "/usr/lib64/python2.7/threading.py", line 766, in run
>  >
>  >     self.__target(*self.__args, **self.__kwargs)
>  >
>  >   File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py",
>  > line 227, in run
>  >
>  >     threading.Thread.run(self, *args, **kwargs)
>  >
>  > NoSuchGroup: core
>  >
>  >
>  >
>  > What do you want to do now?
>  >
>  > 1) Report Bug
>  >
>  > 2) Debug
>  >
>  > 3) Run shell
>  >
>  > 4) Quit
>  >
>  >
>  >
>  > Please make your choice from above:
>  >
>  >
>  > Who can give some suggestions? Thanks a lot!
>
>  That error is because you do not have any comps groups since you didn't
>  use the right options on createrepo.
>
>  you could just make your own repo and tell anaconda about it. which is
>  likely a simpler path to go down.
>
>  Dennis
>
> >  -----BEGIN PGP SIGNATURE-----
> >  Version: GnuPG v2
> >
> >  iQIcBAEBAgAGBQJUt9KMAAoJEH7ltONmPFDRUPEQALAwGY7LMtGG1A3yOisl598i
> >  pD1DYtGR0REtiuO5s+JhxjOyOGM2wgn8lFx+loFuhBrjB4iEAiRtg/B08H1qkLaK
> >  7PKGumsAslgRv5Zz8NArv1Jrn/se7gzeX1zSHKLl7IxQnRMGg/VkvBi0j/qD36Eu
> >  Z/fIBQ2AW2w9DEo49SSazuARw9SgXgAodX+ugV3C9N+Le1G4FUFG6rVB8T0sstLZ
> >  Dbvmqk6WKjti8qRZ3LK+11inkc5DCdUo+r0+Qfr2Rlp5rFQ2UG3wnY0qvjbtCld+
> >  J4ja7q8kDa9Zq16IVPyFt59MUFx3C2f+b2W4dlefwXTV1bR4k1NEB3WiJcPuBMz9
> >  tEZMCs9IeBng5vTIykKQGHAr6vOzFv7JUa7G46WSI86tkua6KJf2YYHWJ5TUs5JN
> >  2t4ecVAdxNAqILuJvkIzj2ekwEiIgpkuFdy6017rwoYj9Rrl8EcIWRbYQU65Cx5a
> >  GrJEbkTvgo9c0gAfSwRqrTMLq6pGmGPlu8J6esDQ6jNU5KHUgatWM0bvdwvQBLa4
> >  AA4dL4hL5FDSwxBwE7q2H85fEXjSjA38FoPRz1Vt4Zj7tcRL6V1lMOatRi5UXjHw
> >  rW8yHhvuVH9eocNQo/+LTfM70D4VaaQO+C+3n5wQNhZ/7BSs3V3KB+u1rSulMq5X
> >  OIr50On4wMXyb6Ds+rbB
> >  =dVxB
> >  -----END PGP SIGNATURE----- 
>  _______________________________________________
>  arm mailing list
>  arm(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/arm

[Peter Robinson]

On Fri, Jan 16, 2015 at 3:34 AM, Brooks Hu <brooks.hu(a)gmail.com&gt; wrote:
>  Thanks Dennis.
>
>  I did following experiment:
>
>  Mounted ISO onto a local directory, changed to the directory, did nothing,
>  run "createrepo --update .", but I found the files under repodata changed,
>  including the checksum in filename. Is that expected? I suppose they
>  shouldn't be changed.
>
>  I am readying the manual of pungi.
>
>  One more question: do you have any good links about customizing a ISO? I
>  found a few pages, but they seem not to work. 
You can't really customise a Fedora installer iso. You basically have
two options:
1) Regenerate the iso from clean
2) Use the existing installer iso but point it to a new
updated/changed repository.

Peter

[Jon Masters]

On 01/15/2015 10:57 PM, Peter Robinson wrote:
>  On Fri, Jan 16, 2015 at 3:34 AM, Brooks Hu
> <brooks.hu(a)gmail.com&gt; wrote:
> > Thanks Dennis.
> >
> > I did following experiment:
> >
> > Mounted ISO onto a local directory, changed to the directory, did nothing,
> > run "createrepo --update .", but I found the files under repodata changed,
> > including the checksum in filename. Is that expected? I suppose they
> > shouldn't be changed.
> >
> > I am readying the manual of pungi.
> >
> > One more question: do you have any good links about customizing a ISO? I
> > found a few pages, but they seem not to work.
>  
>  You can't really customise a Fedora installer iso. You basically have
>  two options:
>  1) Regenerate the iso from clean
>  2) Use the existing installer iso but point it to a new
>  updated/changed repository. 
Depending what you're doing, the latter (2) might really be what you
want. Especially if you use a Kickstart file, there is rarely a need to
actually respin the entire media.

Jon.

[Brooks Hu]

Thanks, Jon.

But I want to try the first approach for some special requirements, then
what should i do? I failed to find a complete guide on the Internet.

Regards,
Brooks


On Fri, Jan 16, 2015 at 1:02 PM, Jon Masters <jcm(a)redhat.com&gt; wrote:

>  On 01/15/2015 10:57 PM, Peter Robinson wrote:
>  > On Fri, Jan 16, 2015 at 3:34 AM, Brooks Hu <brooks.hu(a)gmail.com&gt; wrote:
>  >> Thanks Dennis.
>  >>
>  >> I did following experiment:
>  >>
>  >> Mounted ISO onto a local directory, changed to the directory, did
>  nothing,
>  >> run "createrepo --update .", but I found the files under repodata
>  changed,
>  >> including the checksum in filename. Is that expected? I suppose they
>  >> shouldn't be changed.
>  >>
>  >> I am readying the manual of pungi.
>  >>
>  >> One more question: do you have any good links about customizing a ISO? I
>  >> found a few pages, but they seem not to work.
>  >
>  > You can't really customise a Fedora installer iso. You basically have
>  > two options:
>  > 1) Regenerate the iso from clean
>  > 2) Use the existing installer iso but point it to a new
>  > updated/changed repository.
>
>  Depending what you're doing, the latter (2) might really be what you
>  want. Especially if you use a Kickstart file, there is rarely a need to
>  actually respin the entire media.
>
>  Jon.
>
>
>  _______________________________________________
>  arm mailing list
>  arm(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/arm
>

[Robert Moskowitz]

On 01/16/2015 12:02 AM, Jon Masters wrote:
>  On 01/15/2015 10:57 PM, Peter Robinson wrote:
> > On Fri, Jan 16, 2015 at 3:34 AM, Brooks Hu <brooks.hu(a)gmail.com&gt; wrote:
> >> Thanks Dennis.
> >>
> >> I did following experiment:
> >>
> >> Mounted ISO onto a local directory, changed to the directory, did nothing,
> >> run "createrepo --update .", but I found the files under repodata
> changed,
> >> including the checksum in filename. Is that expected? I suppose they
> >> shouldn't be changed.
> >>
> >> I am readying the manual of pungi.
> >>
> >> One more question: do you have any good links about customizing a ISO? I
> >> found a few pages, but they seem not to work.
> > You can't really customise a Fedora installer iso. You basically have
> > two options:
> > 1) Regenerate the iso from clean
> > 2) Use the existing installer iso but point it to a new
> > updated/changed repository.
>  Depending what you're doing, the latter (2) might really be what you
>  want. Especially if you use a Kickstart file, there is rarely a need to
>  actually respin the entire media. 
I had to do this years ago with Centos 4 to build an iso that would even 
start on a old piece of hardware.  It was really painful and Karanbir 
was a big help at the time.  Doubt if I can find my notes. These days, 
as long as I can boot into a netinstal and maybe grab a kickstart file, 
do see needing a custom iso.  Those are for times when you can't even 
get through the boot process.

[Brooks Hu]

Robert,

It would be highly appreciated if you can find the notes. Thanks a lot!

Regards,
Brooks

On Fri, Jan 16, 2015 at 10:06 PM, Robert Moskowitz <rgm(a)htt-consult.com&gt;
wrote:

>  On 01/16/2015 12:02 AM, Jon Masters wrote:
>
> > On 01/15/2015 10:57 PM, Peter Robinson wrote:
> >
> >> On Fri, Jan 16, 2015 at 3:34 AM, Brooks Hu <brooks.hu(a)gmail.com&gt; wrote:
> >>
> >>> Thanks Dennis.
> >>>
> >>> I did following experiment:
> >>>
> >>> Mounted ISO onto a local directory, changed to the directory, did
> >>> nothing,
> >>> run "createrepo --update .", but I found the files under repodata
> >>> changed,
> >>> including the checksum in filename. Is that expected? I suppose they
> >>> shouldn't be changed.
> >>>
> >>> I am readying the manual of pungi.
> >>>
> >>> One more question: do you have any good links about customizing a ISO? I
> >>> found a few pages, but they seem not to work.
> >>>
> >> You can't really customise a Fedora installer iso. You basically have
> >> two options:
> >> 1) Regenerate the iso from clean
> >> 2) Use the existing installer iso but point it to a new
> >> updated/changed repository.
> >>
> > Depending what you're doing, the latter (2) might really be what you
> > want. Especially if you use a Kickstart file, there is rarely a need to
> > actually respin the entire media.
> >
>
>  I had to do this years ago with Centos 4 to build an iso that would even
>  start on a old piece of hardware.  It was really painful and Karanbir was a
>  big help at the time.  Doubt if I can find my notes. These days, as long as
>  I can boot into a netinstal and maybe grab a kickstart file, do see needing
>  a custom iso.  Those are for times when you can't even get through the boot
>  process.
>
>
>
>  _______________________________________________
>  arm mailing list
>  arm(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/arm
>