http://qa.mandrakesoft.com/show_bug.cgi?id=6056


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEEDINFO
     Ever Confirmed|                            |1




------- Additional Comments From [EMAIL PROTECTED]  2003-06-10 04:01 -------
Ok, I build an 9.2 urpmi with smal fixes for 9.1, can you try it, I put it in
unsupported (perl-URPM-0.94-6_91mdk and urpmi-4.4-38_91mdk).

It should have the fix for curl proxy problems as well as many others problems
fixed.

-- 
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: NEEDINFO
creation_date: 
description: 
"urpmi.update --update" takes a lot of time to work (cca. 5-10 minutes) if URMP
has no proxy settings (file /etc/urpmi/proxy.cfg is empty), but there is
environment 'http_proxy' variable set (file /etc/profile.d/proxy.sh has proxy
definition).
That kind of configuration is needed because we have firewall, but Mdk updates
mirror location is on the local network (local mirror ftp server for Mandrake
updates).

I think that the problem is in calling 'culr' command, if there is no proxy
settings in file '/etc/urpmi/proxy.cfg'. Urmpi.update calls curl as follows:

/usr/bin/curl 0-s -I ftp://nanos/linux/distr/Mandrake/updates/9.1/base/hd

I think that there is invalid parameter '0-s', which maybe? it should be '-0
-s', but I can not see the whole command line with parameters of the running
process to see the whole picture.
In this situation probably curl uses parameter '0-s' as an URL, which must be
found, but '0-s' URL doesn't exist.

There is no problem to make 'urpmi.update', if URPMI update source resides on
the internet (e.g. ftp://mandrake.redbox.cz/...). In this situation URPM http
proxy must be set because of the firewall.

Maybe there is a bug in vendor perl module 'urpm.pm'?

Reply via email to