Bug 703235 - sblim-sfcb not enabled after F14->F15 upgrade
Summary: sblim-sfcb not enabled after F14->F15 upgrade
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: sblim-sfcb
Version: 15
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Vitezslav Crhonek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: RejectedNTH https://fedoraproject.org...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-09 17:14 UTC by James Laska
Modified: 2013-09-02 06:56 UTC (History)
7 users (show)

Fixed In Version: sblim-sfcb-1.3.10-5.fc15
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-03 05:36:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description James Laska 2011-05-09 17:14:33 UTC
As the  states, sblim-sfcb is enabled and starts on boot in Fedora 14.  After upgrading to Fedora 15, sblim-sfcb is no longer enabled by default, and does not start on boot.  \n\nWhile the workaround is straight forward, I am proposing this as a NTH fix for F15 since this will likely impact F14->F15 users, and it's not obvious that the service isn't running.

Comment 1 Praveen K Paladugu 2011-05-09 18:44:54 UTC
The sblim-sfcb service shouldn't be started automatically with a fresh install of the package. The service will only be added for management with chkconfig with "chkconfig --add sblim-sfcb" in the %postinstall section.


The admin is expected to enable the service in the runlevels he/she wants the service to be running in.


A fresh install of sblim-sfcb package in F14 shouldn't automatically enable the sblim-sfcb service either.

Comment 2 Fedora Update System 2011-05-09 18:54:08 UTC
sblim-sfcb-1.3.10-5.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/sblim-sfcb-1.3.10-5.fc15

Comment 3 Adam Williamson 2011-05-09 19:19:48 UTC
not on the DVD, so nothing to be gained by making this NTH. -1



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 4 James Laska 2011-05-09 19:24:42 UTC
(In reply to comment #3)
> not on the DVD, so nothing to be gained by making this NTH. -1

I wasn't able to cross-reference the bugs with what packages are available on the DVD.  Given that this isn't provided on the DVD, I'm in perfect agreement that this can easily be addressed by a post-release update and does not affect the installation media in any way.

Adding whiteboard:RejectedNTH

Comment 5 James Laska 2011-05-09 19:54:10 UTC
(In reply to comment #1)
> A fresh install of sblim-sfcb package in F14 shouldn't automatically enable the
> sblim-sfcb service either.

Understood, but I believe if a system admin enables sblim-sfcb to start automatically, that change is expected to remain after upgrade.

Comment 6 Fedora Update System 2011-05-09 22:37:53 UTC
Package sblim-sfcb-1.3.10-5.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing sblim-sfcb-1.3.10-5.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/sblim-sfcb-1.3.10-5.fc15
then log in and leave karma (feedback).

Comment 7 Adam Williamson 2011-05-10 18:58:30 UTC
you also have to drop the blocks: f15-accepted when rejecting.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 8 James Laska 2011-05-24 13:26:09 UTC
I documented this issue as a CommonBug.  Please feel free to adjust/patch as needed.

https://fedoraproject.org/wiki/Common_F15_bugs#upgrade-disabled-services

Comment 9 Fedora Admin XMLRPC Client 2011-05-30 14:27:26 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 10 Fedora Update System 2011-06-03 05:36:00 UTC
sblim-sfcb-1.3.10-5.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.


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