Bug 1311334 - libsemanage-20160223 is available
Summary: libsemanage-20160223 is available
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: libsemanage
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Lautrbach
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-24 00:18 UTC by Upstream Release Monitoring
Modified: 2016-02-24 08:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-24 08:27:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2016-02-24 00:18:05 UTC
Latest upstream release: 20160223
Current version/release in rawhide: 2.5-1.fc24
URL: http://selinuxproject.org

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Comment 1 Upstream Release Monitoring 2016-02-24 00:18:34 UTC
Failed to kick off scratch build.

spectool was unable to grab new sources

old source: libsemanage-2.5.tar.gz
old sha256: 46e2f36254369b6e91d1eea0460c262b139361b055a3a67d3ceea2d8ef72e006

new source: ./libsemanage-2.5.tar.gz
new sha256: 46e2f36254369b6e91d1eea0460c262b139361b055a3a67d3ceea2d8ef72e006

Comment 2 Petr Lautrbach 2016-02-24 08:27:58 UTC
libsepol-2.5-1.fc24
libselinux-2.5-1.fc24
setools-3.3.8-10.fc24
libsemanage-2.5-1.fc24
policycoreutils-2.5-1.fc24
checkpolicy-2.5-1.fc24


Note You need to log in before you can comment on or make changes to this bug.