Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Bark <martin@barkynet.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] axel: fixed package download issue
Date: Tue, 04 Feb 2014 00:00:41 +0000	[thread overview]
Message-ID: <52F02DA9.3000802@barkynet.com> (raw)
In-Reply-To: <20140202091052.64e36322@skate>

Thomas,

On 02/02/14 08:10, Thomas Petazzoni wrote:
> Dear Martin Bark,
>
> On Sat,  1 Feb 2014 12:46:58 +0000, Martin Bark wrote:
>> This patch updates axel.mk to download axel v2.4 from snapshot.debian.org.
>> The download from alioth.debian.org is currently broken resulting in a
>> malformed axel.2.4.tar.gz being downloaded and the build failing.  The
>> package is available instead from snapshot.debian.org.
>>
>> Signed-off-by: Martin Bark <martin@barkynet.com>
>
> As I explained, this problem is not specific to Axel, but to all
> package that download from Alioth. So I believe it would be better to
> have one single patch that changes all the Alioth URLs to other URLs,
> so that we can revert that single patch later on once Alioth is working
> again.
>
> Best regards,
>
> Thomas
>

Yes I agree.  I had not notice at first that all alioth was broken.  I 
see Ryan Barnett has submitted a patch to update all alioth urls now so 
hopefully that's will fix the issue.

Thanks

Martin

      reply	other threads:[~2014-02-04  0:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-01 12:46 [Buildroot] [PATCH 1/1] axel: fixed package download issue Martin Bark
2014-02-02  8:10 ` Thomas Petazzoni
2014-02-04  0:00   ` Martin Bark [this message]

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=52F02DA9.3000802@barkynet.com \
    --to=martin@barkynet.com \
    --cc=buildroot@busybox.net \
    /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