Package: libpython3.4-minimal
Version: 3.4.2-1
Severity: minor

The attached patch fixes this apparent mistake, which does
still happen.

I would have provided a bzr diff, but the VCS-Bzr URL
http://bazaar.launchpad.net/~doko/python/pkg3.4-debian
gives a 404. Please fix that too ☺

-- System Information:
Debian Release: jessie/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable')
Architecture: x32 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh

Versions of packages libpython3.4-minimal depends on:
ii  libc6              2.19-11
ii  libssl1.0.0        1.0.1i-2
ii  multiarch-support  2.19-11

Versions of packages libpython3.4-minimal recommends:
ii  libpython3.4-stdlib  3.4.2-1

libpython3.4-minimal suggests no packages.

-- Configuration Files:
/etc/python3.4/sitecustomize.py [Errno 2] No such file or directory: 
u'/etc/python3.4/sitecustomize.py'

-- no debconf information
diff -pru python3.4-3.4.2~/debian/PVER-minimal.postinst.in python3.4-3.4.2/debian/PVER-minimal.postinst.in
--- python3.4-3.4.2~/debian/PVER-minimal.postinst.in	2014-10-09 09:56:26.000000000 +0200
+++ python3.4-3.4.2/debian/PVER-minimal.postinst.in	2014-10-09 09:57:14.899574723 +0200
@@ -3,7 +3,7 @@
 set -e
 
 if [ ! -f /etc/@PVER@/sitecustomize.py ]; then
-    cat <<-EOF
+    cat >>/etc/@PVER@/sitecustomize.py <<-EOF
 	# Empty sitecustomize.py to avoid a dangling symlink
 EOF
 fi
diff -pru python3.4-3.4.2~/debian/libPVER-minimal.postinst.in python3.4-3.4.2/debian/libPVER-minimal.postinst.in
--- python3.4-3.4.2~/debian/libPVER-minimal.postinst.in	2014-10-09 09:56:26.000000000 +0200
+++ python3.4-3.4.2/debian/libPVER-minimal.postinst.in	2014-10-09 09:57:14.571570325 +0200
@@ -3,7 +3,7 @@
 set -e
 
 if [ ! -f /etc/@PVER@/sitecustomize.py ]; then
-    cat <<-EOF
+    cat >>/etc/@PVER@/sitecustomize.py <<-EOF
 	# Empty sitecustomize.py to avoid a dangling symlink
 EOF
 fi

Reply via email to