Bug 682909

Summary: tinc rpm is not creating /etc/init.d/tinc daemon
Product: [Fedora] Fedora Reporter: Robert Townley <rob.townley>
Component: tincAssignee: Fabian Affolter <mail>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: mail
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 14:12:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
etc-initd-tincd.sh none

Description Robert Townley 2011-03-07 23:03:28 UTC 
Description of problem:
tinc package isn't creating a daemon script.

Version-Release number of selected component (if applicable):
1.0.12-1.fc14

How reproducible:


Steps to Reproduce:
1.yum -y install tinc
2.chkconfig | grep tinc
3.rpm --query --filesbypkg tinc
  
Actual results:
yum install shows success even though there is not /etc/init.d/tinc 
Not in rpm, otherwise rpm --query --filesbypkg tinc would have an /etc/init.d/tinc or /etc/rc.d/init.d/tinc

Expected results:
Installation of the package would add a tinc daemon to /etc/init.d/
The daemon script would show just like it does for the httpd package ala 'rpm --query --filesbypkg httpd | grep init'

Additional info:
i have numerous tinc.sh scripts i have used to start tinc that i will attach when i get to those machines at work which is kinda difficult since i don't have tinc running on this fresh install.
Comment 1 Robert Townley 2011-03-08 22:38:35 UTC 
Created attachment 483052 [details]
etc-initd-tincd.sh
Comment 2 Robert Townley 2011-03-08 22:40:22 UTC 
need to investigate github to see what happened to this init script.
Comment 3 Fabian Affolter 2011-06-30 09:01:22 UTC 
Maybe it would a good idea to move directly to systemd?
Comment 4 Fedora End Of Life 2012-08-16 14:12:17 UTC 
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping