The bug report is some days old now - so I updated the goal to 7.0.40.
See also https://bugs.launchpad.net/ubuntu/precise/+source/tomcat7/+bug/1178645
and for libtomcat7-native 
https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1092548 .

A "no change backport" from debian [7.0.40-2] to precise was build in
https://launchpad.net/~dirk-computer42/+archive/c42-edge-server and is
distributed in https://launchpad.net/~dirk-
computer42/+archive/c42-backport.

For my installations it works without any known problem.

** Summary changed:

- Please backport tomcat7 7.0.34 (main) from raring to precise (and quantal) 
[and tomcat-native] to fix serious CVE reports
+ Please backport tomcat7 7.0.40 (main) from debian to precise (and quantal) 
[and tomcat-native] to fix serious CVE reports

** Summary changed:

- Please backport tomcat7 7.0.40 (main) from debian to precise (and quantal) 
[and tomcat-native] to fix serious CVE reports
+ Please backport tomcat7 7.0.40 (main) from saucy/debian to precise (and 
quantal) [and tomcat-native] to fix serious CVE reports

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1073159

Title:
  Please backport tomcat7 7.0.40 (main) from saucy/debian to precise
  (and quantal) [and tomcat-native] to fix serious CVE reports

To manage notifications about this bug go to:
https://bugs.launchpad.net/precise-backports/+bug/1073159/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to