Re: [revisor-users] [Revisor-users] no init found
by Jeroen van Meeuwen
Filip Slunecko wrote:
> Hi,
>
> I've tried make Fedora 10 i386 cd (not live). Isos are created but I
> can't boot from them. I always get this "Kernel panic - not syncing: No init
> found. Try passing init= option to kernel".
>
> I tried it many times with diffierent packages but always with this
> message.
>
> Thx for any advise.
>
> Revisor: 2.1.3-1
> Fedora 10 x64
>
There's a huge bug in building i386 on a x86_64 platform. In this case,
it may be either of a popt.i386 package missing on the host (needs to be
installed), the non-chroot linking that anaconda does (sigh), or missing
libraries because of how anaconda installs these into a tree.
My recommendation at this point, is to use mock;
# yum install mock
Edit /etc/mock/site-defaults.cfg to bind mount /selinux into the chroot:
config_opts['plugin_conf']['bind_mount_opts']['dirs'].append(('/selinux/',
'/selinux/' ))
Then,
$ mock -v -r fedora-10-i386 init
$ mock -v -r fedora-10-i386 install comps-extras createrepo \
rhpl pykickstart livecd-tools anaconda-runtime squashfs-tools \
busybox-anaconda notify-python usermode pam python automake \
intltool gettext desktop-file-utils glib2-devel gcc \
cobbler koan deltarpm pygtk pygtk2-libglade gnome-python2-gconf \
system-config-kickstart jigdo python-virtinst git sudo \
spin-kickstarts mock
$ mock -v -r fedora-10-i386 shell
mock> git clone git://git.fedorahosted.org/revisor
mock> cd /revisor
mock> ./switchhere --yes
mock> autoreconf && ./configure
mock> rm -rf /var/lib/rpm/__db.00*
mock> ./revisor.py --cli [options]
I'm very sorry it has to be like this :/ I'm working on getting this
fixed but re-writing the building procedures anaconda has now isn't an
easy task :/
Kind regards,
Jeroen van Meeuwen
-kanarip
15 years
Empty repodata/comps.xml file ?
by Syed Sajjad Lateef
Hi all,
I am using Revisor (revisor-2.0.5-15.fc8) to respin a CentOS ISO with only the default base, core groups and some custom packages in a group I specified.
I created a comps.xml file that is based off the comps-c5.xml and a very simple kickstart file based off centos-5-ks.cfg.
The comps.xml has pretty much the same base and core groups, except all the "xml:lang" lines have been removed (English only installer) and a new group added (with my packages) and a new category that includes my group+base+core. The kickstart file has only my custom group specified in the "%packages" section.
I do get a valid ISO file with about 450 rpms in it, including my custom packages. However, when installed, this ISO results in an installation that is skeletal - kernel, shell and little else (not even vim).
After digging around, I found that the ISO being built has an empty ISO:/repodata/comps.xml file. I guess that the skeletal installation is the result of an empty comps.xml file i.e. <comps />. As far as I can tell, this /repodata/comps.xml originates from /var/tmp/revisor-pungi/VERSION/MODEL/comps.xml and this file is created sometime after the packages are downloaded but before pkgdir is created.
I'd appreciate any suggestions on:
A) Why the ISO installation is skeletal - is it really because of an empty repodata/comps.xml file?
B) What do I need to tweak in order to fix this issue?
Thanks
Sajjad
15 years, 1 month
Re: [revisor-users] [Revisor-users] Revisor not loading repositories
by Jeroen van Meeuwen
On 03/24/2009 04:58 AM, JORDAN MINER wrote:
>
> I am trying to use Revisor to build a DVD with all the programs I use on
> it. However, when Revisor gets the step of downloading repository
> information, it hangs for a minute or two, then displays this error:
>
> Fatal Error: Unable to retrieve software information.
> This could be caused by one of the following:
> - not having a network connection available,
> - Server refusing connections,
> - Using a mirror that isn't fully synchronized,
> - Misconfigured repositories.
>
> Any help?
>
Please remove the updates-newkey repositories which were added to the
default configuration files for Fedora 10 by mistake.
Kind regards,
Jeroen van Meeuwen
-kanarip
15 years, 1 month
Re: [revisor-users] Need help with revisor
by Jeroen van Meeuwen
Oral wrote:
> OK, I have Revisor running in F10 now. It still fails to find the
> rebrand packages, but now instead of telling me one at a time it gives
> me a complete list.
> It seems to me that if the directions to the repo are correct it must be
> a bad repo. I don't have any experience with creating repos beyond this
> one. What I did was copy the contents of rebrand-template into a folder
> called PB-Repo, then use createrepo on it. That took a while, after
> which there was a Repodata folder added. Then I uploaded the resulting
> PB-Repo to my website.
>
> To make sure it could be accessed I browsed to
> http://development-resources.com/PB-Repo/PeachBandit-logos/kde-splash/Blu...
> and viewed the photo in Firefox.
>
> Do these steps look correct to you ?
Not really. You should create a -release and -logos package similar to
the existing fedora-release and fedora-logos package. As an example, in
Fedora 10, the package generic-release and generic-logos is made
available, debranding (not rebranding) the Fedora distribution.
The contents of what used to be rebrand-template can be removed. It's
obsolete in the sense that it worked once, but caused a lot of problems
and other challenges afterwards.
Right now, the workflow is as follows:
You create a foo-release and foo-logos package, taking generic-release
and generic-logos as the example. You may also just use generic-release
and generic-logos to see how it works.
If you choose to create a foo-logos and foo-release package, you put
these in a directory and run createrepo on that directory. Then you add
the location to the repository in your configuration file, and execute
Revisor with --rebrand=foo.
In this case, just to show how things work, maybe execute revisor with
--rebrand=generic and see how things go.
Kind regards,
Jeroen van Meeuwen
-kanarip
PS. I'm putting the mailing list in CC:, because this should be
Googleable in the future.
15 years, 1 month
