Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-35224

apt-get upgrade jenkins fails (not POSIXLY_CORRECT)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • packaging
    • Ubuntu 15.04, jenkins 2.6 installed
    • 2.335

      Upgrade from jenkins 2.6 to 2.7 fails if the environment variable POSIXLY_CORRECT is set (which is the default on all of our servers):

       > + apt-get upgrade jenkins
      Reading package lists... Done
      Building dependency tree       
      Reading state information... Done
      Calculating upgrade... jenkins is already the newest version.
      Done
      0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
      1 not fully installed or removed.
      After this operation, 0 B of additional disk space will be used.
      Do you want to continue? [Y/n] 
      Setting up jenkins (2.7) ...
       * Starting Jenkins Continuous Integration Server jenkins
      -su: --shell=/bin/bash: invalid option
      Usage:	-su [GNU long option] [option] ...
      	-su [GNU long option] [option] script-file ...
      GNU long options:
      	--debug
      	--debugger
      	--dump-po-strings
      	--dump-strings
      	--help
      	--init-file
      	--login
      	--noediting
      	--noprofile
      	--norc
      	--posix
      	--rcfile
      	--restricted
      	--verbose
      	--version
      Shell options:
      	-ilrsD or -c command or -O shopt_option		(invocation only)
      	-abefhkmnptuvxBCHP or -o option
         ...fail!
      invoke-rc.d: initscript jenkins, action "start" failed.
      dpkg: error processing package jenkins (--configure):
       subprocess installed post-installation script returned error exit status 7
      Errors were encountered while processing:
       jenkins
      E: Sub-process /usr/bin/dpkg returned an error code (1)
      

            basil Basil Crow
            jelmd Jens Elkner
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: