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

Broken Debian upgrades because postinst doesn't check for present group/user


    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core

      Package upgrade from 1.559 to 1.560 on Debian systems fails with:

      dpkg: error processing jenkins (--configure):
      subprocess installed post-installation script returned error exit status 1

      due to the:

      addgroup --system --quiet jenkins

      call in postinst without checking whether corresponding group already exists.

      Problem introduced as of:

      commit 7216aab0d3f7215be7d71109936ad4b3aa0a583b
      Author: Peter Eisentraut <peter@eisentraut.org>
      Date: Sun Nov 3 08:12:17 2013 -0500
      debian: Use a configurable group for the Jenkins user
      Typical Debian practice is to have one equally-named group per system
      user. Make that for the jenkins user by default, but allow it to be
      overridden in /etc/default/jenkins, same as for the user name.

      This change also deleted the check for the existing Jenkins user (for whatever reason, but that's also broken).

      I'm working on a fix/PR right now.

            Unassigned Unassigned
            mika Michael Prokop
            3 Vote for this issue
            10 Start watching this issue