Comment 9 for bug 165074

I forwarded this info upstream at the same time as I submitted the info above to this bug report.
The upstream maintainer mentioned he would fix the problems, but it doesn't look like a new
upstream version has been released yet.

You're right that my proposed solution wouldn't work.
I'm not sure why tar is used instead of cp - perhaps something to do with the handling of special
files? It looks like tar is always used in the script when copying files, so I guess there is
probably a reason for it.

BTW - http://lists.debian.org/debian-mentors/2006/11/msg00008.html
I believe the reason those bugs aren't going away is because they are tagged as 'fixed in
installwatch 0.7.0beta4-1', so the BTS assumes the bug still exists in any version of checkinstall
that is installed on a system without installwatch > 0.7.0beta4-1 - and, since the installwatch
package is now gone, all versions of checkinstall are now "installed on a system without
installwatch > 0.7.0beta4-1". You would expect that the 'replaces: installwatch' tag would
automatically take care of this, but I guess not.
You probably need to re-tag those bugs as 'fixed in checkinstall 1.6.0'. Or maybe add a changelog
entry to your next update to checkinstall which closes all those bugs again.

Thanks!
-Paul