From: James McMechan <james_mcmechan@hotmail.com>
To: "gentoo-dev@lists.gentoo.org" <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Call for help in testing - sparc + gnutls-3.5
Date: Sun, 16 Jul 2017 16:11:01 +0000 [thread overview]
Message-ID: <MWHPR10MB1534DC381D7D77B836B6B8F3E2A30@MWHPR10MB1534.namprd10.prod.outlook.com> (raw)
In-Reply-To: <CAEdQ38E4WJhuJfxBKoK3iSctOfyADJO+y4pKC+d84T9A-BdH5A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
Hi, Matt
I have been helping Alon with testing on one of my sparc boxes,
what is broken?
is there a log of #gentoo-sparc or a gentoo-sparc mailing list somewhere?
on a side note
where should I ask about a respin of the iso, the old kernel will crash if a ATI graphics card is present.
Thank you,
Jim McMechan
________________________________
From: Matt Turner <mattst88@gentoo.org>
Sent: Saturday, July 15, 2017 12:04 PM
To: gentoo development; Gentoo infra
Subject: Re: [gentoo-dev] Call for help in testing - sparc + gnutls-3.5
On Sat, Jul 15, 2017 at 11:33 AM, Alon Bar-Lev <alonbl@gentoo.org> wrote:
> Hello,
>
> I am looking for someone that is using gentoo on sparc and is willing to
> help out to resolve an issue[1] of gnutls-3.5 with sparc so that we can drop
> gnutls-3.3 from tree.
>
> I tried to create a bootable sparc qemu gentoo image and failed, so need
> someone with a live system.
>
> Regards,
> Alon
>
> [1] https://bugs.gentoo.org/show_bug.cgi?id=613418
I don't think our sparc box has been fixed (down since March).
Otherwise I would continue helping.
I'll ask in #gentoo-sparc for help.
[-- Attachment #2: Type: text/html, Size: 2303 bytes --]
prev parent reply other threads:[~2017-07-16 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-15 18:33 [gentoo-dev] Call for help in testing - sparc + gnutls-3.5 Alon Bar-Lev
2017-07-15 19:04 ` Matt Turner
2017-07-16 16:11 ` James McMechan [this message]
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=MWHPR10MB1534DC381D7D77B836B6B8F3E2A30@MWHPR10MB1534.namprd10.prod.outlook.com \
--to=james_mcmechan@hotmail.com \
--cc=gentoo-dev@lists.gentoo.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