Your message dated Sat, 24 May 2014 17:53:19 +0200
with message-id <[email protected]>
and subject line Closing this bug
has caused the Debian Bug report #673337,
regarding Subject: zenmap install should use DESTDIR instead of modifying prefix
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
673337: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673337
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nmap
Version: 5.51.6
Severity: minor
Tags: patch
The installation step should use DESTDIR, and not change the value of
prefix to something different than was used at the build step. This
would make a later sed command to remove the bogus prefix unnecessary.
This is somewhat related to #663217, in which a directory under /tmp was
written into a script file because prefix was changed rather than
DESTDIR.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (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
diff --git a/debian/rules b/debian/rules
index 236313c..8940926 100644
--- a/debian/rules
+++ b/debian/rules
@@ -57,8 +57,7 @@ install: build
dh_testroot
dh_clean -k
dh_installdirs
- $(MAKE) prefix=`pwd`/debian/tmp/usr install
- find debian/tmp/usr/lib/python* -type f | xargs sed -i "s:`pwd`/debian/tmp::g"
+ $(MAKE) DESTDIR=`pwd`/debian/tmp install
rm debian/tmp/usr/bin/uninstall_zenmap
# This single target is used to build all the packages, all at once, or
--- End Message ---
--- Begin Message ---
This issue has been fixed since 5.51.6-0.2, so I'm closing the bug.
Cheers,
-Hilko
--- End Message ---
