Hey,
I'm not certain this is the problem I'm having but:
when I run livecd-tools it hangs after "setting intervals between checks to 0 seconds".
If I wait long enough I get an error about mirrorlists and repo details not being able to be retrieved, so I'm assuming my problem is with the proxy server I'm behind. The details for the proxy are all set in yum, but does livecd-tools not make use of this?
Can anybody help me out a bit with this?
Thanks in advance :D
Jon
On Sat, 2007-11-24 at 16:35 +0000, Jonathan Roberts wrote:
I'm not certain this is the problem I'm having but:
when I run livecd-tools it hangs after "setting intervals between checks to 0 seconds".
If I wait long enough I get an error about mirrorlists and repo details not being able to be retrieved, so I'm assuming my problem is with the proxy server I'm behind. The details for the proxy are all set in yum, but does livecd-tools not make use of this?
We don't use the yum config on the system because doing so would make it difficult to have as full control over what's being created as would be liked. Also, it's often (?) the case that the live image you're creating isn't really related to what's running on the host.
The simplest way to get this to work would be to set the http_proxy environment variable which should then get picked up and used by yum. More than that is going to require adding some syntax (and thus require a little more thought)
Jeremy
On Mon, 2007-11-26 at 08:46 -0500, Jeremy Katz wrote:
On Sat, 2007-11-24 at 16:35 +0000, Jonathan Roberts wrote:
I'm not certain this is the problem I'm having but:
when I run livecd-tools it hangs after "setting intervals between checks to 0 seconds".
If I wait long enough I get an error about mirrorlists and repo details not being able to be retrieved, so I'm assuming my problem is with the proxy server I'm behind. The details for the proxy are all set in yum, but does livecd-tools not make use of this?
We don't use the yum config on the system because doing so would make it difficult to have as full control over what's being created as would be liked. Also, it's often (?) the case that the live image you're creating isn't really related to what's running on the host.
The simplest way to get this to work would be to set the http_proxy environment variable which should then get picked up and used by yum. More than that is going to require adding some syntax (and thus require a little more thought)
No, that solution's worked brilliantly :D
Thanks for your help...
Jon
Jeremy
-- Fedora-livecd-list mailing list Fedora-livecd-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list
Jeremy Katz wrote:
The simplest way to get this to work would be to set the http_proxy environment variable which should then get picked up and used by yum. More than that is going to require adding some syntax (and thus require a little more thought)
Is there any way to set http_proxy like this in a traditional anaconda install? I.e. doing something in %pre ?
-dmc
On Mon, 2007-11-26 at 12:23 -0600, Douglas McClendon wrote:
Jeremy Katz wrote:
The simplest way to get this to work would be to set the http_proxy environment variable which should then get picked up and used by yum. More than that is going to require adding some syntax (and thus require a little more thought)
Is there any way to set http_proxy like this in a traditional anaconda install? I.e. doing something in %pre ?
Not at present... it's one of the things that will hopefully be enabled in Fedora 9. See http://fedoraproject.org/wiki/Anaconda/Features/SecondStageInstallSource
Jeremy
livecd@lists.fedoraproject.org