Source: redis-server
Version: 2:2.8.7-1
Severity: normal

Dear Maintainer,

I'm installing redis-server into a root filesystem using multistrap. The
host has a different architecture, so multistrap skips all scripts during
the install.  Then when I run dpkg --configure -a, the postinst script
tries to chown redis /var/lib/redis, which fails because the redis user
that would have been created by preinst doesn't exist.

I haven't found an official policy on how packages are supposed to create a
user during install, but all the instances I found (in openssh-server,
racoon, trousers) did so in postinst rather than preinst. This unofficial
wiki document also recommends postinst:
https://wiki.debian.org/AccountHandlingInMaintainerScripts .  Since this
convention happens to benefit multistrap users, I'd like to see
redis-server adopt it.

(See bug 627068 for further discussion about skipping preinst during
foreign installs.)

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.11.0-17-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Reply via email to