FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Build System

 
 
LinkBack Thread Tools
 
Old 09-18-2008, 07:44 AM
"Martin Langhoff"
 
Default Revisor / yum oddity: anaconda-runtime

On Fedora 9, using F9's revisor which has not changed in a while...

- last week, I was able to invoke revisor and create a new installer
CD without any problem...
- this week, buildinstall dies, and if I enable logging it complains
missing anaconda-runtime
- this is looking at a local copy of the 'release' repo - I rsync'd
it earlier today, but IIRC it had not changed...
- my custom packages have changed a little bit, but none of them
required anaconda-runtime
- I have been experimenting with a different version of revisor -
I've nuked /var/tmp/revisor* - perhaps state got saved anywhere else?

Adding anaconda-runtime to the kickstart file that drives the process
fixes the problem. It's not a problem I was expecting to have though
:-/

In any case, am I missing any factor that could be messing up the process?

cheers,


m
--
martin.langhoff@gmail.com
martin@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

--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
 
Old 09-18-2008, 08:50 AM
Jeroen van Meeuwen
 
Default Revisor / yum oddity: anaconda-runtime

Martin Langhoff wrote:

On Fedora 9, using F9's revisor which has not changed in a while...

- last week, I was able to invoke revisor and create a new installer
CD without any problem...
- this week, buildinstall dies, and if I enable logging it complains
missing anaconda-runtime
- this is looking at a local copy of the 'release' repo - I rsync'd
it earlier today, but IIRC it had not changed...
- my custom packages have changed a little bit, but none of them
required anaconda-runtime
- I have been experimenting with a different version of revisor -
I've nuked /var/tmp/revisor* - perhaps state got saved anywhere else?

Adding anaconda-runtime to the kickstart file that drives the process
fixes the problem. It's not a problem I was expecting to have though
:-/

In any case, am I missing any factor that could be messing up the process?



I'd like to know what version of Fedora you're attempting to compose...
Also Fedora 9?


I'd love some debug output, since it's going to tell me what happened
exactly. --debug 9 should do the trick and you can send it to me in
private (since it's going to end up being a large log file).


Kind regards,

Jeroen van Meeuwen
-kanarip

--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
 
Old 09-19-2008, 04:33 AM
"Martin Langhoff"
 
Default Revisor / yum oddity: anaconda-runtime

On Fri, Sep 19, 2008 at 3:16 AM, Jerry Vonau <jvonau@shaw.ca> wrote:
> Yea, revisor needs anaconda-runtime,
> cat /usr/lib/revisor/scripts/F9-buildinstall | grep anaconda

Yes, but from what Jeroen has said, revisor will pull it in to satisfy
the need at CD build time, without it being listed in the ks file (and
therefore getting installed on the target system too...)

> Anaconda-runtime needs to exist in the repo that you use for the compose,
> but doesn't need to be in the kickstart file. Too bad, you have to add
> anaconda-runtime to the kickstart file, to get the package into the compose
> repo, in order to use it later in buildinstall.

Well, that's supposed to be true for pungi, not true for revisor.

As far as I understand anyway :-) Jeroen has asked for logs and I'm
collecting some right now...

cheers,



m
--
martin.langhoff@gmail.com
martin@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

--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
 
Old 09-19-2008, 10:23 AM
Jeroen van Meeuwen
 
Default Revisor / yum oddity: anaconda-runtime

Martin Langhoff wrote:

On Fri, Sep 19, 2008 at 3:16 AM, Jerry Vonau <jvonau@shaw.ca> wrote:

Yea, revisor needs anaconda-runtime,
cat /usr/lib/revisor/scripts/F9-buildinstall | grep anaconda


Yes, but from what Jeroen has said, revisor will pull it in to satisfy
the need at CD build time, without it being listed in the ks file (and
therefore getting installed on the target system too...)



Revisor for Fedora 9 will not pull any required packages into the
composed tree anymore, and here's why;


F9-buildinstall shipped with Revisor in Fedora 9 takes additional
parameters, which are supposed to represent the repositories used during
the compose of the tree (e.g. Packages/ and repodata/). See the YUM
config file you used for the model in /etc/revisor/conf.d/.


The required packages for buildinstall to run completely have to exist
in these repositories but they would have to exist no matter if Revisor
wanted to pull them in the composed tree or whether buildinstall can
pull them from the repositories directly.


Hence the log-file is of interest to me ;-)


Anaconda-runtime needs to exist in the repo that you use for the compose,
but doesn't need to be in the kickstart file. Too bad, you have to add
anaconda-runtime to the kickstart file, to get the package into the compose
repo, in order to use it later in buildinstall.


Well, that's supposed to be true for pungi, not true for revisor.

As far as I understand anyway :-) Jeroen has asked for logs and I'm
collecting some right now...



Yes, anaconda-runtime needs to exist in the repositories you use. Again
whether Revisor looks to these repositories for required packages, or
whether buildinstall does doesn't matter in this aspect.


However, you should not be required you to add it to the kickstart's
package manifest. Apparently though, since it does work with
anaconda-runtime listed in the package manifest I'm confused because the
package seems to be available from the repositories but buildinstall
can't seem to find it, judging from Martin's earlier message.


Kind regards,

Jeroen van Meeuwen
-kanarip

--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
 
Old 09-19-2008, 10:37 AM
"Martin Langhoff"
 
Default Revisor / yum oddity: anaconda-runtime

On Fri, Sep 19, 2008 at 10:23 PM, Jeroen van Meeuwen
<kanarip@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!)

cheers,


m
--
martin.langhoff@gmail.com
martin@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

--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
 
Old 09-20-2008, 11:20 AM
Jeroen van Meeuwen
 
Default Revisor / yum oddity: anaconda-runtime

Jerry Vonau wrote:

Martin Langhoff wrote:

On Fri, Sep 19, 2008 at 10:23 PM, Jeroen van Meeuwen
<kanarip@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

--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
 

Thread Tools




All times are GMT. The time now is 06:46 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org