From: Patrick Williams <patrick@stwcx.xyz>
To: Jonathan Arias <jonathanarias@gmail.com>
Cc: OpenBMC List <openbmc@lists.ozlabs.org>
Subject: Re: Updated links on dev-environment.md
Date: Tue, 31 May 2022 18:08:15 -0500 [thread overview]
Message-ID: <Ypaf3wQAL2qxrqf9@heinlein.stwcx.org.github.beta.tailscale.net> (raw)
In-Reply-To: <CAG3oxEfmZ2OsE=nGWXnD_4opkiKC7dMi7+wzqo_3dqN37aAT8g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
On Mon, May 30, 2022 at 12:56:54PM -0500, Jonathan Arias wrote:
Hello Jonathan,
Trimmed out a bit of your message and cc'd the ML. It's best to use the
ML for assistance.
> Anyway, I was following the guide here
> https://github.com/openbmc/docs/blob/master/development/dev-environment.md
> But some of the links for the toolchains are broken, was hoping you knew
> where I could find them?
>
> For example, this toolchain link is broken below.
>
> wget
> https://jenkins.openbmc.org/job/latest-master-sdk/label=docker-builder,target=romulus/lastSuccessfulBuild/artifact/deploy/sdk/oecore-x86_64-arm1176jzs-toolchain-nodistro.0.sh
>
> I went to https://jenkins.openbmc.org/job/latest-master-sdk/ to look for
> it, but that project is disabled, so no artifacts.
It looks like Andrew disabled this on 2022-04-09. I'm not sure the
reason why. Hopefully he can elaborate.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next parent reply other threads:[~2022-05-31 23:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAG3oxEfmZ2OsE=nGWXnD_4opkiKC7dMi7+wzqo_3dqN37aAT8g@mail.gmail.com>
2022-05-31 23:08 ` Patrick Williams [this message]
2022-06-01 14:13 ` Updated links on dev-environment.md Andrew Geissler
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=Ypaf3wQAL2qxrqf9@heinlein.stwcx.org.github.beta.tailscale.net \
--to=patrick@stwcx.xyz \
--cc=jonathanarias@gmail.com \
--cc=openbmc@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.