Mailinglist Archive: zypp-devel (39 mails)

[Jano Kupec <jkupec@xxxxxxx>]

On 05/03/2010 06:58 PM, Scott Bahling wrote:
> On Mon, 2010-05-03 at 12:09 +0200, Michael Andres wrote:
> > On Friday 30 April 2010 16:55:53 Michael Schroeder wrote:
> > > On Fri, Apr 30, 2010 at 04:45:31PM +0200, Scott Bahling wrote:
> > > > I am trying to register a repository that sits behind an https:// URL
> > > > and requires authentication. zypper appears to automatically detect such
> > > > URLs as services instead of repositories.
> > >
> > > What's the zypper command you're using to register the repo?
> >
> > If it was 'zypper ar', please open a bugreport and attach the zypp.log.
>
> I realize now that the problem is more fundamental. I am trying to
> register a repository on a server that uses iChain authentication. Is
> this possible with zypper? If yes, how/where is the login information
> registered?
>
> > From what I can tell, the standard https://user:password@server URI will
> not work.

It should. If it doesn't, we need to take a look at it, and we need
zypper.log. Since this is an http(s) problem, running zypper with
ZYPP_MEDIA_CURL_DEBUG=2 could provide even more info:

$ zypper ar https://user:password@server myrepo
$ ZYPP_LOGFILE=zypper.log ZYPP_MEDIA_CURL_DEBUG=2 zypper ref myrepo

and attach the log. Even though zypper now uses aria, curl is still used
for some requests (e.g. to check whether the remote file exists), that's
why the curl debug variable.

-- 
cheers,
jano


 Ján Kupec
 YaST team
---------------------------------------------------------(PGP)---
 Key ID: 637EE901
 Fingerprint: 93B9 C79B 2D20 51C3 800B  E09B 8048 46A6 637E E901
---------------------------------------------------------(IRC)---
 Server: irc.freenode.net
 Nick: jniq
 Channels: #zypp #yast #suse #susecz
---------------------------------------------------------(EOF)---