docs.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: Quentin Schulz <foss@0leil.net>
To: docs@lists.yoctoproject.org, Jon Mason <jdmason@kudzu.us>,
	openembedded-core@lists.openembedded.org,
	bitbake-devel@lists.openembedded.org
Subject: Re: [docs] [PATCH 1/8] oeqa/manual: Fix no longer valid URLs
Date: Thu, 07 Oct 2021 18:15:28 +0200	[thread overview]
Message-ID: <B0A9ED6D-F661-4C4D-8FA4-C5FF536A915E@0leil.net> (raw)
In-Reply-To: <20211007150630.22138-2-jdmason@kudzu.us>

Hi Jon,

On October 7, 2021 5:06:23 PM GMT+02:00, Jon Mason <jdmason@kudzu.us> wrote:
>autobuilder.yoctoproject.org URLS no longer work.  Update them to a
>working location.
>
>Signed-off-by: Jon Mason <jdmason@kudzu.us>
>---
> meta/lib/oeqa/manual/eclipse-plugin.json | 6 +++---

We don't support the eclipse plugin anymore, I guess this is a file we forgot to remove?

Cheers,
Quentin

> 1 file changed, 3 insertions(+), 3 deletions(-)
>
>diff --git a/meta/lib/oeqa/manual/eclipse-plugin.json b/meta/lib/oeqa/manual/eclipse-plugin.json
>index d77d0e673b8b..6c110d0656ec 100644
>--- a/meta/lib/oeqa/manual/eclipse-plugin.json
>+++ b/meta/lib/oeqa/manual/eclipse-plugin.json
>@@ -44,7 +44,7 @@
>                     "expected_results": ""
>                 },
>                 "2": {
>-                    "action": "wget  autobuilder.yoctoproject.org/pub/releases//machines/qemu/qemux86/qemu (ex:core-image-sato-sdk-qemux86-date-rootfs-tar-bz2) \nsource /opt/poky/version/environment-setup-i585-poky-linux  \n\nExtract qemu with runqemu-extract-sdk /home/user/file(ex.core-image-sato-sdk-qemux86.bz2) \n/home/user/qemux86-sato-sdk  \n\n",
>+                    "action": "wget  https://downloads.yoctoproject.org/releases/yocto/yocto-$VERSION/machines/qemu/qemux86/ (ex:core-image-sato-sdk-qemux86-date-rootfs-tar-bz2) \nsource /opt/poky/version/environment-setup-i585-poky-linux  \n\nExtract qemu with runqemu-extract-sdk /home/user/file(ex.core-image-sato-sdk-qemux86.bz2) \n/home/user/qemux86-sato-sdk  \n\n",
>                     "expected_results": " Qemu can be lauched normally."
>                 },
>                 "3": {
>@@ -60,7 +60,7 @@
>                     "expected_results": ""
>                 },
>                 "6": {
>-                    "action": "(d) QEMU: \nSelect this option if you will be using the QEMU emulator. Specify the Kernel matching the QEMU architecture you are using. \n      wget  autobuilder.yoctoproject.org/pub/releases//machines/qemu/qemux86/bzImage-qemux86.bin \n      e.g: /home/$USER/yocto/adt-installer/download_image/bzImage-qemux86.bin  \n\n",
>+                    "action": "(d) QEMU: \nSelect this option if you will be using the QEMU emulator. Specify the Kernel matching the QEMU architecture you are using. \n      wget  https://downloads.yoctoproject.org/releases/yocto/yocto-$VERSION/machines/qemu/qemux86/bzImage-qemux86.bin \n      e.g: /home/$USER/yocto/adt-installer/download_image/bzImage-qemux86.bin  \n\n",
>                     "expected_results": ""
>                 },	
>                 "7": {
>@@ -247,7 +247,7 @@
>             "execution": {
>                 "1": {
>                     "action": "Clone eclipse-poky source.   \n    \n    - git clone git://git.yoctoproject.org/eclipse-poky  \n\n",
>-                    "expected_results": "Eclipse plugin is successfully installed  \n\nDocumentation is there. For example if you have release yocto-2.0.1 you will found on   http://autobuilder.yoctoproject.org/pub/releases/yocto-2.0.1/eclipse-plugin/mars/  archive with documentation like org.yocto.doc-development-$date.zip  \n  \n"
>+                    "expected_results": "Eclipse plugin is successfully installed  \n\nDocumentation is there. For example if you have release yocto-2.0.1 you will found on   https://downloads.yoctoproject.org/releases/yocto/yocto-2.0.1/eclipse-plugin/mars/  archive with documentation like org.yocto.doc-development-$date.zip  \n  \n"
>                 },
>                 "2": {
>                     "action": "Checkout correct tag.  \n\n    - git checkout <eclipse-version>/<yocto-version> \n\n",


  reply	other threads:[~2021-10-07 16:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-07 15:06 [PATCH 0/8] replace http with https for URLs Jon Mason
2021-10-07 15:06 ` [PATCH 1/8] oeqa/manual: Fix no longer valid URLs Jon Mason
2021-10-07 16:15   ` Quentin Schulz [this message]
2021-10-07 15:06 ` [PATCH 2/8] bitbake:toaster:test: Update SSTATE URL Jon Mason
2021-10-07 15:06 ` [PATCH 3/8] meta: replace http with https for URLs Jon Mason
2021-10-07 16:25   ` [docs] " Quentin Schulz
2021-10-07 15:06 ` [PATCH 4/8] yocto-bsp/poky: " Jon Mason
2021-10-07 16:27   ` [docs] " Quentin Schulz
2021-10-07 15:06 ` [PATCH 5/8] bitbake: " Jon Mason
2021-10-08  8:57   ` [docs] " Michael Opdenacker
2021-10-08  9:38   ` Richard Purdie
2021-10-07 15:06 ` [PATCH 6/8] documentation: " Jon Mason
2021-10-08  9:08   ` [docs] " Michael Opdenacker
2021-10-07 15:06 ` [PATCH 7/8] documentation: use YOCTO_DL_URL Jon Mason
2021-10-08 12:15   ` [docs] " Michael Opdenacker
2021-10-07 15:06 ` [PATCH 8/8] dev-manual: remove errant / Jon Mason
2021-10-08 12:19   ` [docs] " Michael Opdenacker

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=B0A9ED6D-F661-4C4D-8FA4-C5FF536A915E@0leil.net \
    --to=foss@0leil.net \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=docs@lists.yoctoproject.org \
    --cc=jdmason@kudzu.us \
    --cc=openembedded-core@lists.openembedded.org \
    /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;
as well as URLs for NNTP newsgroup(s).