[Bug 1051044] New: policycoreutils-2.2 changes syntax of semange fcontext -f option

bugzilla at redhat.com bugzilla at redhat.com
Thu Jan 9 15:48:55 UTC 2014


https://bugzilla.redhat.com/show_bug.cgi?id=1051044

            Bug ID: 1051044
           Summary: policycoreutils-2.2 changes syntax of semange fcontext
                    -f option
           Product: Fedora Documentation
           Version: devel
         Component: release-notes
          Severity: low
          Assignee: relnotes at fedoraproject.org
          Reporter: edgar.hoch at ims.uni-stuttgart.de
        QA Contact: docs-qa at lists.fedoraproject.org
                CC: relnotes at fedoraproject.org, wb8rcr at arrl.net,
                    zach at oglesby.co



Description of problem:
Since Fedora 20 the syntax of the command semanage fcontext option -f has
changed in an incompatible way to previous versions. I think that this change
should be noted in the updates to the Fedora 20 release notes.

In previous versions, the argument to semanage fcontext option -f was also
prefixed by a dash "-". In Fedora 20, the argument contains no dash, and the
char for "regular file" was changed from "-" to "f".

I think that the change is reasonable, because dashes in arguments are unsual
in linux / unix command lines. But the change is incompatible with previous
versions and breaks existing scripts, so I think the users and administrators
should be informed of that change!


It would be nice if the developers of semanage command would also accept the
old syntax, together with the new one, to be backward compatible - at least for
some time. But this is another point - not regarding the documentation.


Version-Release number of selected component (if applicable):
policycoreutils-2.2.5-1.fc20.x86_64

How reproducible:
Always.

Steps to Reproduce:
Compare the man page of "semanage" on
policycoreutils-python-2.1.14-46.6.fc19.x86_64 and of "semanage-fcontext" on
policycoreutils-2.2.5-1.fc20.x86_64 regarding option "-f" (filetype).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.


More information about the docs-qa mailing list