https://bugzilla.redhat.com/show_bug.cgi?id=1826621
Neil Horman <nhorman(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |needinfo?(arunprabhu.vijaya
| |n(a)intel.com)
--- Comment #15 from Neil Horman <nhorman(a)redhat.com> ---
Hello again, in response:
1) go-rpm-macros - Yes, I checked, and F30 did not yet, package the
go-rpm-macros. You can either:
a) Upgrade to Fedora 32
b) install the go-rpm-macro package directly from this url on your F30 box:
https://dl.fedoraproject.org/pub/fedora/linux/releases/32/Everything/x86_...
Note: There may be some other dependency (functional or explicit), so
this may not work, but its probably worth trying
c) Follow the new packager process, in particular this step:
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers#In...
which will allow you to submit builds to the koji build service that the
fedora project maintains
I would suggest that you do either (a) or (b) AND (c). I say that because, as
we go through this process, you will become the rmd co-maintainer along with
me, and as such you will want to be able to do builds as part of your
maintenance responsibilities anyway.
2) Its functional, but not the proscribed method for doing this. According to:
https://docs.fedoraproject.org/en-US/packaging-guidelines/Scriptlets/
you should just add a BuildRequries: systemd-rpm-macros
and for your scriptlets add:
%post
%systemd_post rmd.service
%preun
%systemd_preun rmd.service
Those scriptlets will take care of the appropriate actions for systemd units
(including stopping the service prior to removal and such). Theres no need to
write your own script for it.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component