Leonid Flaks wrote:
Finally got some time to re-visit my problems.
Answering my own question. The correct variable to set up proxy is
indeed http_proxy (not just proxy).
I still can't figure out how to deal with doing reposync on the whole
repo, not just a list of rpms. yumdownloader likes to have implicit list
of files to download.
Is mirror location in the form of http:// supported in cobbler if RPMS
list is empty?
I am using cobbler 1.4.3 on fedora 10.
In short - if I enter http_proxy either by editing file in
/var/lib/cobbler/config/repos.d/ or using cobbler command and list rpms
to use it works as expected.
Ok, I would hope that yum reposync could also pull this from the
environment. This is something to look into.
If you set it with say, "export", it doesn't use this setting?
Michael DeHaan wrote:
>
>
>>> Edit your /var/lib/cobbler/config/repos.d/$name file and replace the
>>> "environment" variable section with just:
>>>
>>> environment: {}
>>>
>>>
>>>
>> If I do this, how would I set the proxy then?
>>
>> This should fix your problem and allow for other edits.
>>
>>
> You would clear it and then set it, and then thereafter setting it would
> work fine.
>
>
I tried to follow your advice, but see no difference. The environment
field (and it is the only one I noticed!) seems to change after saving
it in web interface.
I'll check this out...
>> Yes, other edits work, but they add more of {:} to
environment. If it is
>> empty to begin with, that it does not matter.
>>
>>
>>> Presumably this is because you were running 1.4.X previously, I've seen
>>> that some and there is not much we can do about it, but thankfully it's
>>> an easy fix.
>>>
>>> --Michael
>>>
>>>
>>>
>> I had cobbler version that came with fedora 10 first, then updated a few
>> times to what is now 1.4.3. Should I just wait for the next update?
>>
>>
> What would you be waiting for?
>
I am confused with version numbers here. I am using 1.4.3 now. Did you
mean to try it on 1.6.*? I'd rather wait for 1.6 to hit fedora 10
updates to give it another try.
Thanks!
I meant did you think there was something wrong with the field storage
in 1.4.3 still.
I think if you fix the config file it wouldn't do that again, though if
it /does/ that's a problem we need to fix.
You are correct, 1.6 is not released yet.