From: Alexander Dahl <ada@thorsis.com>
To: distrokit@pengutronix.de
Subject: [DistroKit] [PATCH] doc: intro: Update URLs
Date: Mon, 31 Aug 2020 16:44:20 +0200 [thread overview]
Message-ID: <20200831144420.19479-1-ada@thorsis.com> (raw)
At least http://www.pengutronix.de/oselas/toolchain/ redirects to a
page, where the user gets a HTTP error 403.
The other URLs were just updated to the targets you get redirected to.
Note: none of those links connects you to
https://www.pengutronix.de/de/software/toolchain.html …
Signed-off-by: Alexander Dahl <ada@thorsis.com>
---
doc/intro.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/intro.rst b/doc/intro.rst
index b827834..5bd6461 100644
--- a/doc/intro.rst
+++ b/doc/intro.rst
@@ -16,7 +16,7 @@ Installing the BSP
------------------
DistroKit is built with ptxdist. In order to install ptxdist,
-`download the tarball <http://www.pengutronix.de/software/ptxdist/download/ptxdist-|ptxdistVendorVersion|.tar.bz2>`_
+`download the tarball <https://public.pengutronix.de/software/ptxdist/ptxdist-|ptxdistVendorVersion|.tar.bz2>`_
from the PTXdist Download Area.
Extract the tarball:
@@ -37,12 +37,12 @@ Installing the Toolchain
In order to build a BSP, you need a toolchain. The easiest way to get a
toolchain is to install the debian packages for OSELAS.Toolchain:
- `<http://www.pengutronix.de/oselas/toolchain/>`_
+ `<https://debian.pengutronix.de/>`_
If you want to build the toolchain yourself, you can download the
toolchain sources from
- `<http://www.pengutronix.de/oselas/toolchain/download/>`_
+ `<https://public.pengutronix.de/oselas/toolchain/>`_
and build them manually.
--
2.27.0
_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de
next reply other threads:[~2020-08-31 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 14:44 Alexander Dahl [this message]
2020-08-31 21:11 ` Roland Hieber
2020-09-01 6:16 ` Alexander Dahl
2020-11-01 8:37 ` Robert Schwebel
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=20200831144420.19479-1-ada@thorsis.com \
--to=ada@thorsis.com \
--cc=distrokit@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