public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: R0b0t1 <r030t1@gmail.com>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] emerge firefox-52.4.0 compile failure
Date: Mon, 9 Oct 2017 18:47:32 -0500	[thread overview]
Message-ID: <CAAD4mYjpSn3FJ4iA0zeYqGbKuNsuy+rmS_BGN6HtkGxD9Hkk5w@mail.gmail.com> (raw)
In-Reply-To: <orfvvu$lsv$1@blaine.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 772 bytes --]

On Monday, October 9, 2017, Grant Edwards <grant.b.edwards@gmail.com> wrote:
> On 2017-10-09, allan gottlieb <gottlieb@nyu.edu> wrote:
>
>> This is a know bug see https://bugs.gentoo.org/633790
>
> Yep, that's it.  Yet when you search for roundingflags or
> shapedtextflags in Gentoo's bugzilla, it finds nothing.  Has the
> search feature in Bugzilla ever worked?
>

It's pretty limited. You might notice developers renaming bugs - this is
why. They usually include the full package name and version in their
rename, as well as the exact text from the last or most important error
encountered.

I filed a bug against nvidia-drivers last night which was a duplicate of
something that came up in the automatic search. It's hard to canvas the
tracker exhaustively.

R0b0t1.

[-- Attachment #2: Type: text/html, Size: 1002 bytes --]

  reply	other threads:[~2017-10-09 23:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-08  2:51 [gentoo-user] emerge firefox-52.4.0 compile failure Grant Edwards
2017-10-08  9:05 ` Mick
2017-10-08 17:02   ` [gentoo-user] " Grant Edwards
2017-10-08 18:23     ` Mick
2017-10-08 18:54       ` Grant Edwards
2017-10-08 21:11         ` R0b0t1
2017-10-08 21:53           ` Grant Edwards
2017-10-09  0:14             ` R0b0t1
2017-10-09  1:38               ` Grant Edwards
2017-10-09  2:16                 ` Grant Edwards
2017-10-09  2:34                   ` allan gottlieb
2017-10-09 14:10                     ` Grant Edwards
2017-10-09 23:47                       ` R0b0t1 [this message]
2017-10-10  0:57                         ` Grant Edwards
2017-10-10  5:16                           ` R0b0t1
2017-10-10 10:27                           ` Marc Joliet
2017-10-10 10:49                             ` Marc Joliet
2017-10-11 20:58               ` mad.scientist.at.large
2017-10-09 19:20   ` Grant Edwards
2017-10-10  9:19     ` Peter Humphrey
2017-10-10 10:11       ` Marc Joliet
2017-10-10 10:46     ` Neil Bothwick
2017-10-10 23:30       ` Peter Humphrey
2017-10-11  3:02         ` R0b0t1
2017-10-11  9:09           ` Peter Humphrey
2017-10-11 13:28           ` Grant Edwards

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=CAAD4mYjpSn3FJ4iA0zeYqGbKuNsuy+rmS_BGN6HtkGxD9Hkk5w@mail.gmail.com \
    --to=r030t1@gmail.com \
    --cc=gentoo-user@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