From: Mark Wielaard <mark@klomp.org>
To: Frank Nguyen via RT <aarch64-hosting-request@osuosl.org>
Cc: buildbot@sourceware.org
Subject: Re: [support.osuosl.org #32565] AARCH64 OpenStack Request: sourceware - GNU Toolchain Infrastructure builder
Date: Tue, 12 Jul 2022 01:32:59 +0200 [thread overview]
Message-ID: <YsyzK1CbMjHdWYiw@wildebeest.org> (raw)
In-Reply-To: <rt-4.0.4-50580-1657579635-97.32565-6-0@osuosl.org>
Hi Frank,
On Mon, Jul 11, 2022 at 03:47:15PM -0700, Frank Nguyen via RT wrote:
> Your machine is ready on 140.211.167.69.
Thanks. I found the fedora account and could login and have sudo
access.
I see the machine has Fedora 32 installed. Can we just upgrade to
Fedora 36 using normal sudo dnf system-upgrade ... or is there a
different procedure to do that?
Thanks,
Mark
next prev parent reply other threads:[~2022-07-11 23:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <RT-Ticket-32565@osuosl.org>
2022-06-07 23:03 ` AARCH64 OpenStack Request Form Mark Wielaard
[not found] ` <rt-4.0.4-89118-1654643049-1349.32565-4-0@osuosl.org>
[not found] ` <DM5PR01MB26184D95E08A00402DBBDD4DCFA59@DM5PR01MB2618.prod.exchangelabs.com>
2022-06-07 23:22 ` [support.osuosl.org #32565] " via RT
[not found] ` <rt-4.0.4-90590-1654644173-1711.32565-6-0@osuosl.org>
2022-06-07 23:39 ` [support.osuosl.org #32565] AARCH64 OpenStack Request: sourceware - GNU Toolchain Infrastructure builder Lance Albertson via RT
[not found] ` <rt-4.0.4-93713-1654645166-610.32565-6-0@osuosl.org>
2022-07-11 22:47 ` Frank Nguyen via RT
2022-07-11 23:32 ` Mark Wielaard [this message]
2022-07-11 23:33 ` via RT
[not found] ` <rt-4.0.4-60212-1657582390-641.32565-6-0@osuosl.org>
2022-07-13 21:32 ` Lance Albertson via RT
2022-07-14 9:30 ` Mark Wielaard
2022-07-14 9:30 ` via RT
[not found] ` <rt-4.0.4-131659-1657791042-1428.32565-6-0@osuosl.org>
2022-07-14 20:54 ` Lance Albertson via RT
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=YsyzK1CbMjHdWYiw@wildebeest.org \
--to=mark@klomp.org \
--cc=aarch64-hosting-request@osuosl.org \
--cc=buildbot@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).