Bug 850302 - Introduce new systemd-rpm macros in rusers spec file
Summary: Introduce new systemd-rpm macros in rusers spec file
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rusers
Version: 18
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Honza Horak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 850016
TreeView+ depends on / blocked
 
Reported: 2012-08-21 14:05 UTC by Lukáš Nykrýn
Modified: 2012-11-01 15:08 UTC (History)
1 user (show)

Fixed In Version: rusers-0.17-70.fc18
Clone Of:
Environment:
Last Closed: 2012-11-01 15:08:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Lukáš Nykrýn 2012-08-21 14:05:12 UTC
Fedora 18 changes the way how to work with services in spec files. It introduces new macros - %systemd_post, %systemd_preun and %systemd_postun; which replace scriptlets from Fedora 17 and older (see https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd, https://bugzilla.redhat.com/show_bug.cgi?id=850016).

Comment 1 Honza Horak 2012-09-11 10:27:05 UTC
Committed in git, update will be made with other planned changes.

Comment 2 Fedora Update System 2012-09-25 12:10:53 UTC
rusers-0.17-70.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/rusers-0.17-70.fc18

Comment 3 Fedora Update System 2012-09-25 15:58:28 UTC
Package rusers-0.17-70.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing rusers-0.17-70.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-14763/rusers-0.17-70.fc18
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2012-10-04 11:53:08 UTC
rusers-0.17-71.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/rusers-0.17-71.fc18


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