[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Server-devel] Troubles running F9 mock chroot under F11



On Wed, 2009-09-16 at 10:32 +0545, Daniel Drake wrote:
> 2009/9/15 Jerry Vonau <jvonau shaw ca>:
> > Are you just adding rpms to the install media? Or are you trying
> > something more difficult? I have a process in mind if you're just adding
> > rpms to the mix...
> 
> Just adding RPMs would be enough, but also we're customizing the
> kickstart file a little.
> 

That should be do-able using mkslim (read it first) from xs-livecd's git
repo, along with my idea to use a pre-configured "updates repo" on the
iso. 

http://lists.laptop.org/pipermail/server-devel/2009-February/002937.html

You would create an "overlay tree" in lets say /tmp/xsupdates/, this
will hold what files you want to add/change on the iso. Now just make a
tree for the files in /tmp/xsupdates/. Create a directory updates,
populate it with rpms and run createrepo against it. If you wish to
replace/add a file on the iso, just have them be in the same place in
the xsupdates directory, as it would be on the iso. eg: xsupdates/ks.cfg
xsupdates/isolinux/isolinux.cfg. Then call 

mkslim <path to iso> <output dir> /tmp/xsupdates

Remember to add the repo line to the kickstart file or add them as a
boot argument, for usb:
repo --name=updates --baseurl=file:///mnt/isodir/updates 
for cdrom:
repo --name=updates --baseurl=file:///mnt/stage2/updates 

The usb method is tested, while I have not tested the cdrom iso

> > However, I see that the older buildinstall(s) are not present any
> > more(?)! (File a bug I guess)  If you were to add the buildinstall from
> > F9's anaconda in revisor's script directory as F9-buildinstall, then the
> > buildinstall from F9 should be used instead of the one on the host
> > system.
> 
> I did that and it now fails at a later point. I first had to modify pungi.py
> +        buildinstall.append('--output')
>          buildinstall.append(self.topdir)
> 
> and the end result is:
> 
> Linking in release notes:
> ######################################## 100.0%
> Size of the installation tree is 518 MB
> Traceback (most recent call last):
>   File "/usr/lib/python2.6/site-packages/revisor/__init__.py", line 528, in run
>     self.base.run()
>   File "/usr/lib/python2.6/site-packages/revisor/base.py", line 106, in run
>     self.cli.run()
>   File "/usr/lib/python2.6/site-packages/revisor/cli.py", line 44, in run
>     self.base.lift_off()
>   File "/usr/lib/python2.6/site-packages/revisor/base.py", line 867, in lift_off
>     self.buildInstallationMedia()
>   File "/usr/lib/python2.6/site-packages/revisor/base.py", line 1478,
> in buildInstallationMedia
>     f = open(os.path.join(mypungi.topdir,"isolinux","isolinux.cfg"),"rw+")
> IOError: [Errno 2] No such file or directory:
> '/var/tmp/revisor-pungi/0.5.2/xs-f9-i386/i386/os/isolinux/isolinux.cfg'
> Traceback occurred, please report a bug at http://fedorahosted.org/revisor
> 
> The size should be more like 850mb.
> 
> Did you have any luck in your own experiment?
> 
No, I stopped when it bombed out, had to do my real work, must of been
at the point you got past with the patched pungi.py. 

Jerry



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]