[tools] mrepo now has YOU support

[Nicole Hähnel]

Dag Wieers schrieb:
> On Fri, 9 Nov 2007, Nicole Hähnel wrote:
>
>   
>> Dag Wieers schrieb:
>>     
>>> On Fri, 2 Nov 2007, Nicole Hähnel wrote:
>>>       
>>>> Dag Wieers schrieb:
>>>>
>>>>         
>>>>> To prove that I am still alive and the tool is still evolving, I just
>>>>> added YOU support (in the form of a youget program) to download updates
>>>>> from a YOU (Yast Online Update) support.
>>>>>
>>>>> This means that it is (theoretically) possible to download updates for
>>>>> NLD9, SLES9 and possibly some other SuSE distributions with mrepo.
>>>>>
>>>>> It works for me on NLD9 and I need people to test it for the other
>>>>> distributions. Documentation is included.
>>>>>
>>>>> The youget tool currently does not have proxy-support and does not have
>>>>> exception-handling (eg. for network problems etc...). If you have
>>>>> problems, please let me know so we can strengthen the codebase.
>>>>>
>>>>> http://dag.wieers.com/blog/content/mrepo-now-with-you-yast-online-update-support
>>>>>           
>>>> I tried mrepo with you on an OpenEnterprise 2 (SLES10) server,
>>>> but I get an error:
>>>>
>>>> oes2:/etc/mrepo.conf.d # mrepo -u
>>>> sles10-i586: Updating SuSE Linux Enterprise Server 10 SP1 (i586)
>>>> youget: HTTP Error 401: digest auth failed
>>>> mrepo: Mirroring failed for
>>>> you://update.novell.com/repo/$RCE/SLES10-Updates/sles-10-i586/ with
>>>> message:
>>>>  Failed with return code: 256
>>>> oes2:/etc/mrepo.conf.d #
>>>>
>>>> Deviceid and secret files copied to /srv/mrepo/sles10-i586.
>>>> Any suggestions?
>>>>
>>>>         
>>> I haven't tested it myself for OES but it is possible and likely that the
>>> YOU location for OES is different than the one for SLES10.
>>>
>>> One way to find out is to use ssltap to work as a ssl-proxy to the YOU
>>> server. That way you can spy on the communication between YaST and the YOU
>>> server.
>>>
>>> The digest auth failed can mean one of two things:
>>>
>>>  - either the credentials do not exist at the YOU server (meaning that the
>>>    system credentials wer not properly registered at Novell or there was
>>>    no subscription to the Updates 'channel')
>>>
>>>  - or the wrong location is being used
>>>
>>> Since each different (channel) subscription means you have access to a
>>> single location, it is not possible to make a distinction between the
>>> wrong location or bad credentials :/
>>>
>>> Thanks for testing !
>>>       
>> it works with OES2 servers on SLES10SP1.
>> I only had the wrong urls.
>>
>> updates = you://nu.novell.com/repo/$RCE/SLES10-SP1-Updates/sles-10-$arch/
>> updatesoes = you://nu.novell.com/repo/$RCE/OES2-Updates/sles-10-$arch/
>>     
>
> Great feedback, Nicole.
>
> Are you sure that you need the updates channel as well ? I would expect
> (but could be terribly wrong) that the OES updates include the OS updates
> (as OES includes the OS).
>
> The reason why I am asking is because I would like to understand whether
> OES is a seperate distribution or not. I think it is, but if you still
> need the SLES10 updates channel, maybe I should make OES just a SLES10
> repository.
>
> What do you think based on your experience ?
>
> PS Thanks for getting back, I was wondering this morning in the shower
> what happened ans was going to contact you later today :)
>
>   

You're right for the first version of OES.
There is only one update channel which includes both update packages, 
for OES and SLES9.

OES2 is an add-on which can be included during the installation of 
SLES10 SP1.
So OES2 is not included in SLES10 like OES in SLES9.
Furthermore the update agent ZMD shows to channels for updates 
(OES2-Updates and SLES10SP1-Updates).

Nicole