Phil Schaffner wrote:
> Looks a lot like
> https://bugzilla.redhat.com/show_bug.cgi?id=458861
> that is marked "Status: RELEASE_PENDING", so one might expect a fix in 5.3.
>
> Added a note to the CentOS BZ and a link to CentOS to the upstream BZ.
>
>
Thanks Phil, that is good news indeed!
Hywe
Hywel Richards wrote:
> It looks like maybe I was right to be confused as to where to report
> bugs as now there are two different answers.
>
> Karanbir Singh wrote:
>> Hywel Richards wrote:
>>
>>> Is there some policy as to what to do and where to report the bug?
>>>
>> report it on bugs
It looks like maybe I was right to be confused as to where to report
bugs as now there are two different answers.
Karanbir Singh wrote:
> Hywel Richards wrote:
>
>> Is there some policy as to what to do and where to report the bug?
>>
>
> report it on bugs.centos.org unless you have a RH
Hywel Richards wrote:
> Is there some policy as to what to do and where to report the bug?
report it on bugs.centos.org unless you have a RHEL subscription and are
able to also reproduce the exact same issue under the exact same
conditions, in which case you should report it at bugzilla.redhat.c
Hywel Richards wrote:
> I'm a little confused about what you are supposed to do when you
> discover a bug with CentOS (and by implication RHEL).
>
> Is there some policy as to what to do and where to report the bug?
>
> It doesn't seem appropriate to report it to http://bugs.centos.org
> becaus
I'm a little confused about what you are supposed to do when you
discover a bug with CentOS (and by implication RHEL).
Is there some policy as to what to do and where to report the bug?
It doesn't seem appropriate to report it to http://bugs.centos.org
because CentOS is kept in-sync with the up
6 matches
Mail list logo
