The current version of sysutils/bbcp (bbcp-20120520) does not support data transfer over IPv6 (which is a problem in an IPv6-only environment). Please upgrade to a more recent version, such as 14.07.01.00.0 (or at least 14.04.14.00.0). The bbcp web page (http://www.slac.stanford.edu/~abh/bbcp/) states the following changes: 1.11 New Features Version 14.07.01.00.0 of documented here has the following new features: · The new –gross option forces bbcp to copy empty directory structures in recursive mode. · The new –mkdir option creates the destination directory for a recursive copy should it not exist. · The new –symlinks option specifies how symbolic links are to be handled during a recursive copy. Version 14.04.14.00.0 of documented here has the following new features: · Dual stack IPv6 mode is fully functional and is the default mode of operation. The new –ipv4 option forces bbcp to use the IPv4 TCP stack. · The new –license option prints the license under which bbcp is distributed. · The new –version option displays bbcp’s version number installed on the current host. · The BBCP_ALLOWPP environmental variable may be used to restrict program pipes to a specified set of programs or disable the feature altogether. Note the license has changed with 14.04.14.00.0, previously it was a BSD license, now it is a GNU Lesser General Public License.
Mark, it's not like I don't disagree, but PRs aren't supposed to be used for update requests. We have a tool called "portscout" that lets the maintainer know that a new version is ready. I'm notifying the maintainer in CC. If, in two weeks, he doesn't respond, or even before then, feel free to provide a patch that will update the port. If the maintainer doesn't respond in two weeks the PR is considered approved through silence (aka "timed out"). Your chances of getting an update go up tremendously if you provide a patch instead of requesting a non-maintainer to do the work. (given as advice)
Closing upgrade request PR -- no traffic on it.
Resolved by Bug 196746 *** This bug has been marked as a duplicate of bug 196746 ***