Bug 1688905

Summary: libseccomp v2.4.0 released
Product: [Fedora] Fedora Reporter: Paul Moore <paul>
Component: libseccompAssignee: Paul Moore <paul>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 29CC: darunesh, extras-qa, paul
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: libseccomp-2.4.0-0.fc29 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1688902 Environment:
Last Closed: 2019-03-21 14:40:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1688902, 1688906    
Bug Blocks: 1688903, 1690897    

Description Paul Moore 2019-03-14 17:15:33 UTC
+++ This bug was initially created as a clone of Bug #1688902 +++

Description of problem:

New upstream version which adds new features and fixes a number of bugs in libseccomp.

* https://github.com/seccomp/libseccomp/releases/tag/v2.4.0

Comment 1 Fedora Update System 2019-03-14 20:08:38 UTC
libseccomp-2.4.0-0.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-e9dcc7806a

Comment 2 Fedora Update System 2019-03-15 17:57:22 UTC
libseccomp-2.4.0-0.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-e9dcc7806a

Comment 3 Paul Moore 2019-03-20 14:26:01 UTC
*** Bug 1690898 has been marked as a duplicate of this bug. ***

Comment 4 Fedora Update System 2019-03-21 14:40:55 UTC
libseccomp-2.4.0-0.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.