Package: mozilla-thunderbird
Version: 1.0.2-3
Severity: minor
Tags: patch

Running the update-mozilla-thunderbird-chrome script yields a warning
when using the unstable version of findutils (4.2.22-1). Reordering the
arguments to find(1) in the script fixes the problem. A patch which does
this is included.

The warning:

# update-mozilla-thunderbird-chrome
Updating mozilla-thunderbird chrome registry...find: warning: you have
specified the -maxdepth option after a non-option argument -name, but
options are not positional (-maxdepth affects tests specified before it
as well as those specified after it).  Please specify options before
other arguments.

find: warning: you have specified the -maxdepth option after a
non-option argument -name, but options are not positional (-maxdepth
affects tests specified before it as well as those specified after it). 
Please specify options before other arguments.

done.

--- mozilla-thunderbird-1.0.2/debian/update-mozilla-thunderbird-chrome	2005-06-23 14:26:33.511997936 -0400
+++ mozilla-thunderbird-1.0.2-n/debian/update-mozilla-thunderbird-chrome	2005-06-23 14:28:31.046130032 -0400
@@ -72,7 +72,7 @@
 # previously packaged extensions):
 # remove those that are symlinks pointing to nowhere
 # and remove those that are directory and are in defaults/profile/extensions
-for f in `find ${LIBDIR}/extensions/ -name '{*}' -maxdepth 1`; do
+for f in `find ${LIBDIR}/extensions/ -maxdepth 1 -name '{*}'`; do
     if [ -L $f ] && [ ! -e $f ]; then
         rm ${RM_FLAGS} -f $f
     elif [ ! -L $f ] && [ -d $f ] && [ -d ${LIBDIR}/defaults/profile/extensions/`basename $f` ]; then
@@ -89,7 +89,7 @@
     fi
 done
 # create symlinks that are not already there
-for f in `find ${LIBDIR}/defaults/profile/extensions/ -name '{*}' -maxdepth 1`; do
+for f in `find ${LIBDIR}/defaults/profile/extensions/ -maxdepth 1 -name '{*}'`; do
     [ "${VERBOSE}" ] && echo "W: ${f} should be in ${LIBDIR}/extensions/" >&2
     if [ ! -e ${LIBDIR}/extensions/`basename $f` ]; then
         ln -s $f ${LIBDIR}/extensions

Reply via email to