From: Alexander Dahl <ada@thorsis.com>
To: ptxdist@pengutronix.de
Cc: Olivier Croquette <ocroquette@free.fr>
Subject: Re: [ptxdist] Download issues (error 404), custom single mirror?
Date: Mon, 18 Feb 2019 15:28:19 +0100 [thread overview]
Message-ID: <1811398.Ayl94Fg3ty@ada> (raw)
In-Reply-To: <e555fc9c-7fb1-b459-48da-6750968678bd@free.fr>
Hei hei,
Am Samstag, 16. Februar 2019, 19:09:32 CET schrieb Olivier Croquette:
> 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.
At least in the first step. If you once got those tarballs and put it in the
right place, you don't need to fetch them again.
> 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.
You should keep and backup all the tarballs you need at your site. What we do:
ptxdist setup -> Source Directories
Set a path to a mounted network file system (cifs, nfs, etc.) and do a central
backup of that share.
> Also, does anyone know where the list of mirrors for the different
> packages is?
Not sure what you mean, but if you're looking for specific tarballs, buildroot
has an archive, too:
http://sources.buildroot.org/
Greets
Alex
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-02-18 14:28 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
2019-02-22 5:51 ` Michael Olbrich
2019-02-18 14:28 ` Alexander Dahl [this message]
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=1811398.Ayl94Fg3ty@ada \
--to=ada@thorsis.com \
--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