Bug 870579 - Jetty regularly breaks systemd-tmpfiles-setup.service by deleting user jetty
Summary: Jetty regularly breaks systemd-tmpfiles-setup.service by deleting user jetty
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: jetty
Version: 17
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Mikolaj Izdebski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-26 23:36 UTC by Hannes Frederic Sowa
Modified: 2013-06-13 14:18 UTC (History)
8 users (show)

Fixed In Version: 8.1.5-6
Clone Of:
Environment:
Last Closed: 2013-06-13 14:18:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Hannes Frederic Sowa 2012-10-26 23:36:01 UTC
Description of problem:
A broken trigger in the jetty package regularly removes the user jetty from the system thus breaking systemd-tmpfiles-setup.service:

[/etc/tmpfiles.d/jetty.conf:1] Unknown user 'jetty'.

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

How reproducible:
Happens on every upgrade of jetty.

Comment 1 Alek Paunov 2012-11-13 22:30:36 UTC
This is a side effect of bug 857708 (jetty rpm can not create jetty user and group with ids 110, e.g. because accidental uid/gid collision with previuosly installed packages)

Comment 2 Mikolaj Izdebski 2013-06-13 14:13:14 UTC
Fixed in jetty-8.1.5-6

Comment 3 Mikolaj Izdebski 2013-06-13 14:18:46 UTC
I believe that this bug is fixed in jetty-8.1.5-6,
which is available in updates for Fedora 18, so I am closing this bug now.

The build containing the fix can be found at Koji:
http://koji.fedoraproject.org/koji/buildinfo?buildID=358455

This bug was fixed in the next release of Fedora, and is not planned
to be fixed in the release it was filed against.  If you want this bug
to be fixed in updates for Fedora 17, please say so in a comment.
Otherwise you can update to the newer release of Fedora to get the fix.


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