From: Jonathan Callen <jcallen@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Sparse security announcements
Date: Mon, 12 Sep 2016 01:19:27 -0400 [thread overview]
Message-ID: <bd0ef21d-9011-5662-ad88-395c5bdfa9a6@gentoo.org> (raw)
In-Reply-To: <20160912034134.6024.33C8DBA9@matica.foolinux.mooo.com>
[-- Attachment #1.1: Type: text/plain, Size: 1115 bytes --]
On 09/11/2016 11:43 PM, Ian Zimmerman wrote:
> On 2016-09-11 11:02, Michael Orlitzky wrote:
>
>>> Most are indeed fixed in 6.9.4, but a few (2 or 3 out of
>>> the 10 or so) only in 7.x. Should a bug be filed?
>>>
>>
>> Sure, if for some reason our imagemagick isn't affected, it only takes a
>> second to mark the bug invalid. Better to play it safe.
>
> Done:
> https://bugs.gentoo.org/show_bug.cgi?id=593526
> https://bugs.gentoo.org/show_bug.cgi?id=593528
> https://bugs.gentoo.org/show_bug.cgi?id=593530
> https://bugs.gentoo.org/show_bug.cgi?id=593532
>
> (Hmm. Are only even numbers assigned as Bug IDs?)
>
At one point, there were two bugzilla servers that synchronized bugs
between each other. If you got one of the servers, all new bugs would
be even. If you got the other, all new bugs would be odd. This was to
avoid having to check with the other server every time a new bug was
created (to ensure that a duplicate number was not assigned). I don't
know if this is still the case, or just a configuration remnant from
when it was an issue.
--
Jonathan Callen
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 829 bytes --]
next prev parent reply other threads:[~2016-09-12 5:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-10 23:11 [gentoo-user] Sparse security announcements Ian Zimmerman
2016-09-10 23:47 ` Michael Orlitzky
2016-09-11 4:48 ` [gentoo-user] " Ian Zimmerman
2016-09-11 15:02 ` Michael Orlitzky
2016-09-12 3:43 ` Ian Zimmerman
2016-09-12 5:19 ` Jonathan Callen [this message]
2016-09-10 23:48 ` [gentoo-user] " Rich Freeman
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=bd0ef21d-9011-5662-ad88-395c5bdfa9a6@gentoo.org \
--to=jcallen@gentoo.org \
--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