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

2018-06-30 Thread Markus Koschany
Am 30.06.2018 um 02:04 schrieb EmTeedee: > Hi, > > On 29/06/2018 18:05, Markus Koschany wrote: >> Ok, that makes sense. If this is the only MANIFEST file that needs an update, >> we can patch it with the next update. > > I changed the version number in just the one MANIFEST file and the

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

2018-06-29 Thread EmTeedee
Hi, On 29/06/2018 18:05, Markus Koschany wrote: > Ok, that makes sense. If this is the only MANIFEST file that needs an update, > we can patch it with the next update. I changed the version number in just the one MANIFEST file and the application started without an issue. Is this bug enough to

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

2018-06-29 Thread 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

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

2018-06-29 Thread Emmanuel Bourg
Le 29/06/2018 à 16:35, Markus Koschany a écrit : > I don't think we can fix the version of tomcat7 without making it > impossible to upgrade from Jessie to Stretch. I think the issue is the version in the OSGi metadata of the MANIFEST.MF file, not the version of the package. This is something we

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

2018-06-29 Thread 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

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

2018-06-29 Thread Markus Koschany
Am 29.06.2018 um 13:07 schrieb EmTeedee: > Package: tomcat7 > Version: 7.0.56-3+really7.0.88-1 > Severity: important > Tags: jessie jessie-security > > During startup the current version number causes an application using > ecplise osgi to fail with an exception. I don't think we can fix the

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

2018-06-29 Thread EmTeedee
Package: tomcat7 Version: 7.0.56-3+really7.0.88-1 Severity: important Tags: jessie jessie-security During startup the current version number causes an application using ecplise osgi to fail with an exception. Caused by: java.lang.IllegalArgumentException: invalid version "7.0.56-3+really7.0.88":