[bug-notifications] [findutils 0001101]: gupdatedb mktemp and !
Mantis Bug Tracker
noreply at opencsw.org
Sat Jul 4 01:16:44 CEST 2009
A NOTE has been added to this issue.
======================================================================
http://www.opencsw.org/bugtrack/view.php?id=1101
======================================================================
Reported By: james
Assigned To: car
======================================================================
Project: findutils
Issue ID: 1101
Category: regular use
Reproducibility: sometimes
Severity: tweak
Priority: normal
Status: acknowledged
======================================================================
Date Submitted: 2005-07-26 18:10 CEST
Last Modified: 2009-07-04 01:16 CEST
======================================================================
Summary: gupdatedb mktemp and !
Description:
This started as a request for mktemp but even with mktemp gupdatedb needs a
tweak. Without CSWmktemp:
$ gupdatedb --old-format
Warning: future versions of findutils will shortly discontinue support for
the old locate database format.
/opt/csw/bin/gupdatedb: mktemp: not found
/opt/csw/bin/gupdatedb: !: not found
/opt/csw/bin/gupdatedb: mktemp: not found
/opt/csw/bin/gupdatedb: !: not found
Install CSWmktemp which is not in the findutils depend list and it still
fails:
$ gupdatedb --old-format
Warning: future versions of findutils will shortly discontinue support for
the old locate database format.
/opt/csw/bin/gupdatedb: !: not found
/opt/csw/bin/gupdatedb: !: not found
becasue the ! is not /bin/sh, I guess the was written for a system that
emulated sh with something else, probably bash. #!/bin/ksh at the top will
fix it.
======================================================================
----------------------------------------------------------------------
(0006392) car (manager) - 2009-07-04 01:16
http://www.opencsw.org/bugtrack/view.php?id=1101#c6392
----------------------------------------------------------------------
It seems to me that the slightly harder route, to fix the script so that it
*is* Bourne shell compatible, is probably the better fix.
At a brief glance, the problem seems to be a couple of if tests unadorned
by []. Fixing these certainly gets rid of the warnings and the script
appears to function properly afterwards. I'll double-check this later,
submit a new package to testing, then submit a patch upstream if this fixes
the issue.
More information about the bug-notifications
mailing list