Bug 1249137 - Obsolete selinux policy for xrootd
Summary: Obsolete selinux policy for xrootd
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xrootd
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mattias Ellert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1238407
TreeView+ depends on / blocked
 
Reported: 2015-07-31 15:26 UTC by Lukas Vrabec
Modified: 2015-08-17 19:09 UTC (History)
4 users (show)

Fixed In Version: xrootd-4.2.2-1.el5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-10 09:54:54 UTC


Attachments (Terms of Use)

Description Lukas Vrabec 2015-07-31 15:26:10 UTC
Description of problem:
Due to https://fedoraproject.org//wiki/Changes/SELinuxPolicyStoreMigration we test all packages shipping own SELinux policy.
Rules from xrootd policy must be in optional policy.
Also there is wrong rules related to logrotate

Version-Release number of selected component (if applicable):
xrootd-selinux-4.2.1-3.fc23.noarch

How reproducible:
Always

Steps to Reproduce:
1.dnf install xrootd-selinux
2.semodule -d logrotate


Actual results:
Disable logrotate failed

Expected results:
Disable logrotate will work

Attaching fix for this, via pull request: https://github.com/xrootd/xrootd/pull/272

Comment 1 Fedora Update System 2015-08-01 11:00:37 UTC
xrootd-4.2.2-1.el7 has been submitted as an update for Fedora EPEL 7.
https://admin.fedoraproject.org/updates/xrootd-4.2.2-1.el7

Comment 2 Fedora Update System 2015-08-01 11:00:44 UTC
xrootd-4.2.2-1.el5 has been submitted as an update for Fedora EPEL 5.
https://admin.fedoraproject.org/updates/xrootd-4.2.2-1.el5

Comment 3 Fedora Update System 2015-08-01 11:00:50 UTC
xrootd-4.2.2-1.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/xrootd-4.2.2-1.fc22

Comment 4 Fedora Update System 2015-08-01 11:00:57 UTC
xrootd-4.2.2-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/xrootd-4.2.2-1.fc21

Comment 5 Fedora Update System 2015-08-01 11:01:05 UTC
xrootd-4.2.2-1.fc23 has been submitted as an update for Fedora 23.
https://admin.fedoraproject.org/updates/xrootd-4.2.2-1.fc23

Comment 6 Fedora Update System 2015-08-01 11:01:11 UTC
xrootd-4.2.2-1.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/xrootd-4.2.2-1.el6

Comment 7 Fedora Update System 2015-08-01 17:41:42 UTC
Package xrootd-4.2.2-1.fc23:
* should fix your issue,
* was pushed to the Fedora 23 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing xrootd-4.2.2-1.fc23'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-12594/xrootd-4.2.2-1.fc23
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2015-08-10 09:54:54 UTC
xrootd-4.2.2-1.fc23 has been pushed to the Fedora 23 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2015-08-11 02:06:06 UTC
xrootd-4.2.2-1.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2015-08-11 02:13:28 UTC
xrootd-4.2.2-1.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2015-08-17 19:05:31 UTC
xrootd-4.2.2-1.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 12 Fedora Update System 2015-08-17 19:08:57 UTC
xrootd-4.2.2-1.el7 has been pushed to the Fedora EPEL 7 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 13 Fedora Update System 2015-08-17 19:09:02 UTC
xrootd-4.2.2-1.el5 has been pushed to the Fedora EPEL 5 stable repository.  If problems still persist, please make note of it in this bug report.


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