Re: [Server-devel] Troubles running F9 mock chroot under F11
2009/9/16 Jerry Vonau jvo...@shaw.ca: 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 Thanks! Got it working as follows: 1. extract ISO 2. copy in new ks file 3. add more RPMs to Packages/ (using creative use of yumdownloader to make sure that deps come with the new RPMs) 4. createrepo --database --groupfile repodata/comps.xml . 5. remove stuff that mkslim removes 6. mkisofs no need to mess with bdb stuff any more :) Daniel ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Troubles running F9 mock chroot under F11
On Thu, Sep 17, 2009 at 1:47 PM, Daniel Drake d...@laptop.org wrote: Thanks! Got it working as follows: 1. extract ISO 2. copy in new ks file 3. add more RPMs to Packages/ (using creative use of yumdownloader to make sure that deps come with the new RPMs) 4. createrepo --database --groupfile repodata/comps.xml . 5. remove stuff that mkslim removes 6. mkisofs no need to mess with bdb stuff any more :) Good to hear it's worked! Thinking about future support for that deployment and also for the XS (as upstream) -- is it in your plans to document what rpms and ks changes you are using? cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Troubles running F9 mock chroot under F11
2009/9/17 Jerry Vonau jvo...@shaw.ca:
Well not quite the way I would of done it, I was hoping someone else
would test my idea, but glad you got what you needed done. Mind sharing
the yumdownloader routine? I might try to use something like that to
populate my updates repo, then remove any duplicates in the rpms what
would take extra space on the iso.
During the build script:
cat EOF yum.conf
[main]
reposdir=$(pwd)/yumrepos
cachedir=/var/cache/yum-xs
EOF
pushd ${isocopy}/Packages
yumdownloader -c ../../yum.conf --resolve mysql-server mysql php-mysql
expect ImageMagick graphviz php-tidy java-1.6.0-openjdk
java-1.6.0-openjdk-devel
popd
yumrepos/ then contains 2 repo files, one for F9 and one for F9 updates.
The only slightly awkward thing is that the added packages have to be
listed twice, once above and once in the kickstart file. Of course, we
could automate the construction of the ks file but that's adding more
complexity than I'd like to leave behind in Nepal.
Daniel
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel
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 jvo...@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
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Troubles running F9 mock chroot under F11
On Tue, Sep 15, 2009 at 12:02 PM, Daniel Drake d...@laptop.org wrote: I then tried to create a F9 chroot using mock, with the intention of running revisor or pungi inside. This doesn't work, because mock creates a v9 berkeley DB inside the chroot, but the libraries/apps inside the chroot only support bdb v8. So running rpm -qa inside a fresh F9 chroot on F11 gives you these errors: mock-chroot rpm -qa rpmdb: /var/lib/rpm/Packages: unsupported hash version: 9 error: cannot open Packages index using db3 - Invalid argument (22) error: cannot open Packages database in /var/lib/rpm I keep my build machine of F9 due to similar issues I saw building F7 from F9 -- however, ISTR there's been some discussion of this recently. Hmmm, a bit of googling leads to a nice thread http://www.mail-archive.com/fedora-buildsys-l...@redhat.com/msg02210.html which if you read in depth seems to indicate that either of: rm -f /var/lib/rpm/__db* /bin/rpm --rebuilddb fixes the problem. Probably either triggers the other. For obvious reasons I am interested in the results -- let me know if it works. m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Troubles running F9 mock chroot under F11
2009/9/15 Jerry Vonau jvo...@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.
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?
Daniel
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel
