Bug 963916 - please remove +x bit from systemd unit file
Summary: please remove +x bit from systemd unit file
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: trousers
Version: 19
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Steve Grubb
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-16 18:44 UTC by Zbigniew Jędrzejewski-Szmek
Modified: 2013-06-12 03:30 UTC (History)
4 users (show)

Fixed In Version: trousers-0.3.10-3.fc19
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-12 03:30:34 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Zbigniew Jędrzejewski-Szmek 2013-05-16 18:44:22 UTC 
The unit file is not executable, and should not be marked +x. C.f. https://fedoraproject.org/wiki/Packaging:Guidelines#File_Permissions.

-rwxr-xr-x. 1 root root 148 Feb 18 15:38 /usr/lib/systemd/system/tcsd.service
trousers-0.3.10-2.fc19.x86_64
Comment 1 Steve Grubb 2013-06-02 13:44:19 UTC 
New trousers package built to fix this issue.
Comment 2 Fedora Update System 2013-06-02 13:47:11 UTC 
trousers-0.3.10-3.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/trousers-0.3.10-3.fc19
Comment 3 Fedora Update System 2013-06-02 18:42:02 UTC 
Package trousers-0.3.10-3.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing trousers-0.3.10-3.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-9877/trousers-0.3.10-3.fc19
then log in and leave karma (feedback).
Comment 4 Fedora Update System 2013-06-12 03:30:34 UTC 
trousers-0.3.10-3.fc19 has been pushed to the Fedora 19 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.