Bug 1343 - Cannot access online media when behind a proxy
Summary: Cannot access online media when behind a proxy
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: Release (media or process) (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-19 15:05 CEST by Daniel Le Berre
Modified: 2011-10-11 12:38 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Daniel Le Berre 2011-05-19 15:05:06 CEST
Description of problem:

I updated a MDV 2010.2 with a Mageia 1 RC on a computer that is behind a proxy.

It looks like the package manager cannot access the internet when the computer is behind a proxy:
- during update, the installer failed to retrieve the list of media from the net
- when using the media manager, I got the following error message when trying to add manually the new media:

Impossible d'ajouter le média, erreurs rapportées :

impossible d'analyser media.cfg

Média : distrib ()

I tried with curl and wget, none of them is working.

Version-Release number of selected component (if applicable):

MGA 1 RC

How reproducible:

Always
Comment 1 Daniel Le Berre 2011-05-19 16:10:17 CEST
Additional informations:

-After a while, I was able to get Mandriva sources from the media manager??? I do not understand why. I did not really change anything.

- Using a urpmi.addmedia -distrib with a mageia mirror fixed the problem

I installed successfully 2 MGA 1 RC before that one without any problem. The only difference here is the proxy. But I do not understand why I observed that behavior.
Comment 2 Dave Hodgins 2011-05-19 23:44:18 CEST
I expect this is due to dsn lookups failing in the installer.
See https://bugs.mageia.org/show_bug.cgi?id=1319

CC: (none) => davidwhodgins

Comment 3 Daniel Le Berre 2011-05-20 07:49:32 CEST
ok, I see that mga servers have been also down for a while yesterday. I launched the installation around 2pm, so I got that error about 3pm. It might also be related to that.
Comment 4 Ahmad Samir 2011-06-16 20:24:01 CEST
Is this one still valid?
Comment 5 Manuel Hiebel 2011-10-11 12:38:24 CEST
 (In reply to comment #4)
> Is this one still valid?
no news, closing

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.