public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: speakup@braille.uwo.ca
Subject: reporting bugs on gentoo
Date: Sun, 23 Sep 2007 13:49:34 -0500	[thread overview]
Message-ID: <20070923184934.GA6088@linux1> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, Sep 18, 2007 at 11:59:58PM -0500, Nick Gawronski wrote:
> Hi, I just tried using the latest gentoo 2.6.21 kernel using emerge and 
> genkernel and found out that my dectalk express does not work with this 
> kernel.  I am stuck with using the kernel and modules from the live CD 
> 2007.0 that is using 2.6.19.  Is there any plans to fix this issue?  Also, 
> What is the easiest and accessible way to report a bug in gentoo packages or 
> compilation errors that stop a package from compiling when using emerge? 

Hi Nick,

to report bugs on gentoo, open an account on http://bugs.gentoo.org.

Once that is done, we have a package called pybugz which is a python
script that is a command line interface to bugzilla.

It is not in the stable tree as of yet, so to get it, you have to do the
following:

echo www-client/pybugz >> /etc/portage/package.keywords
emerge pybugz

There is not a man page for it as of yet, so once it is installed, you
can use the --help option to find out the correct usage.

The command it gives you is bugz (spelled with z not s), so you can
type:

bugz --help

Let me know if you have any questions.

Thanks,

- ---
William Hubbs
gentoo accessibility team lead
williamh@gentoo.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFG9rU+blQW9DDEZTgRAgZEAJ9c//JLd7osPxoFuJg5BjmQJuctLQCfYd4Z
1+/OM6AMqH7FGHQqSVK9LjY=
=0hGR
-----END PGP SIGNATURE-----


                 reply	other threads:[~ UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20070923184934.GA6088@linux1 \
    --to=williamh@gentoo.org \
    --cc=speakup@braille.uwo.ca \
    /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).