Bug 850295

Summary: Introduce new systemd-rpm macros in riak spec file
Product: [Fedora] Fedora Reporter: Lukáš Nykrýn <lnykryn>
Component: riakAssignee: Peter Lemenkov <lemenkov>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 18CC: lemenkov
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: erlang-riak_search-1.3.2-1.fc19 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-15 23:31:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 850016    

Description Lukáš Nykrýn 2012-08-21 14:03:58 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 Peter Lemenkov 2013-01-22 13:49:23 UTC
WONTFIX (I need these patches to be available in all supported Fedora releases forst).

Comment 2 Fedora Update System 2013-08-06 18:36:18 UTC
erlang-riak_search-1.3.2-1.fc19, riak-1.3.2-1.fc19, erlang-R16B-01.1.fc19, erlang-riaknostic-1.1.0-1.fc19, erlang-sidejob-0.2.0-2.fc19, erlang-riak_kv-1.3.2-1.fc19, erlang-eleveldb-1.3.2-1.fc19, erlang-riak_core-1.3.2-1.fc19, erlang-riak_pipe-1.3.2-1.fc19, erlang-bitcask-1.6.3-1.fc19, erlang-riak_api-1.3.2-2.fc19, erlang-riak_control-1.3.2-3.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/riak-1.3.2-1.fc19,erlang-R16B-01.1.fc19,erlang-riak_search-1.3.2-1.fc19,erlang-riak_kv-1.3.2-1.fc19,erlang-riaknostic-1.1.0-1.fc19,erlang-sidejob-0.2.0-2.fc19,erlang-riak_control-1.3.2-3.fc19,erlang-riak_api-1.3.2-2.fc19,erlang-bitcask-1.6.3-1.fc19,erlang-riak_pipe-1.3.2-1.fc19,erlang-riak_core-1.3.2-1.fc19,erlang-eleveldb-1.3.2-1.fc19

Comment 3 Fedora Update System 2013-08-07 23:05:24 UTC
Package erlang-riak_search-1.3.2-1.fc19, riak-1.3.2-1.fc19, erlang-R16B-01.1.fc19, erlang-riaknostic-1.1.0-1.fc19, erlang-sidejob-0.2.0-2.fc19, erlang-riak_kv-1.3.2-1.fc19, erlang-eleveldb-1.3.2-1.fc19, erlang-riak_core-1.3.2-1.fc19, erlang-riak_pipe-1.3.2-1.fc19, erlang-bitcask-1.6.3-1.fc19, erlang-riak_api-1.3.2-2.fc19, erlang-riak_control-1.3.2-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 erlang-riak_search-1.3.2-1.fc19 riak-1.3.2-1.fc19 erlang-R16B-01.1.fc19 erlang-riaknostic-1.1.0-1.fc19 erlang-sidejob-0.2.0-2.fc19 erlang-riak_kv-1.3.2-1.fc19 erlang-eleveldb-1.3.2-1.fc19 erlang-riak_core-1.3.2-1.fc19 erlang-riak_pipe-1.3.2-1.fc19 erlang-bitcask-1.6.3-1.fc19 erlang-riak_api-1.3.2-2.fc19 erlang-riak_control-1.3.2-3.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-14411/riak-1.3.2-1.fc19,erlang-R16B-01.1.fc19,erlang-riak_search-1.3.2-1.fc19,erlang-riak_kv-1.3.2-1.fc19,erlang-riaknostic-1.1.0-1.fc19,erlang-sidejob-0.2.0-2.fc19,erlang-riak_control-1.3.2-3.fc19,erlang-riak_api-1.3.2-2.fc19,erlang-bitcask-1.6.3-1.fc19,erlang-riak_pipe-1.3.2-1.fc19,erlang-riak_core-1.3.2-1.fc19,erlang-eleveldb-1.3.2-1.fc19
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2013-08-15 23:31:22 UTC
erlang-riak_search-1.3.2-1.fc19, riak-1.3.2-1.fc19, erlang-R16B-01.1.fc19, erlang-riaknostic-1.1.0-1.fc19, erlang-sidejob-0.2.0-2.fc19, erlang-riak_kv-1.3.2-1.fc19, erlang-eleveldb-1.3.2-1.fc19, erlang-riak_core-1.3.2-1.fc19, erlang-riak_pipe-1.3.2-1.fc19, erlang-bitcask-1.6.3-1.fc19, erlang-riak_api-1.3.2-2.fc19, erlang-riak_control-1.3.2-3.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.