| 1 |
Hi, |
| 2 |
|
| 3 |
On Sunday 21 November 2010 09:45:46 Christopher Schwan wrote: |
| 4 |
> Hi, |
| 5 |
> |
| 6 |
> On Saturday 20 November 2010 20:16:04 François Bissey wrote: |
| 7 |
> > [...] |
| 8 |
> > |
| 9 |
> > I cannot reproduce the issue. ebuild fetch and emerge both work like a |
| 10 |
> > charm and download the file. |
| 11 |
> > Two possibilities: |
| 12 |
> > 1) temporary issues, you just fetch at the wrong time. |
| 13 |
> > 2) version of portage and list of FEAURES please |
| 14 |
> |
| 15 |
> Its indeed the portage version: |
| 16 |
> |
| 17 |
> - Portage 2.2.01.17168-prefix -> does not work |
| 18 |
> - Portage 2.1.8.3 -> works |
| 19 |
|
| 20 |
I experienced the following behavior: In a prefixed shell wget-1.12-r1 fails to |
| 21 |
download from gforge.inria.fr (complaining the server's certificate is self- |
| 22 |
signed), in a default shell it works both with wget-1.12-r{1,2}. |
| 23 |
|
| 24 |
Ralf: Please send us your output of |
| 25 |
|
| 26 |
emerge --info |
| 27 |
|
| 28 |
> |
| 29 |
> > Nevertheless we should change the SRC_URI to reflect the move to https. |
| 30 |
> > I will see to revbump to 1.5 as well. |
| 31 |
> > |
| 32 |
> > Francois |
| 33 |
> |
| 34 |
> Christopher |
Archives