Bug#314351: initscripts: bootclean.sh seems broken

2005-07-08 Thread David Jarvie
I tried rearranging the order of the arguments to find, and find . -maxdepth 0 -perm -002 works without error. So the fix appears to be very simple. -- David Jarvie. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#314351: initscripts: bootclean.sh seems broken/patch

2005-06-22 Thread Richard Green
shouldn't the line in the patch be: ( if cd /tmp && [ "`find . -maxdepth 0 -perm -002`" = "." ] instead of: ( if cd /tmp && [ "`find . -maxdepth -perm -002 0`" = "." ] and also that patch doesn't seem to cover the other two errors: find: warning: you have specified the -depth option after a non-

Bug#314351: initscripts: bootclean.sh seems broken

2005-06-16 Thread Miquel van Smoorenburg
On Thu, 2005-06-16 at 11:27 +0200, Michael Prokop wrote: > Package: initscripts > Version: 2.86.ds1-1 > Followup-For: Bug #314351 > > > JFYI: The problem seems to be related to one of the latest versions > of findutils (here findutils 4.2.22-1). I know. You're about the 4th or 5th person to file

Bug#314351: initscripts: bootclean.sh seems broken

2005-06-16 Thread Michael Prokop
Package: initscripts Version: 2.86.ds1-1 Followup-For: Bug #314351 JFYI: The problem seems to be related to one of the latest versions of findutils (here findutils 4.2.22-1). BTW: Shouldn't initscripts depend on findutils? regards, -mika- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a

Bug#314351: initscripts: bootclean.sh seems broken

2005-06-15 Thread Can Burak Cilingir
Package: initscripts Version: 2.86.ds1-1 Severity: important I got the following message during my system bootup Cleaning /tmpfind: warning: you have specified the -maxdepth option after a non-option argument -perm, but options are not positional (-maxdepth affects tests specified before it as