Bug#902670: tomcat7: version number causes exception in osgi startup

[Markus Koschany]

Am 29.06.2018 um 17:20 schrieb EmTeedee:
> Hi,
> 
> The application we are using uses Eclipse Equinox, which is an OSGI framework.
> It is not trying to parse the debian version number, it is trying to parse the
> version of exported OSGI packages.
> This is used to resolve dependencies and is a core feature of OSGI.
> 
> It looks like the offending version number comes from the Export-Package[1]
> attribute in /usr/share/tomcat7/lib/tomcat-jdbc.jar:/META-INF/MANIFEST.MF
> In the stable package (7.0.56-3+deb8u11), the version reads "7.0.56"
> In the security update (7.0.56-3+really7.0.88-1) it reads "7.0.56-3+really7.0.88"
> 
> This simply isn't a valid version specification, see e.g.
> http://www.eclipse.org/virgo/documentation/virgo-documentation-3.7.0.M01/docs/virgo-user-guide/html/ch02s02.html#d0e341
> 
> The stable package must have set this version number independently. If this is
> actually 7.0.88, I suggest that that should be put in there.

Ok, that makes sense. If this is the only MANIFEST file that needs an
update, we can patch it with the next update.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-java-maintainers/attachments/20180629/015e5343/attachment.sig>