Package: dh-virtualenv
Version: 0.10-1~bpo8+1
Severity: normal
Hi,
when building a .deb packet with a python3 virtual environment and a few
requirements I've found out, that the symbolic link $ENV/bin/python points to
/$MYHOMEDIR/$MYBUILDDIR/$MYPACKETDIR/debian/$MYPACKETNAME/$DESTINATIONDIR/bin/python3
I assume, that the correct link destination would be ./python3 instead of the
absolute path of where the packet has been built. Correct me, if I'm wrong.
debian/rules looks as follows:
#!/usr/bin/make -f
export DH_VIRTUALENV_INSTALL_ROOT=/srv
%:
dh $@ --with python-virtualenv --install-suffix my_app_name --python
/usr/bin/python3 --builtin-venv --skip-install
I'm going to tweak some options, and maybe I'll dirtyfix this problem by simply
recreating the link, if the problem remains, but in any case I thought, that
you want to know, that there's a bug hidden somewhere.
-- System Information:
Debian Release: 8.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages dh-virtualenv depends on:
ii libjs-sphinxdoc 1.2.3+dfsg-1
ii python 2.7.9-1
ii virtualenv 1.11.6+ds-1
dh-virtualenv recommends no packages.
dh-virtualenv suggests no packages.
-- no debconf information
