gradle depends on libtomcat6-java

[Stephen Byrne]

gradle depends on libtomcat6-java. tomcat7 depends on tomcat7-common, which depends on libtomcat7-java, which conflicts with libtomcat6-java; thus you cannot install both gradle and tomcat7.

Perhaps there should be a libtomcat-java meta-package (provided by libtomcat6-java | libtomcat7-java) that gradle depends on, or Gradle's Tomcat plugin should be split out to a separate package. Or maybe libtomcat6-java and libtomcat6-java do not really need to conflict.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gradle 1.0~m3-1
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Thu May 10 14:24:14 2012
InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1)
PackageArchitecture: all
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 LC_MESSAGES=en_US.UTF-8
 SHELL=bash
SourcePackage: gradle
UpgradeStatus: No upgrade log present (probably fresh install)

[Hans Joachim Desserud (hjd)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in gradle version 1.4-2ubuntu1 which is available in Ubuntu 13.10, since tomcat is no longer listed among the dependencies.

 If you need a fix for the bug in previous versions of Ubuntu, please follow the instructions for "Requesting a Backport" at https://wiki.ubuntu.com/UbuntuBackports#Requesting_a_Backport

[Arr Loh (elspam)]

A backport to 12.04 LTS would be divine, given that, you know, it's the long-term supported version and all.

[Ru Uuy (ruuuuy)]

Hello,
I can't see how this is fixed in 13.10.
See my console output:
$ apt-rdepends libgradle-plugins-java | grep tomcat
Reading package lists... Done
Building dependency tree
Reading state information... Done
  Depends: libtomcat6-java (>= 6.0.20-2)
libtomcat6-java

The "path" is: gradle -> libgradle-plugins-java -> libjetty-extra-java -> libtomcat6-java

[Hans Joachim Desserud (hjd)]

First of all, sorry for the slow response.

>The "path" is: gradle -> libgradle-plugins-java -> libjetty-extra-java -> libtomcat6-java

That is interesting, and I'm not sure how I missed it. What I did when investigating this bug was:
1) Comparing the control files. I looked at the control files listing all build and install dependencies for gradle which in 1.4-2ubuntu1 no longer mentioned tomcat. Thus, gradle was no longer directly depending on tomcat.
2) I checked on a virtual machine the list of packages which would be installed by "sudo apt-get install gradle" for this version where I didn't find tomcat mentioned at all. (Either I missed it, or it was already installed on the system, sorry about that.)

I am not quite sure how to proceed with this bug. As mentioned in 1) gradle is no longer directly depending on tomcat. Though, due to the dependency on libjetty-extra-java we still run into the same problem. So any fix would likely need to be applied outside the gradle package. I will look into whether this should be reopened, whether a new bug should be filed against libjetty-extra-java or whether this should be marked as affecting both.

(Btw. I recently found that libjetty-extra-java has a bug report on migrating to tomcat7 in the Debian BTS, see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686876 for more info. In fact, it mentions gradle as one of the packages it causes problems for.)

[Hans Joachim Desserud (hjd)]

I filed the follow-up bug 1286779 against libjetty-java-extra.

[Juan Sotuyo (juansotuyo)]

This issue persists in 14.04

$ apt-rdepends libgradle-plugins-java | grep tomcat
Reading package lists... Done
Building dependency tree
Reading state information... Done
  Depends: libtomcat6-java (>= 6.0.20-2)
libtomcat6-java

The "path" is: gradle -> libgradle-plugins-java -> libjetty-extra-java -> libtomcat6-java

[Daniil Ivanov (daniil-ivanov)]

As of today, issue is still in 14.04, but is fixed in 14.10.