[Server-devel] Revisor / yum oddity: anaconda-runtime

[Jeroen van Meeuwen]

Jerry Vonau wrote:
> Martin Langhoff wrote:
>> On Fri, Sep 19, 2008 at 10:23 PM, Jeroen van Meeuwen
>> <kanarip at kanarip.com> wrote:
>>> Hence the log-file is of interest to me ;-)
>>
>> Sent it in a private email :-)
>>
>>> Yes, anaconda-runtime needs to exist in the repositories you use.
>>
>> Sorry - I should have clarified - anaconda-runtime *is* in the repos
>> configured. (otherwise, adding it to the ks wouldn't help anyway!)
>>
> 
> "runtime" won't be in the repo that you're "spinning", and that is the 
> one that buildinstall is going to use:
> 
> if [[ "$REPO" =~ ^/ ]]; then
>     [ -n "$OUTPUT" ] || OUTPUT=$REPO
>     REPO="file://$REPO"
> 
> and from the log OUTPUT is set to:
> /var/tmp/revisor-pungi/0.5/xs-f9-i386/i386/os
> 
> That is the repo that getting spun right?
> 

That is the composed tree, yes.

 From the log files though, you can see that more then one repository is 
used during buildinstall:

Running Command: /usr/lib/revisor/scripts/F9-buildinstall --debug \
   --product OLPC School Server --variant xs-f9-i386 --version 0.5 \
   --release OLPC School Server 0.5 \
   /var/tmp/revisor-pungi/0.5/xs-f9-i386/i386/os \
   file:///xsrepos/testing/olpc/7/i386/ \
   file:///media/disk/xs/releases/9/Everything/i386/os/ \
   http://fedora.laptop.org/xs/testing/olpc/9/i386/

All of these should be searched for the anaconda-runtime package... I'm 
trying to figure out why it isn't so.

Kind regards,

Jeroen van Meeuwen
-kanarip