Bug#802716: libjetty-extra-java: Jasper symlinks are broken after switch to tomcat7

Hans Joachim Desserud debian at desserud.org
Thu Oct 22 20:08:39 UTC 2015


Package: libjetty-extra-java
Version: 6.1.26-5
Severity: important

Dear Maintainer,

Some time back (version 6.1.26-2), jetty switched dependencies from
tomcat6 to tomcat7. Things seemed to be working fine and I don't see
any tomcat-related entries in the changelog since then.

However, there was recently a bug report for the Ubuntu package
which points out that some of the symlinks from libjetty-extra-java
no longer works with tomcat7.

The package install the following symlinks:
$ ls -l /usr/share/jetty/lib/jsp-2.1/
total 0
lrwxrwxrwx 1 root root 21 Jun  4 08:39 ant.jar -> ../../../java/ant.jar
lrwxrwxrwx 1 root root 30 Jun  4 08:39 ant-launcher.jar -> 
../../../java/ant-launcher.jar
lrwxrwxrwx 1 root root 27 Jun  4 08:39 commons-el.jar -> 
../../../java/jasper-el.jar
lrwxrwxrwx 1 root root 28 Jun  4 08:39 el-api.jar -> 
../../../java/el-api-2.1.jar
lrwxrwxrwx 1 root root 24 Jun  4 08:39 jasper.jar -> 
../../../java/jasper.jar
lrwxrwxrwx 1 root root 32 Jun  4 08:39 jcl-over-slf4j.jar -> 
../../../java/jcl-over-slf4j.jar
lrwxrwxrwx 1 root root 29 Jun  4 08:39 jsp-api.jar -> 
../../../java/jsp-api-2.1.jar
lrwxrwxrwx 1 root root 27 Jun  4 08:39 slf4j-api.jar -> 
../../../java/slf4j-api.jar
lrwxrwxrwx 1 root root 30 Jun  4 08:39 slf4j-simple.jar -> 
../../../java/slf4j-simple.jar
lrwxrwxrwx 1 root root 29 Jun  4 08:39 tomcat-juli.jar -> 
../../../java/tomcat-juli.jar
lrwxrwxrwx 1 root root 28 Jun  4 08:39 xercesImpl.jar -> 
../../../java/xercesImpl.jar
lrwxrwxrwx 1 root root 31 Jun  4 08:39 xmlParserAPIs.jar -> 
../../../java/xmlParserAPIs.jar

Of these, commons-el.jar and jasper.jar have broken symlinks. The
reporter tried to point them to the corresponding tomcat7 jars, but
ran into different problems. Please see
https://bugs.launchpad.net/ubuntu/+source/jetty/+bug/1508562
for more information.

As a side note, the package was naturally synced to the development
release of Ubuntu at the time. However, due to conflicts when
attempting to install packages depending on different tomcat
versions, the patch was also applied as a stable release upgrade.
The transition patch looked rather small and fixed the dependencies,
so everything seemed fine up until now.

I've since verified that this symlink issue affects not only that
release, but also later Ubuntu releases and Debian Sid. So I believe
that we need to resolve this and once we have a solution look at
whether that should be applied for older releases too (might be
relevant in both Debian- and Ubuntu-land).

-- System Information:
Debian Release: stretch/sid
   APT prefers unstable
   APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.2.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libjetty-extra-java depends on:
ii  ant                                                               
1.9.6-1
ii  libgeronimo-jta-1.1-spec-java [libgeronimo-jta-1.0.1b-spec-java]  
1.1.1-3
ii  libjetty-java                                                     
6.1.26-5
ii  libmail-java                                                      
1.5.3-1
ii  libslf4j-java                                                     
1.7.12-2
ii  libtomcat7-java                                                   
7.0.64-1
ii  libxerces2-java                                                   
2.11.0-7

Versions of packages libjetty-extra-java recommends:
ii  libjetty-extra  6.1.26-5

Versions of packages libjetty-extra-java suggests:
pn  jetty  <none>

-- no debconf information


-- 
mvh / best regards
Hans Joachim Desserud
http://desserud.org



More information about the pkg-java-maintainers mailing list