[Open-scap] new to oscap. Question about oscap results

[Shawn Wells]

On 11/7/12 3:53 AM, Simon Lukasik wrote:
> On 11/07/2012 02:24 AM, Shawn Wells wrote:
>> >On 11/4/12 4:27 AM, Simon Lukasik wrote:
>>> >>On 11/02/2012 06:48 PM, Shawn Wells wrote:
>>>>> >>> >On 10/23/12 3:49 PM, Shawn Wells wrote:
>>>>>>> >>>> >>On 10/23/12 9:42 AM, Simon Lukasik wrote:
>>>>>>>>> >>>>> >>>On 10/23/2012 05:20 AM, Shawn Wells wrote:
>>>>>>>>>>>>> >>>>>>> >>>> >Is there a BugZilla we can add ourselves to, to keep
>>>>>>>> >>>>>>>abreast of the
>>>>>>>>>>>>> >>>>>>> >>>> >latest activity on the issue?
>>>>>>>>>>>>> >>>>>>> >>>> >
>>>>>>>>> >>>>> >>>It is tracked within bug 829349.
>>>>>>> >>>> >>Thanks Simon! Much appreciated.
>>>>> >>> >
>>>>> >>> >Hi Guys, I'm trying to find the BZ for the OpenSCAP rebase in RHEL5....
>>>>> >>> >and failing. Does one exist? The closest I've found:
>>>>> >>> >https://bugzilla.redhat.com/show_bug.cgi?id=871120
>>>>> >>> >
>>> >>Yeah, the bug you are referring to seems to be the closest one.
>>> >>
>>> >>Though I am not sure whether the OpenSCAP upstream list is the right
>>> >>place to answer questions regarding downstream products. :)
>> >
>> >Yes you are very much correct. Where should people go for such questions?
>> >
> I guess to the provider from which they get the product? In case of Red
> Hat Enterprise Linux use either customer portal
>
>    https://access.redhat.com/support/cases/new
>
> or your account representative.
>
> It may sound like a bureaucracy, but having a request officially tracked
> has a lot of advantages for both, the customer and the engineering
> group. I have learned the hard way.
>
> Of course, if someone finds a bug in upstream OpenSCAP release, he or
> she is more than welcome to report it and I encourage him/her to report
> it here. But I would like to see this mailing list focused on upstream
> development. Especially when there are better tools for the downstream.
I wasn't sure of there was a separate list tracking the RHEL OpenSCAP 
work vs the upstream work done here. Thanks for pointing me in the right 
direction!