Bug in :copy; question about bug tracker

I'm using version 1.032 on Debian 3.0.  With the following short recipe 
I get the traceback below.
____________________________________________
all:
    temp=/tmp/orig
    other=/tmp/other
    :mkdir {f} $(temp) $(temp)/x $(other)
    :pushdir $(temp)
    :copy {r} . $(other)

    :print Copied successfully.
____________________________________________

____________________________________________
extra:  Reading recipe "problem.aap"
extra:  Finished reading recipe "problem.aap"
depend: Adding default dependency for "clean"
depend: Adding default dependency for "cleanmore"
depend: Building the "all" target
depend: 1 - updating target "all"
depend: 2 - Using dependency "all : "
depend: 1 - Updating "all" from "": virtual target
info:   Created directory "/tmp/orig"
info:   Created directory "/tmp/orig/x"
changedir:      Entering directory `/tmp/orig'
error:  Internal Error
error:  Traceback (most recent call last):
   File
"/home/cdodt/aap-1.032/debian/aap/usr/lib/aap/Exec-1.032/Process.py", line
1107, in Process
    exec script_string in recdict, recdict
   File "<string>", line 14, in ?
   File
"/home/cdodt/aap-1.032/debian/aap/usr/lib/aap/Exec-1.032/Commands.py",
line 1967, in aap_copy
    copy_move(line_nr, recdict, arg, 1)
   File
"/home/cdodt/aap-1.032/debian/aap/usr/lib/aap/Exec-1.032/CopyMove.py",
line 61, in copy_move
    argdictlist[-1], optiondict, 1, errmsg = 1)
   File
"/home/cdodt/aap-1.032/debian/aap/usr/lib/aap/Exec-1.032/CopyMove.py",
line 428, in remote_copy_move
    {"name": destpath}, opt, 0, errmsg)
   File
"/home/cdodt/aap-1.032/debian/aap/usr/lib/aap/Exec-1.032/CopyMove.py",
line 428, in remote_copy_move
    {"name": destpath}, opt, 0, errmsg)
   File
"/home/cdodt/aap-1.032/debian/aap/usr/lib/aap/Exec-1.032/CopyMove.py",
line 581, in remote_copy_move
    if fscheme != '':
 UnboundLocalError: local variable 'fscheme' referenced before assignment

error:  Aborted
____________________________________________________

A trivial patch to fix this is to add 
    fscheme='' 
to the top of remote_copy_move in CopyMove.py.


*-*

Now my question about the bug tracker.  A couple of months ago I used the
bug tracker here:
http://sourceforge.net/tracker/?group_id=46523&atid=446418 .  The lonely
bug presently there is mine.  I'm not one to complain about the length of
time it takes to fix bugs; if it takes a long time to fix then it takes a
long time to fix.  The fact that there are no other bugs in the tracker
and my bug hasn't received any responses yet leads me to believe that
nobody even looks there, and that this list is the best place to report
bugs.

If that is indeed the case, and nobody uses the tracker, I suggest
disabling it on SourceForge so future bugs don't get lost there. :-) 
FWIW, I'm on the Twisted dev team and we've been pretty happy with Roundup
for bug tracking.  I can certainly understand if nobody likes the sf
tracker. :-P

C

__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf