Public bug reported:

TMPTIME setting from Wily is not migrated to mountall on upgrade to
Xenial.

systemd.postinst from 229-4ubuntu4 contains this bit:

# Do a one-time migration of the TMPTIME setting
if dpkg --compare-versions "$2" lt "204-9"; then
    # Fix up potentially broken tmp.conf, see Debian#738862
    if [ -e /etc/tmpfiles.d/tmp.conf ]; then
        sed -i '/^# Clear \/var\/tmp/d' /etc/tmpfiles.d/tmp.conf
        sed -i 's,^\(d /var/tmp\),#\1,g' /etc/tmpfiles.d/tmp.conf
    fi

    if [ -f /etc/default/rcS ]; then
        . /etc/default/rcS
    fi
    if [ ! -e /etc/tmpfiles.d/tmp.conf ]; then
        case "$TMPTIME" in
            -*|infinite|infinity)
                cat > /etc/tmpfiles.d/tmp.conf <<EOF
# Avoid clearing /tmp by shipping an empty /etc/tmpfiles.d/tmp.conf file
# which overrides /usr/lib/tmpfiles.d/tmp.conf.
# This file was automatically created because of local modifications in
# /etc/default/rcS where TMPTIME was set to infinite.
EOF
                ;;
        esac
    fi
fi

However, Xenial ships with a more recent systemd than 204, meaning that
the TMPTIME setting is not migrated. As a result people who upgrade from
Wily to Xenial will find that /tmp is always erased on startup, with no
clear indication of how to change the behavior.

Fixing this behavior would still expose this debian bug
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795269> because the
(currently broken) code does not handle values other than infinity.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: initscripts 2.88dsf-59.3ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Tue Apr 19 19:57:23 2016
InstallationDate: Installed on 2012-10-07 (1290 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120822.4)
ProcEnviron:
 LANGUAGE=
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: sysvinit
UpgradeStatus: Upgraded to xenial on 2016-04-09 (10 days ago)
modified.conffile..etc.default.rcS: [modified]
mtime.conffile..etc.default.rcS: 2015-05-26T01:09:17.227420

** Affects: sysvinit (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug dist-upgrade xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1572349

Title:
  TMPTIME migration does not work on upgrade from wily to xenial

Status in sysvinit package in Ubuntu:
  New

Bug description:
  TMPTIME setting from Wily is not migrated to mountall on upgrade to
  Xenial.

  systemd.postinst from 229-4ubuntu4 contains this bit:

  # Do a one-time migration of the TMPTIME setting
  if dpkg --compare-versions "$2" lt "204-9"; then
      # Fix up potentially broken tmp.conf, see Debian#738862
      if [ -e /etc/tmpfiles.d/tmp.conf ]; then
          sed -i '/^# Clear \/var\/tmp/d' /etc/tmpfiles.d/tmp.conf
          sed -i 's,^\(d /var/tmp\),#\1,g' /etc/tmpfiles.d/tmp.conf
      fi

      if [ -f /etc/default/rcS ]; then
          . /etc/default/rcS
      fi
      if [ ! -e /etc/tmpfiles.d/tmp.conf ]; then
          case "$TMPTIME" in
              -*|infinite|infinity)
                  cat > /etc/tmpfiles.d/tmp.conf <<EOF
  # Avoid clearing /tmp by shipping an empty /etc/tmpfiles.d/tmp.conf file
  # which overrides /usr/lib/tmpfiles.d/tmp.conf.
  # This file was automatically created because of local modifications in
  # /etc/default/rcS where TMPTIME was set to infinite.
  EOF
                  ;;
          esac
      fi
  fi

  However, Xenial ships with a more recent systemd than 204, meaning
  that the TMPTIME setting is not migrated. As a result people who
  upgrade from Wily to Xenial will find that /tmp is always erased on
  startup, with no clear indication of how to change the behavior.

  Fixing this behavior would still expose this debian bug
  <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795269> because the
  (currently broken) code does not handle values other than infinity.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initscripts 2.88dsf-59.3ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Tue Apr 19 19:57:23 2016
  InstallationDate: Installed on 2012-10-07 (1290 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120822.4)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: sysvinit
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (10 days ago)
  modified.conffile..etc.default.rcS: [modified]
  mtime.conffile..etc.default.rcS: 2015-05-26T01:09:17.227420

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to