Re: [Audacity-devel] audacity 1.3.2b ftp patch
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: JP <pen...@rf...> - 2007-03-30 22:02:06
|
> -----Original Message----- > From: aud...@li... > [mailto:aud...@li...] On > Behalf Of Richard Ash > Sent: Friday, March 30, 2007 4:14 PM > To: jp...@rf...; aud...@li... > Subject: Re: [Audacity-devel] audacity 1.3.2b ftp patch snip > When I try to use the current (unpatched) audacity ftp, I can > connect to the server, and get a directory listing, but when > I try to upload a file it tries to use the full local path as > the upload file name, which fails, and then hangs. > > With the patch applied, it hangs before I can get a directory > listing after connecting. It did work once, but as soon as I > did something it froze again. > > If I click disconnect, then the FTP server disconects, but > audacity is left frozen afterwards. > > So, all in all it's not that the patch is necessarily broken, > but it doesn't fix it either, so I can't really test whether > the patch does as advertised. > > Richard Hmmm that's odd, it works ok here other than some unrelated bugs, and we tested it on quite a few files. Ftp server is linux. One of the unrelated bugs I have noticed is that once a file is uploaded, the contents of the target directory get hidden and you cannot navigate to the parent directory without disconnecting and reconnecting first. That behavior was present before I patched though, and I figured I'd take on one thing at a time. Thanks very much for checking it out. I will do some more testing here. I take it you were testing it on a Linux machine? Regards - ~~~~~~~~~~~~~~~~~~~~~~~~~~ John Penovich Radio Free Asia 2025 M Street, NW Ste 300 Washington DC 20036 (202) 587-2042 ~~~~~~~~~~~~~~~~~~~~~~~~~~ CONFIDENTIAL COMMUNICATION This e-mail message is intended only for the use of the addressee and may contain information that is privileged and confidential. Any unauthorized dissemination, distribution, or copying is strictly prohibited. If you receive this transmission in error, please contact network[at]rfa[dot]org Visit us at www.rfa.org or www.techweb.rfa.org |