mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Ian Abbott <abbotti@mev.co.uk>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Download issues (error 404), custom single mirror?
Date: Mon, 18 Feb 2019 20:04:56 +0000	[thread overview]
Message-ID: <f3556ff9-c5b9-b104-7398-a544b22fd0ca@mev.co.uk> (raw)
In-Reply-To: <20190217203240.6rwroaqv2kztl6gq@pengutronix.de>

On 17/02/2019 20:32, Roland Hieber wrote:
> Hi,
> 
> You can adjust the list of mirrors in ptxdist setup -> Source Download.
> 
> If none of the URLs listed for a package can be found, ptxdist falls
> back to look for the tarball under
> https://public.pengutronix.de/mirror/software/ptxdist/temporary-src/ .
> In that case, we at Pengutronix have a very extensive collection of
> tarballs that were downloaded over the years, and if you have a list of
> packages that fail to download (e.g. through "ptxdist -k urlcheck", -k
> keeps going after an error), someone at PTX can put it there. I've
> already done this for memstat_0.8.tar.gz and netperf-2.7.0.tar.bz2, so
> these two should now be downloadable.
> 
>   - Roland

For what it's worth, with PTXdist 2019.01.0, I currently get urlcheck 
failures for:

libconfig-1.4.9.tar.gz
opkg-utils-0.3.6.tar.bz2

But I have local copies of both of those.

-- 
-=( Ian Abbott <abbotti@mev.co.uk> || Web: www.mev.co.uk )=-
-=( MEV Ltd. is a company registered in England & Wales. )=-
-=( Registered number: 02862268.  Registered address:    )=-
-=( 15 West Park Road, Bramhall, STOCKPORT, SK7 3JZ, UK. )=-

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2019-02-18 20:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-16 18:09 Olivier Croquette
2019-02-17 20:32 ` Roland Hieber
2019-02-18 20:04   ` Ian Abbott [this message]
2019-02-22  5:51     ` Michael Olbrich
2019-02-18 14:28 ` Alexander Dahl
2019-02-18 15:47   ` Michael Olbrich

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=f3556ff9-c5b9-b104-7398-a544b22fd0ca@mev.co.uk \
    --to=abbotti@mev.co.uk \
    --cc=ptxdist@pengutronix.de \
    /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