From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Download issues (error 404), custom single mirror?
Date: Fri, 22 Feb 2019 06:51:17 +0100 [thread overview]
Message-ID: <20190222055117.numne4fe4tyvfipp@pengutronix.de> (raw)
In-Reply-To: <f3556ff9-c5b9-b104-7398-a544b22fd0ca@mev.co.uk>
On Mon, Feb 18, 2019 at 08:04:56PM +0000, Ian Abbott wrote:
> On 17/02/2019 20:32, Roland Hieber wrote:
> > 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
That's one if the reasons why this package is in staging.
> opkg-utils-0.3.6.tar.bz2
This one works for me.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-02-22 5:51 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 [this message]
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=20190222055117.numne4fe4tyvfipp@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--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