← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1666570] Re: Post install script has error in RegEx

 

Only source package, binary is not present in zesty

** Also affects: tomcat8 (Ubuntu)
   Importance: Undecided
       Status: New

** No longer affects: tomcat8 (Ubuntu Trusty)

** Patch removed: "debdiff for trusty"
   https://bugs.launchpad.net/ubuntu/+source/tomcat8/+bug/1666570/+attachment/4834136/+files/tomcat7_7.0.52-1ubuntu11.debdiff

** Changed in: tomcat7 (Ubuntu Zesty)
       Status: In Progress => Invalid

** Changed in: tomcat7 (Ubuntu Zesty)
     Assignee: Joshua Powers (powersj) => (unassigned)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1666570

Title:
  Post install script has error in RegEx

Status in tomcat7 package in Ubuntu:
  Invalid
Status in tomcat8 package in Ubuntu:
  New
Status in tomcat7 source package in Trusty:
  New
Status in tomcat7 source package in Xenial:
  New
Status in tomcat8 source package in Xenial:
  New
Status in tomcat7 source package in Yakkety:
  New
Status in tomcat8 source package in Yakkety:
  New
Status in tomcat7 source package in Zesty:
  Invalid
Status in tomcat8 source package in Zesty:
  New
Status in tomcat7 package in Debian:
  New

Bug description:
  == Begin SRU Template ==
  [Impact] 

   * On upgrade of tomcat7 package, if a user has updated their JAVA_OPTS variable to include a '%' an upgrade will fail. The sed command in the postinst uses the '%' character to act as a delimiter, previous versions used '/' however it was updated to '%' in hopes it was far less common.
   * This SRU updates it to a character that should not be found in the JAVA_ARGS value, namely '\001'. 
   * This is the same solution Debian and tomcat maintainers are now using for Tomcat8.

  [Test Case]

  Install the version from the trusty pocket. Modify JAVA_OPTS and then
  install the version from security/updates to reproduce the issue.

   * lxc launch ubuntu-daily:trusty terusty
   * lxc exec trusty bash
   * apt install tomcat7=7.0.52-1
   * Edit /etc/defaults/tomcat7, set JAVA_OPTS="-Djava.awt.headless=true -XX:ErrorFile=/var/log/tomcat7/java_error%p.log -XX:+DisableExplicitGC -XX:+UseG1GC"
   * Enable proposed or use version from ppa (ppa:powersj/tomcat7-1666570)
   * apt update
   * apt install tomcat7
   * Keep the local version currently installed
   * With the fix, install will complete
   * Without the fix, post-installation script will return a sed -e expression #1 error.

  [Regression Potential]

   * Using a new delimiter that is far less likely to be in someone's path. This is not the first time the delimiter has changed, as it originally as '/' which is obviously going to show up as soon as someone adds a path.
   * Upstream change to tomcat8: https://anonscm.debian.org/cgit/pkg-java/tomcat8.git/patch/?id=7664221d66701e2c31a31fe3b4f22e8bea4158dc

  [Other Info]

   * Error message on failure:

  Setting up tomcat7 (7.0.52-1ubuntu0.10) ...
  sed: -e expression #1, char 97: unknown option to `s'
  dpkg: error processing package tomcat7 (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   tomcat7
  E: Sub-process /usr/bin/dpkg returned an error code (1)
   
  == End SRU Template ==

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1666570/+subscriptions