Bug 865252 - Move /usr/bin/jack_control to -dbus package
Summary: Move /usr/bin/jack_control to -dbus package
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: jack-audio-connection-kit
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Brendan Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-11 05:07 UTC by Brendan Jones
Modified: 2014-01-18 21:53 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-18 21:53:30 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Brendan Jones 2012-10-11 05:07:14 UTC 
Currently /usr/bin/jack_control resides in the -example-clients sub-package. It is used to start/stop jackdbus

Can we move it into the -dbus package? I'm happy to commit the change and push an update.
Comment 1 Orcan Ogetbil 2012-10-11 12:14:15 UTC 
Sure Brendan, go ahead. Thanks for asking.
Comment 2 Orcan Ogetbil 2012-10-18 12:19:17 UTC 
Do you think we should update README.Fedora, telling the user to add himself to the "audio" group in addition to the "jackuser" group? Since you will get your hands dirty this time, you might consider to slip this in.
Comment 3 Fedora End Of Life 2013-04-03 16:35:19 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
Comment 4 Fedora Admin XMLRPC Client 2013-11-03 18:55:53 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 5 Orcan Ogetbil 2014-01-18 21:53:30 UTC 
This was already fixed in 2012. Closing.
Note You need to log in before you can comment on or make changes to this bug.