From: Jim Watson <jim@amarooas.com.au>
To: gentoo-sparc@lists.gentoo.org
Subject: Re: [gentoo-sparc] GWN "Want ad" for sparc architecture testers
Date: Wed, 26 Sep 2007 19:41:59 +1000 [thread overview]
Message-ID: <46FA2967.7080901@amarooas.com.au> (raw)
In-Reply-To: <20070926000759.f1001a30.alex.buell@munted.org.uk>
Alex Buell wrote:
> Yes, I would be very much interested in testing and reporting problems
> with OpenOffice builds. That and the lack of a suitable Java VM on that
> platform is one of my biggest annoyances with the UltraSparc platforms.
>
There is information about testing OpenOffice.org here:
http://qa.openoffice.org/ooQAReloaded/Docs/QA-Reloaded-HowToStart.html
If a problem is found, the first step is to decide if it is "upstream"
or is it a problem for the distribution.
The best way to know this is to try and reproduce a problem in the
upstream build.
Google for "contrib/linuxsparc" for the upstream sparc binaries.
It is also needed to find if a problem is sparc related - test on
different platforms. I can help you with that.
There are currently not any bugs upstream that are specific to sparc.
I am not a gentoo user, but doing the upstream OOo port for sparc
jim
--
gentoo-sparc@gentoo.org mailing list
next prev parent reply other threads:[~2007-09-26 9:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 15:33 [gentoo-sparc] GWN "Want ad" for sparc architecture testers Ferris McCormick
2007-09-24 16:01 ` Alex Buell
2007-09-25 22:37 ` Jorge Manuel B. S. Vicetto
2007-09-25 23:07 ` Alex Buell
2007-09-26 9:41 ` Jim Watson [this message]
2007-09-26 13:25 ` Alex Buell
2007-09-26 14:49 ` Ferris McCormick
2007-09-27 7:16 ` Alex Buell
2007-09-27 10:29 ` Jim Watson
2007-09-27 13:40 ` Ferris McCormick
2007-09-26 20:49 ` Jim Watson
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=46FA2967.7080901@amarooas.com.au \
--to=jim@amarooas.com.au \
--cc=gentoo-sparc@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