Package: mediatomb-daemon Version: 0.12.0~svn2018-3 Severity: normal Also I found out that the test: if dpkg --compare-versions "$2" le "0.12.0~svn2018-1"; then is triggered on new installs.
And there seems to be a bug in the mv_db is triggers: [ -e /var/lib/mediatomb/sqlite3.db ] && \ cp --preserve /var/lib/mediatomb/sqlite3.db /var/lib/mediatomb/mediatomb.db alsways returns 1 which errors out the postinst. Adding "|| return 0" at the end of it helps. Probably adding parenthesis around to avoid it applying to the "cp" would be good. Best regards, Alban -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.30-rc6-wl-24012-g8dcff58 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages mediatomb-daemon depends on: ii adduser 3.110 add and remove users and groups ii mediatomb-common 0.12.0~svn2018-3 UPnP MediaServer (base package) mediatomb-daemon recommends no packages. mediatomb-daemon suggests no packages. -- no debconf information -- debsums errors found: debsums: package mediatomb-daemon is not installed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org