public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
From: Christopher Schwan <cschwan@students.uni-mainz.de>
To: <gentoo-science@lists.gentoo.org>
Subject: Re: [gentoo-science] Fetch failed for sci-libs/mpfi-1.4
Date: Sun, 21 Nov 2010 10:23:44 +0100	[thread overview]
Message-ID: <201011211023.44528.cschwan@students.uni-mainz.de> (raw)
In-Reply-To: <201011210945.46887.cschwan@students.uni-mainz.de>

Hi,

On Sunday 21 November 2010 09:45:46 Christopher Schwan wrote:
> Hi,
> 
> On Saturday 20 November 2010 20:16:04 François Bissey wrote:
> > [...]
> > 
> > I cannot reproduce the issue. ebuild fetch and emerge both work like a
> > charm and download the file.
> > Two possibilities:
> > 1) temporary issues, you just fetch at the wrong time.
> > 2) version of portage and list of FEAURES please
> 
> Its indeed the portage version:
> 
> - Portage 2.2.01.17168-prefix -> does not work
> - Portage 2.1.8.3 -> works

I experienced the following behavior: In a prefixed shell wget-1.12-r1 fails to 
download from gforge.inria.fr (complaining the server's certificate is self-
signed), in a default shell it works both with wget-1.12-r{1,2}.

Ralf: Please send us your output of

    emerge --info

> 
> > Nevertheless we should change the SRC_URI to reflect the move to https.
> > I will see to revbump to 1.5 as well.
> > 
> > Francois
> 
> Christopher



  reply	other threads:[~2010-11-21  9:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-20 13:36 [gentoo-science] Fetch failed for sci-libs/mpfi-1.4 forenhampel
2010-11-20 16:28 ` Christopher Schwan
2010-11-20 19:16   ` François Bissey
2010-11-21  8:45     ` Christopher Schwan
2010-11-21  9:23       ` Christopher Schwan [this message]
2010-11-21 12:19         ` forenhampel
2010-11-22  9:32           ` Christopher Schwan
2010-11-22 10:36             ` Christopher Schwan
2010-11-22 23:34               ` forenhampel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201011211023.44528.cschwan@students.uni-mainz.de \
    --to=cschwan@students.uni-mainz.de \
    --cc=gentoo-science@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox