Your message dated Fri, 7 Aug 2026 00:04:32 -0700
with message-id
<caere_of1h-ocvmh4r3daj+jz-quetrbrwgydfnl2olmcjtj...@mail.gmail.com>
and subject line Re: Bug#487965: checkinstall: please use absolute patch for
"which"
has caused the Debian Bug report #487965,
regarding checkinstall: please use absolute patch for "which"
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.)
--
487965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=487965
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: checkinstall
Version: 1.6.1-5
Severity: wishlist
User: [email protected]
Usertags: origin-ubuntu intrepid ubuntu-patch
Hi,
If the user has an alias defined for "which", then it can cause
checkinstall to fail. Using the absolute path to "which" ensures
that this doesn't happen. The following patch is used in Ubuntu
to provide this behaviour. Please consider applying it.
Thanks,
James
diff -pruN 1.6.1-5/checkinstall 1.6.1-5ubuntu1/checkinstall
--- 1.6.1-5/checkinstall 2007-11-18 16:12:42.000000000 +0000
+++ 1.6.1-5ubuntu1/checkinstall 2007-11-18 16:11:28.000000000 +0000
@@ -908,7 +908,7 @@ if ! [ -x "$VISUAL" ]; then
if [ -x "$EDITOR" ]; then
VISUAL=$EDITOR
else
- VISUAL=`which vi`
+ VISUAL=`/usr/bin/which vi`
fi
fi
@@ -920,7 +920,7 @@ BADTAR=0
if [ "$TAR" ]; then
! [ -x "$TAR" ] && BADTAR=1
else
- TAR=`which tar-1.13 2> /dev/null`
+ TAR=`/usr/bin/which tar-1.13 2> /dev/null`
fi
if ! [ -x "$TAR" ]; then
@@ -1910,7 +1910,7 @@ FAILED=0
if [ $INSTALL -gt 0 ]; then
# Verify that we have the "installpkg" command in our path
- INSTALLPKG_PATH=`which installpkg 2> /dev/null`
+ INSTALLPKG_PATH=`/usr/bin/which installpkg 2> /dev/null`
if ! [ -x "$INSTALLPKG_PATH" ]; then
echo
@@ -2117,7 +2117,7 @@ FAILED=0
# Verify that we have the rpm command in our path
-RPM_PATH=`which rpm 2> /dev/null`
+RPM_PATH=`/usr/bin/which rpm 2> /dev/null`
if ! [ -x "$RPM_PATH" ]; then
echo
@@ -2167,7 +2167,7 @@ else
RPMBUILD="rpm"
fi
-if [ "$RPMBUILD" = "rpmbuild" -a ! -x "`which rpmbuild 2> /dev/null`" ]; then
+if [ "$RPMBUILD" = "rpmbuild" -a ! -x "`/usr/bin/which rpmbuild 2> /dev/null`"
]; then
echo
echo "*** The \"rpmbuild\" program is not in your PATH!"
echo
@@ -2395,7 +2395,7 @@ FAILED=0
# Verify that we have the dpkg command in our path
-DPKG_PATH=`which dpkg 2> /dev/null`
+DPKG_PATH=`/usr/bin/which dpkg 2> /dev/null`
if ! [ -x "$DPKG_PATH" ]; then
echo
--- End Message ---
--- Begin Message ---
At this point I think this bug can be closed, given it has been 18 years
and there has been no consensus that we should implement it.
Stephen
--- End Message ---
