Bug 192405 - Please upgrade sysutils/bbcp, current version does not support IPv6
Summary: Please upgrade sysutils/bbcp, current version does not support IPv6
Status: Closed DUPLICATE of bug 196746
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-05 18:44 UTC by Mark.Martinec
Modified: 2015-01-29 17:21 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark.Martinec 2014-08-05 18:44:30 UTC
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.
Comment 1 John Marino freebsd_committer freebsd_triage 2014-08-06 08:43:55 UTC
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)
Comment 2 John Marino freebsd_committer freebsd_triage 2014-10-05 22:23:13 UTC
Closing upgrade request PR -- no traffic on it.
Comment 3 Mark.Martinec 2015-01-29 17:21:02 UTC
Resolved by Bug 196746

*** This bug has been marked as a duplicate of bug 196746 ***