Bug 831280 - jetty is running after upgrade to F-17
Summary: jetty is running after upgrade to F-17
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: jetty
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Stanislav Ochotnicky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-12 16:17 UTC by David Tardon
Modified: 2012-06-26 21:29 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-06-26 21:29:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description David Tardon 2012-06-12 16:17:39 UTC
Description of problem:
jetty.service is enabled and running after upgrade from F-16 to F-17 ,
but it is not listed between services allowed to run by default: https://fedoraproject.org/wiki/Starting_services_by_default .

Version-Release number of selected component (if applicable):
jetty-8.1.2-5.fc17.noarch

Comment 1 Stanislav Ochotnicky 2012-06-13 08:52:07 UTC
This was not intended for sure. I'll be fixing this ASAP

Comment 2 Fedora Update System 2012-06-15 14:24:40 UTC
jetty-8.1.2-9.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/jetty-8.1.2-9.fc17

Comment 3 Fedora Update System 2012-06-15 23:50:57 UTC
Package jetty-8.1.2-9.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing jetty-8.1.2-9.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-9506/jetty-8.1.2-9.fc17
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2012-06-26 21:29:55 UTC
jetty-8.1.2-9.fc17 has been pushed to the Fedora 17 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.