CentOS - Jan 2015 - When will CentOS Publish Errata?

> 1.  Blatant screen scraping is a violation of the terms of service for RHN
..
> so where is a SOURCE of information for something like this:
>
> https://rhn.redhat.com/errata/RHSA-2014-2024.html
>
> If you read this:
> https://access.redhat.com/help/terms/
>
> then, one can not just grab all the info on that errata page and distribute
it ..
> which is why we LINK to it and not distribute it currently.
>
> So, the first issue is that one must find a source for the information that
would
> go into the 'updateinfo.xml' file that is always maintained and is
available to read
> and to redistribute.
>
> 2.  If someone comes up with a place to get said data, THEN we could
properly publish
> that data in some way.
>
> Thanks,
> Johnny Hughes
Can't we just ask Red Hat if it's OK for CentOS to use the data for its
updateinfo.xml?
Is there some official communication channel between the CentOS Project and Red
Hat?

On 2015-01-06, Somers-Harris, David | David | OPS
<david.somers-harris at mail.rakuten.com> wrote:
>> 1.  Blatant screen scraping is a violation of the terms of service
>> for RHN ..  so where is a SOURCE of information for something like
>> this:
>>
>> https://rhn.redhat.com/errata/RHSA-2014-2024.html
>>
>> If you read this: https://access.redhat.com/help/terms/
>>
>> then, one can not just grab all the info on that errata page and
>> distribute it ..  which is why we LINK to it and not distribute it
>> currently.
>>
>> So, the first issue is that one must find a source for the
>> information that would go into the 'updateinfo.xml' file that
is
>> always maintained and is available to read and to redistribute.
>>
>> 2.  If someone comes up with a place to get said data, THEN we could
>> properly publish that data in some way.
>>
>> Thanks, Johnny Hughes
>
> Can't we just ask Red Hat if it's OK for CentOS to use the data for
> its updateinfo.xml?  Is there some official communication channel
> between the CentOS Project and Red Hat?
Maybe you missed the big announcement:

http://lists.centos.org/pipermail/centos-announce/2014-January/020100.html

-- 

Liam

On 01/06/2015 04:25 AM, Liam O'Toole wrote:
> On 2015-01-06, Somers-Harris, David | David | OPS
> <david.somers-harris at mail.rakuten.com> wrote:
>>> 1.  Blatant screen scraping is a violation of the terms of service
>>> for RHN ..  so where is a SOURCE of information for something like
>>> this:
>>>
>>> https://rhn.redhat.com/errata/RHSA-2014-2024.html
>>>
>>> If you read this: https://access.redhat.com/help/terms/
>>>
>>> then, one can not just grab all the info on that errata page and
>>> distribute it ..  which is why we LINK to it and not distribute it
>>> currently.
>>>
>>> So, the first issue is that one must find a source for the
>>> information that would go into the 'updateinfo.xml' file
that is
>>> always maintained and is available to read and to redistribute.
>>>
>>> 2.  If someone comes up with a place to get said data, THEN we
could
>>> properly publish that data in some way.
>>>
>>> Thanks, Johnny Hughes
>>
>> Can't we just ask Red Hat if it's OK for CentOS to use the data
for
>> its updateinfo.xml?  Is there some official communication channel
>> between the CentOS Project and Red Hat?
> 
> Maybe you missed the big announcement:
> 
> http://lists.centos.org/pipermail/centos-announce/2014-January/020100.html
> 
Sure, but they aren't likely to let us.

The purpose of CentOS within the Red Hat ecosystem is explained here:

http://community.redhat.com/centos-faq/

CentOS is open source, so you can use it however you want and for what
ever you are comfortable using it for .. however, giving special
dispensation to violate terms of service of RHN to make CentOS more
usable than it already is in the enterprise is not high on their
priority list.

They are not taking any action to make it in any way less usable, but
they are also not going to do anything to make it easier either.

What we need is a way to get that info from another place.

Maybe the oval data, if it has all the required information and if the
Terms of Service allow for that.

Someone in the Community needs to research that and see if it is usable
or if there is some other source for the information that can then be
modified to create the updateinfo.xml file.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.centos.org/pipermail/centos/attachments/20150106/d4b6b55d/attachment-0001.sig>