Bug 1315629 - /usr/share/selinux/devel/include/roles/unconfineduser.if: Syntax error
Summary: /usr/share/selinux/devel/include/roles/unconfineduser.if: Syntax error
Keywords:
Status: CLOSED DUPLICATE of bug 1319338
Alias: None
Product: Fedora
Classification: Fedora
Component: policycoreutils
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Petr Lautrbach
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-08 09:42 UTC by Ralf Corsepius
Modified: 2016-04-08 18:51 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-08 18:51:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ralf Corsepius 2016-03-08 09:42:06 UTC
Description of problem:

On f24:

# dnf update
...
  Upgrading   : selinux-policy-devel-3.13.1-176.fc24.noarch            77/422 
/usr/share/selinux/devel/include/roles/unconfineduser.if: Syntax error on line 706 unconfined_t [type=IDENTIFIER]
/usr/share/selinux/devel/include/contrib/docker.if: Syntax error on line 503 docker_t [type=IDENTIFIER]
...


# dnf reinstall selinux-policy-devel
...
Reinstalling: selinux-policy-devel-3.13.1-176.fc24.noarch                                                           1/2 
/usr/share/selinux/devel/include/roles/unconfineduser.if: Syntax error on line 706 unconfined_t [type=IDENTIFIER]
/usr/share/selinux/devel/include/contrib/docker.if: Syntax error on line 503 docker_t [type=IDENTIFIER]

Comment 1 Richard W.M. Jones 2016-03-21 11:38:07 UTC
Same thing observed with selinux-policy-devel-3.13.1-179.fc25.noarch

Comment 2 Ben Cardoen 2016-04-02 06:03:10 UTC
I have the same problem, with
selinux-policy-devel-3.13.1-180.fc25.noarch

Comment 3 Miroslav Grepl 2016-04-04 08:27:55 UTC
This is known issue. See

https://github.com/fedora-selinux/selinux/pull/21

Comment 4 Petr Lautrbach 2016-04-08 18:51:43 UTC

*** This bug has been marked as a duplicate of bug 1319338 ***


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