mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <rhi@pengutronix.de>
To: Olivier Croquette <ocroquette@free.fr>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Download issues (error 404), custom single mirror?
Date: Sun, 17 Feb 2019 21:32:40 +0100	[thread overview]
Message-ID: <20190217203240.6rwroaqv2kztl6gq@pengutronix.de> (raw)
In-Reply-To: <e555fc9c-7fb1-b459-48da-6750968678bd@free.fr>

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

On Sat, Feb 16, 2019 at 07:09:32PM +0100, Olivier Croquette wrote:
> Hello,
> 
> I am taking over a pretty old project based on PTXdist, and I have the
> problem that many components are not available online anymore, at least
> where PTXdist looks for them (memstat_0.8.tar.gz, netperf-2.7.0.tar.bz2...).
> So far, I was able to find these files by looking on the web, download them
> manually and put them in src/ to allow PTXdist to continue, but this is very
> cumbersome and prevents full automation.
> 
> Is there a way to specify a single custom mirror (HTTP or file based) for
> all packages? That would allow to put all files in a central, safe,
> future-proof location.
> 
> Also, does anyone know where the list of mirrors for the different packages
> is?
> 
> Thank you in advance for your help!
> 
> Regards
> Olivier
> 
> 
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de

-- 
Roland Hieber                     | r.hieber@pengutronix.de     |
Pengutronix e.K.                  | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim | Phone: +49-5121-206917-5086 |
Amtsgericht Hildesheim, HRA 2686  | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2019-02-17 20:32 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 [this message]
2019-02-18 20:04   ` Ian Abbott
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=20190217203240.6rwroaqv2kztl6gq@pengutronix.de \
    --to=rhi@pengutronix.de \
    --cc=ocroquette@free.fr \
    --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