Please migrate libjetty-extra-java to tomcat7

Bug #1286779 reported by Hans Joachim Desserud on 2014-03-02
This bug affects 14 people
Affects Status Importance Assigned to Milestone
One Hundred Papercuts
jetty (Debian)
Fix Released
jetty (Ubuntu)
Timo Jyrinki

Bug Description

libjetty-extra-java still depends on libtomcat6-java which prevents it from being installed alongside other programs which depend on tomcat7. According to the Debian bug report, Eclipse is among these programs.

(Another it causes problems for is gradle which cannot currently be installed at the same time as tomcat7. Gradle's explicit dependency on tomcat6 has been removed (see bug 997743for details) and should have fixed it, but since gradle also depends on libjetty-extra-java the issue is still present. )

SRU for 14.04, debdiff in comment #11:

It is very hard to use this package in conjuction with relevant development tools because they depend on different versions on tomcat which means you can't install both.

[Test case]
For instance `sudo apt-get install eclipse libjetty-extra` will fail because eclipse wants tomcat7, but libjetty-extra-java currently needs tomcat6.

[Regression potential]
See analysis in comment #15 - there should not be regression potential.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libjetty-extra-java 6.1.26-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
Uname: Linux 3.13.0-6-generic i686
ApportVersion: 2.13.2-0ubuntu2
Architecture: i386
CurrentDesktop: Unity
Date: Sun Mar 2 11:48:27 2014
InstallationDate: Installed on 2013-10-26 (127 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20131021.1)
PackageArchitecture: all
SourcePackage: jetty
UpgradeStatus: No upgrade log present (probably fresh install)

Hans Joachim Desserud (hjd) wrote :
description: updated
description: updated
description: updated
tags: added: saucy
Changed in jetty (Debian):
status: Unknown → New
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in jetty (Ubuntu):
status: New → Confirmed

It severely affects packages beyond the one that causes the flaw.

Changed in jetty (Ubuntu):
importance: Undecided → Critical
status: Confirmed → Triaged
Changed in hundredpapercuts:
status: New → Triaged
importance: Undecided → Critical
Changed in jetty (Debian):
status: New → Fix Released
Artur Rona (ari-tczew) wrote :

This bug was fixed in the package jetty - 6.1.26-3
Sponsored for Hans Joachim Desserud (hjd)

jetty (6.1.26-3) unstable; urgency=low

  * Team upload.
  * d/jetty.init: variable $ROTATELOGS path chenged
    from /usr/sbin to /usr/bin (Closes: #719875)
  * Added Class-Path to jars to fix Lintian missing-classpath warning

 -- Eugene Zhukov <email address hidden> Tue, 22 Apr 2014 10:13:52 +0000

jetty (6.1.26-2) unstable; urgency=low

  * Team upload.
  * Bumped to Standard-Versions 3.9.5 - no changes required.
  * Switched to libtomcat7-java (Closes: #686876)
  * Added detection to init script for openjdk-8, openjdk-7
    and openjdk-6 multiarch installations (Closes: #675027)

 -- Eugene Zhukov <email address hidden> Fri, 11 Apr 2014 11:35:28 +0000

Changed in jetty (Ubuntu):
status: Triaged → Fix Released
Changed in hundredpapercuts:
status: Triaged → Fix Released
Egbert van der Wal (eggie) wrote :

The same thing is happening to me in Kubuntu Trusty:

$ sudo apt-get install libjetty-extra-java
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libjetty-extra-java : Depends: libtomcat6-java (>= 6.0.20-2) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

$ sudo apt-cache policy libjetty-extra-java
  Installed: (none)
  Candidate: 6.1.26-1ubuntu1
  Version table:
     6.1.26-1ubuntu1 0
        500 trusty/universe amd64 Packages

Any idea on when this updated package will make its way to the official repositories?

Thad Eirich (thad-eirich) wrote :

Hello, these changes still are not pushed to official repositories! I cannot install gradle because this dependency is conflicting with Eclipse & several other programs.

Bruno Medeiros (brunojcm) wrote :

Wow, this is bizarre.
The bug is "fixed", but nobody cares pushing it, so it's not actually fixed. Why do 99% and left 1% missing?

Bruno Medeiros (brunojcm) wrote :

This seems a reasoable workaround:

Xavier L. (xav0989) wrote :

Any update?

Klaus Ethgen (klaus+ubuntu) wrote :

May I ask what is the update of this bug? There is still only the broken package available in trusty.

Hans Joachim Desserud (hjd) wrote :

Hi all :)

For those wondering, a bug is considered fixed in Ubuntu once a fix for it is available in the current development release. However, if the bug is considered import (such as I believe in this case) it is possible to request a Stable Release Upgrade, see for details.

I have therefore prepared and attached a debdiff which should fix the issue for 14.04, assuming it passes review.

Some details on the debdiff:
I looked at for the changes which occured in version 6.1.26-2 of jetty which fixed the issue. These were the revisions 18019, 18020 and 18027. As we see from the changelog, this also includes the former Ubuntu-patch which was upstream (with added support for openjdk-8). I didn't not include this patch, because the majority of it is already in the existing package and I wanted to keep the SRU patch as minimal as possible. If it makes more sense or is easier to include all of 6.1.26-2, this can of course be done. In essence, I have included the changes in r18019 and r18020 which changes the dependencies from tomcat6 to tomcat7 which should resolve this issue.

If anyone have any details to add to the SRU request, feel free to add it. We need to say something about the regression potential for this to be accepted, and I don't really know how to assess this. I hope someone can outline this. We are switching the dependencies from one version of tomcat to a different one, and while it should be ok, we need to make sure no regressions are introduced because of this.

description: updated
Juan Sotuyo (juansotuyo) wrote :

Any update on the LTS Update?

I for one would love to see this fixed in 14.04. Being a company we use LTS for stability of our development environment, and not beeing able to use Gradle along Tomcat7 is certainly a big issue for us.

Vlad Orlov (monsta) wrote :

Hi Hans,

For some reason their bot didn't recognize your attachment as a patch, and so didn't subscribe Ubuntu Review Team to this report and didn't add the "patch" tag. I'm not sure what to do, maybe do the bot's work manually? :)

As for the regression potential, I think it's quite low: the fix has been in Debian for almost a year now (since 14 Apr 2014 - see the linked bug report) and there were no complaints on Debian bug tracker. The same applies for the patched version in Utopic. So I think we're good to go here.

tags: removed: saucy
Hans Joachim Desserud (hjd) wrote :

>For some reason their bot didn't recognize your attachment as a patch, and so didn't subscribe Ubuntu Review Team to this report

Hm, I thought that would happen automatically when I checked the "this-is-a-patch"-box. I could have sworn it did so in the past. Anyways, I'll subscribe them manually now.

>As for the regression potential...

I see your point. What I'm worried about is that if this is accepted and goes through, every person with libjetty-extra-java installed will be switched from tomcat6 to 7 and I feel on shaky ground when trying to assess what could wrong when this happens. If you don't mind we could add something along the lines of your comment in the regression potential section in the description.

tags: added: patch
Vlad Orlov (monsta) wrote :

I don't mind :)

Well, libtomcat7-java conflicts with libtomcat6-java. So, the update of this dependency in libjetty-extra-java will remove libtomcat6-java and any packages that depend on it. That's the only regression I could think of.

But then I've checked the dependencies with aptitude:

monsta@mint17 ~ $ aptitude why libtomcat6-java
i anacron Recommends rsyslog | system-log-daemon
p syslog-ng-core Provides system-log-daemon
p syslog-ng-core Suggests syslog-ng-mod-stomp
p syslog-ng-mod-stomp Suggests activemq
p activemq Depends libactivemq-java (= 5.6.0+dfsg-1)
p libactivemq-java Depends libspring-context-java
p libspring-context-java Recommends libtomcat6-java

So, it shows no packages that directly depend on libtomcat6-java.

description: updated
Changed in jetty (Ubuntu Trusty):
status: New → Triaged
importance: Undecided → High
description: updated
Changed in jetty (Ubuntu Trusty):
assignee: nobody → Timo Jyrinki (timo-jyrinki)
Timo Jyrinki (timo-jyrinki) wrote :

Thanks for the contribution, Hans! The debdiff was good as is. Indeed it seems Tomcat 7 is the most supported Tomcat version in 14.04 LTS, so it makes sense to be compatible with it. With the updated package for example the test case is again functional.

This bug will be updated when the updated package is ready for testing in -proposed pocket. Until then, it's visible at the Unapproved queue at

Thanks again!

Changed in jetty (Ubuntu Trusty):
status: Triaged → In Progress

Hello Hans, or anyone else affected,

Accepted jetty into trusty-proposed. The package will build now and be available at in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at . Thank you in advance!

Changed in jetty (Ubuntu Trusty):
status: In Progress → Fix Committed
tags: added: verification-needed
Vlad Orlov (monsta) wrote :

I confirm the issue is fixed in jetty 6.1.26-1ubuntu1.1.
Now "sudo apt-get install eclipse libjetty-extra" does not show any dependency problems.

tags: added: verification-done
removed: verification-needed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package jetty - 6.1.26-1ubuntu1.1

jetty (6.1.26-1ubuntu1.1) trusty; urgency=medium

  * Depend on tomcat7 (LP: #1286779)
    - Fixed by taking the tomcat-related part of the changes in 6.1.26-2.
    - Effectively this means the rules files as it was in
      and control file as it was in
      The other changes in 6.1.26-2 seemed unrelated to tomcat so I have not
      included them in order to keep the patch to a bare minimum.
 -- Hans Joachim Desserud <email address hidden> Sun, 21 Sep 2014 21:25:56 +0200

Changed in jetty (Ubuntu Trusty):
status: Fix Committed → Fix Released

The verification of the Stable Release Update for jetty has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Mauro (mauromol) wrote :

This caused a regression, see bug 1508562 (sorry, I don't know how to link the two bugs, I 've opened the new one yesterday without using ubuntu-bug, I discovered this only today).

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.