[Bug 219383] net-mgmt/p5-FusionInventory-Agent: Update to 2.3.19 and remove outdated secondary ports

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Thu May 18 15:44:29 UTC 2017


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219383

            Bug ID: 219383
           Summary: net-mgmt/p5-FusionInventory-Agent: Update to 2.3.19
                    and remove outdated secondary ports
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Ports Framework
          Assignee: portmgr at FreeBSD.org
          Reporter: freebsd at simweb.ch
                CC: freebsd-ports-bugs at FreeBSD.org

Created attachment 182704
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=182704&action=edit
Bump FusionInventory Agent to 2.3.19

Hi

Hereby is a patch that has so far passed a quick real-life check on 10.3 amd64
and seen testport usage on 11.0, 10.3 on both i386 and amd64.

Explanation on the changes beyond version bump:
* Upstream maintainer at CPAN has changed from GROUSSE to GBOUGARD
* Removal p5-POE-Component-Client-Ping and net/p5-POE-Component-Client-Ping
dependencies according to upstream changelog.
* Addition of p5-Parallel-ForkManager according to upstream changelog.
* Change at USE_RC_SUBR is to make portlint happier

Link to upstream changelog:
http://cpansearch.perl.org/src/GBOUGARD/FusionInventory-Agent-2.3.19/Changes

The second 2 patches would remove the p5-FusionInventory-Task-SNMPQuery and
-NetDiscovery ports. I have both mentioned in bug #204632 (Comment 1) that they
wouldn't work with the 2.3 branch of the FusionInventory agent. Things got lost
in transition but in 2017 there is no real meaning in keeping these ports in
the tree so the second and third patch remove these individually.

If there is any additional information that you'd like to get, let me know.

Best regards
Mathieu

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the freebsd-ports-bugs mailing list