Hello,

On Tue, Jan 12, 2021, at 10:58 AM, Vojtech Polasek wrote:
> Hello,
> 
> I would like to announce that a decision was made to discontinue 
> publishing of Scap Security Guide upstream releases in the Copr 
> repository [1]. Lately, maintaining these releases has started to be 
> more and more difficult, while the content of the scap-security-guide 
> package in this repository is actually identical to the content 
> published through Github release process, therefore it brings very low 
> benefit.
> 
> Therefore, if you use the repository to download upstream releases of 
> Scap Security Guide, you will not receive any further updates. I 
> recommend you to watch the Github repository [2] and download a zip 
> file provided with every release. The latest zip file is at [3].
> 
> If there is a need, instructions for creating your own Copr builds are 
> currently at [4].
> 
> I hope that this decision does not cause any inconvenience.
> 
> Best regards,
> 
> Vojta
> 

What was the common cause of failed build?  Seems like it could be 
automatically be built as part of the release tooling.

V/r,
James Cassell


> 
> 
> [1]: https://copr.fedorainfracloud.org/coprs/openscapmaint/openscap-latest/
> 
> [2]: https://github.com/ComplianceAsCode/content
> 
> [3]: 
> https://github.com/ComplianceAsCode/content/releases/download/v0.1.53/scap-security-guide-0.1.53.zip
> 
> [4]: 
> https://github.com/ComplianceAsCode/content/blob/master/release_tools/README.md
> 
> 
> 
> 
> 
> 
> 
> -- 
> Vojtech Polasek 
> 
> Software engineer, security compliance 
> 
> Red Hat  <https://www.redhat.com/> 
> 
> [email protected]   
> 
>  <https://www.redhat.com/> 
_______________________________________________
scap-security-guide mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/[email protected]

Reply via email to