FileZilla fetch fails

[jries@…]

$ sudo port install FileZilla
dyld: DYLD_ environment variables being ignored because main executable (/usr/bin/sudo) is setuid or setgid
Password:
--->  Computing dependencies for FileZilla
--->  Fetching distfiles for FileZilla
--->  Attempting to fetch FileZilla3-src.tar.bz2 from http://distfiles.macports.org/FileZilla/2014-06-17
--->  Attempting to fetch FileZilla3-src.tar.bz2 from http://sea.us.distfiles.macports.org/macports/distfiles/FileZilla/2014-06-17
--->  Attempting to fetch FileZilla3-src.tar.bz2 from http://ykf.ca.distfiles.macports.org/MacPorts/mpdistfiles/FileZilla/2014-06-17
--->  Attempting to fetch FileZilla3-src.tar.bz2 from http://lil.fr.distfiles.macports.org/FileZilla/2014-06-17
--->  Attempting to fetch FileZilla3-src.tar.bz2 from http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/FileZilla/2014-06-17
--->  Attempting to fetch FileZilla3-src.tar.bz2 from https://filezilla-project.org/nightlies/2014-06-17
--->  Attempting to fetch FileZilla3-src.tar.bz2 from http://aarnet.au.distfiles.macports.org/pub/macports/mpdistfiles/FileZilla/2014-06-17
--->  Attempting to fetch FileZilla3-src.tar.bz2 from http://cjj.kr.distfiles.macports.org/FileZilla/2014-06-17
--->  Attempting to fetch FileZilla3-src.tar.bz2 from http://fco.it.distfiles.macports.org/mirrors/macports-distfiles/FileZilla/2014-06-17
--->  Attempting to fetch FileZilla3-src.tar.bz2 from http://nue.de.distfiles.macports.org/macports/distfiles/FileZilla/2014-06-17
--->  Attempting to fetch FileZilla3-src.tar.bz2 from http://her.gr.distfiles.macports.org/mirrors/macports/mpdistfiles/FileZilla/2014-06-17
--->  Attempting to fetch FileZilla3-src.tar.bz2 from http://jog.id.distfiles.macports.org/macports/mpdistfiles/FileZilla/2014-06-17
--->  Attempting to fetch FileZilla3-src.tar.bz2 from http://svn.macports.org/repository/macports/distfiles/FileZilla
Error: org.macports.fetch for port FileZilla returned: fetch failed
Please see the log file for port FileZilla for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_www_FileZilla/FileZilla/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port FileZilla failed

I actually ran across this during a "port upgrade outdated". I had to uninstall both Filezilla and GitX (same problem) to get the update to complete.

For what it's worth, I'm running OSX 10.8.5 (Mountain Lion). I did check one of the mirror URLs and verified that the FileZilla directory was not present.

[mf2k (Frank Schima)]

In the future, please use WikiFormatting and Cc the port maintainers (port info --maintainers FileZilla).

[jries@…]

Replying to mf2k@…:

In the future, please use WikiFormatting and Cc the port maintainers (port info --maintainers FileZilla).

I noticed the results as soon as I posted, but saw no way to fix it ex post facto. Sorry.

[mojca (Mojca Miklavec)]

The nightly versions are deleted from the main server every few days, but I would really like to know why the file isn't mirrored. What's the best thing to do in such cases (I still have the file)?

Apart from that we have a problem: the latest versions switched to C++11. Which makes the port useless on < 10.9 unless:

• someone cares enough to revert a few trivial changes to make the code compile on pre-C++11 (it's doable)
• we link against libc++ or use gcc 4.8 (both options are asking for problems)
• we switch the whole MacPorts to libc++ one day ...

[jries@…]

I actually compile my own employer's codebase with gcc 4.8 as we went to C++11 a couple of years ago, but I can understand the caution. I was distressed when my upgrade to Mavericks prevented the codebase from compiling successfully at all; I downgraded thereafter and have been reluctant to try again until I have time to fix any resulting issues.

[rudloff@…]

Maybe we could solve that by using SVN to fetch the code instead ?

[cooljeanius (Eric Gallager)]

Cc Me!

[mojca (Mojca Miklavec)]

I committed r121570 as a temporary workaround.

We still need to figure out what to do with support for < 10.9 after version 3.9.0 gets released.

[mojca (Mojca Miklavec)]

Please let me know if this patch fixes the problem. And please let me know if it works correctly on 10.8. Because it behaves in a strange way on 10.7 since the upgrade to wx 3.0 and the author cannot reproduce the behaviour on 10.9.

[jries@…]

I successfully compiled and installed it, and it's running as I type. Thank you very much. It looks like I'm going to have to bite the bullet and do the upgrade to Maverick soon.