ok, I see it now. The sed call in the tomcat6.postinst doesn't filter
out some characters (especially "/") so if you submit a JAVA_OPTS
containing a / it will fail. Needs to be fixed.
Workaround is to edit your JAVA_OPTS before upgrade to make sure they
don't contain /, then fix it up afterwards.
I have this problem too. The source of the problem appears to be that I
didn't accept the new version of the config file when asked but opted to
keep my old version. Later processing assumed the new config file.
** Attachment added: "/etc/default/tomcat6"
https://bugs.launchpad.net/ubuntu/+sou
We'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the requested
information? Thanks!
--
Cannot Upgrade Tomcat6 when doing release upgrade from lucid to maverick
https://bugs.launchpad.net/bugs/654549
You received this
Installed tomcat6 on Lucid, do-release-upgrade -d to maverick -> works.
So it's probably due to a missing or borked configuration.
** Changed in: tomcat6 (Ubuntu)
Importance: High => Low
** Changed in: tomcat6 (Ubuntu)
Assignee: Thierry Carrez (ttx) => (unassigned)
--
Cannot Upgrade Tom
Could you attach your /etc/default/tomcat6 file, please.
** Changed in: tomcat6 (Ubuntu)
Importance: Undecided => High
** Changed in: tomcat6 (Ubuntu)
Status: New => Incomplete
** Changed in: tomcat6 (Ubuntu)
Assignee: (unassigned) => Thierry Carrez (ttx)
--
Cannot Upgrade Tomca
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/654549/+attachment/1671319/+files/Dependencies.txt
--
Cannot Upgrade Tomcat6 when doing release upgrade from lucid to maverick
https://bugs.launchpad.net/bugs/654549
You received this bug notification because you are a m
