On Thu, Aug 1, 2013 at 12:35 AM, Emmanuel Bourg <ebo...@apache.org> wrote: > > You can't depend on the version in stable, the goal is to build a set of > packages that work together. You can't rely on an older revision of a > package that is no longer available in the current distribution. >
Thanks for clarifying - that makes more sense than how I had originally understood packaging. > The solution is to patch the tomcat6 package. You can look at the > commons-jci and jasperreports packages which were also affected by this > issue. The patch is trivial, and that's a good opportunity to learn quilt :) > > This issue has also been fixed upstream, so upgrading the package to the > version 6.0.37 might be an alternative. > > https://issues.apache.org/bugzilla/show_bug.cgi?id=54615 > Thanks for the info Emmanuel . I notice there are a number of patches already in the package, so presumably if I were to upgrade the package I would need to determine if those patches had already been applied upstream? If so I think in this case to avoid making huge mistakes I'd prefer to patch what is already there and then look into upgrading it at a later stage. I will also contact the regular maintainer to check I'm not duplicating effort. Stephen Nelson -- To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cahphs3k6f0vasmwrpxwd2o1ijpnja9aze7hqvnnhbxg7b65...@mail.gmail.com
