8:14 a.m.
I am trying to add a custom rpm (my netexec script posted earlier to
fedora-devel), to a nfs kickstart install. I copied the rpm to the
RPMS/ directory and added the following to
/install/fedora/Fedora/base/comps.xml
<group>
<id>netexec-sc</id>
<name>Netexec Client/Server</name>
<description>Network command queueing program</description>
<uservisible>false</uservisible>
<packagelist>
<packagereq type="default"
requires="perl-Frontier-RPC">netexec</packagereq>
</packagelist>
</group>
Then I ran: /usr/lib/anaconda-runtime/genhdlist --productpath Fedora
/data/install/fedora
When I started the kickstart install it produced the following error and died:
WARNING: not all packages in hdlist had order tag.
Any clue as to why this died? The most recent information on custom
nfs installs that I
can find is from RedHat 8.0.
The rpm in question is attached.
--
Christopher Hotchkiss
(813)960-9273
http://www.post227.org
8:18 a.m.
Christopher Hotchkiss wrote:
Then I ran: /usr/lib/anaconda-runtime/genhdlist --productpath Fedora
/data/install/fedora
When I started the kickstart install it produced the following error and died:
WARNING: not all packages in hdlist had order tag.
Any clue as to why this died?
In my experience, the WARNING is harmless. It's dieing for some other
reason.
-- Rex
8:22 a.m.
On Tuesday, December 21, 2004 8:18 AM, Rex Dieter wrote:
Christopher Hotchkiss wrote:
> Then I ran: /usr/lib/anaconda-runtime/genhdlist --productpath Fedora
> /data/install/fedora
>
> When I started the kickstart install it produced the
following error and died:
> WARNING: not all packages in hdlist had order tag.
>
> Any clue as to why this died?
In my experience, the WARNING is harmless. It's dieing for
some other
reason.
-- Rex
I'm no expert on this, but can you do 'requires="perl-Frontier-RPC"'
if
perl-Frontier-RPC is not somewhere earlier in the list? Aren't you
requiring a package that doesn't exist?
Matthew E. Lauterbach
4:26 p.m.
Well I removed all my changes to the comps.xml file and did a
genhdlist. When I boot an intstall box though, I still get the same
error.
--
Christopher Hotchkiss
(813)960-9273
http://www.post227.org
7:31 a.m.
Christopher Hotchkiss wrote:
I am trying to add a custom rpm (my netexec script posted earlier to
fedora-devel), to a nfs kickstart install. I copied the rpm to the
RPMS/ directory and added the following to
/install/fedora/Fedora/base/comps.xml
<group>
<id>netexec-sc</id>
<name>Netexec Client/Server</name>
<description>Network command queueing program</description>
<uservisible>false</uservisible>
<packagelist>
<packagereq type="default"
requires="perl-Frontier-RPC">netexec</packagereq>
</packagelist>
</group>
Then I ran: /usr/lib/anaconda-runtime/genhdlist --productpath Fedora
/data/install/fedora
When I started the kickstart install it produced the following error and died:
WARNING: not all packages in hdlist had order tag.
Any clue as to why this died? The most recent information on custom
nfs installs that I
can find is from RedHat 8.0.
The rpm in question is attached.
I ran into the same type of problem when I tried to create a local
network installation point including the packages from the updates.
Because of the warning I rerun the whole process using a pkgorder file
and that worked. Because I didn't look into it any further I wasn't sure
that the first problem was due to a missing pkgorder or not.
Nevertheless you may want to try it as well. Here's approximatively the
commands I used:
PYTHONPATH=/usr/lib/anaconda /usr/lib/anaconda-runtime/pkgorder <top dir> i386 >
<pkgorder file>
/usr/lib/anaconda-runtime/genhdlist --productpath Fedora --pkgorder <pkgorder file>
<top dir>
/usr/lib/anaconda-runtime/buildinstall --product "Fedora Core" --version 3
--release "Fedora Core 3" --pkgorder <pkgorder file> --prodpath Fedora
<top dir>
11:20 a.m.
On Thu, 23 Dec 2004 14:31:43 +0100, Charles Lopes <tjarls(a)iee.lu> wrote:
I ran into the same type of problem when I tried to create a local
network installation point including the packages from the updates.
Because of the warning I rerun the whole process using a pkgorder file
and that worked. Because I didn't look into it any further I wasn't sure
that the first problem was due to a missing pkgorder or not.
Nevertheless you may want to try it as well. Here's approximatively the
commands I used:
PYTHONPATH=/usr/lib/anaconda /usr/lib/anaconda-runtime/pkgorder <top dir> i386 >
<pkgorder file>
/usr/lib/anaconda-runtime/genhdlist --productpath Fedora --pkgorder <pkgorder file>
<top dir>
/usr/lib/anaconda-runtime/buildinstall --product "Fedora Core" --version 3
--release "Fedora Core 3" --pkgorder <pkgorder file> --prodpath Fedora
<top dir>
I got away with:
export PYTHONPATH=/usr/lib/anaconda
/usr/lib/anaconda-runtime/pkgorder <dir> <arch> Fedora > <file>
/usr/lib/anaconda-runtime/genhdlist --productpath Fedora --withnumbers
--pkgorder <file> <dir>
unset PYTHONPATH
run the install
The third argument to pkgorder, I don't remember being in the manpage
but it worked.
good luck,
--
matt whiteley <mattwhiteley(a)gmail.com>
7103
days inactive
7105
days old
5 comments
5 participants
participants (5)
-
Charles Lopes -
Christopher Hotchkiss -
matt whiteley -
Matthew E. Lauterbach -
Rex Dieter