August 2012 - macports-tickets - lists.macosforge.org

[MacPorts] #33179: xymon and xymon-server disagree about whether clientlaunch.cfg should be registered to the port or not
by MacPorts 29 Sep '14

29 Sep '14

#33179: xymon and xymon-server disagree about whether clientlaunch.cfg should be registered to the port or not -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: fclaire@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: xymon -------------------------------------+-------------------------------------- Installing xymon, then uninstalling xymon, then installing xymon-server, results in an activation failure: {{{ $ sudo port install xymon-server ---> Computing dependencies for xymon-server ---> Fetching archive for xymon-server ---> Attempting to fetch xymon-server-4.3.7_0.darwin_10.x86_64.tbz2 from http://packages.macports.org/xymon-server ---> Fetching xymon-server ---> Verifying checksum(s) for xymon-server ---> Extracting xymon-server ---> Applying patches to xymon-server ---> Configuring xymon-server ---> Building xymon-server ---> Staging xymon-server into destroot ---> Installing xymon-server @4.3.7_0 ---> Activating xymon-server @4.3.7_0 Error: Target org.macports.activate returned: Image error: /opt/local/lib/xymon/client/etc/clientlaunch.cfg already exists and does not belong to a registered port. Unable to activate port xymon-server. Use 'port -f activate xymon-server' to force the activation. Log for xymon-server is at: /opt/local/var/macports/logs /_Users_rschmidt_macports_dports_net_xymon-server/xymon-server/main.log Error: Status 1 encountered during processing. To report a bug, see <http://guide.macports.org/#project.tickets> }}} -- Ticket URL: <https://trac.macports.org/ticket/33179> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #34826: new ports tcl84 @8.4.19_0, tk84 @8.4.19_0, fix for blt
by MacPorts 26 Sep '14

26 Sep '14

#34826: new ports tcl84 @8.4.19_0, tk84 @8.4.19_0, fix for blt ------------------------------+--------------------------------------------- Reporter: neumann@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Keywords: haspatch | Port: tcl84, tk84, blt ------------------------------+--------------------------------------------- As discussed on MacPorts User and Developer mailing list, here are two new ports for tcl84 and tk84 for ports requiring the old tcl version. One such port is blt, another one would be tclx. There are more currently broken ports out there (eg. otcl, tclcl) depending on tcl84; not sure, how important it is to fix these now; providing a tcl84 port is a first step helping for those as well. Without the patch, blt can be compiled with the patch provided in #34345, but then, it does not work (e.g. none of demos work). This is because blt was never ported properly to tcl8.5. With the patch from this ticket, blt is compiled against tcl84 and tk84, the demos work nicely. For the time being, basing blt on tck84 seems better than the approach sketched out in ticket #32599, where a version of blt from a different project was tried (http://pdqi.com/w/pw/pdqi/Wize/Blt) Tclx as it is in the current ports releases does not compile correctly. One correction would be to compile it against tcl84 (as indicated by my mail) but the better solution is to remove the dependency on tcl8.4 and compile it properly against tcl8.5 (the port named "tcl"). This could be done, when the ticket #33203 is committed. Attached is (a) a tar file containing all parts and (b) unified diff to make it easier to spot the changes. I have not changed the maintainers. All three ports are configured with threads-enabled (as discussed in macports, i have compiled tcl on my systems with threads enabled - as it is the case in all current unix-based tcl distributions) and all ports are running nicely. i have further (not yet submitted) ports requiring a threads-enabled tcl. As this is a "new port", it can't break previously running scripts. -- Ticket URL: <https://trac.macports.org/ticket/34826> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #31032: Split out new port for zabbix agentd to handle multiple startup items
by MacPorts 26 Sep '14

26 Sep '14

#31032: Split out new port for zabbix agentd to handle multiple startup items --------------------------------+------------------------------------------- Reporter: kwcheong@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.1 Keywords: | Port: --------------------------------+------------------------------------------- Since the port zabbix consist of proxy, server as well as agentd, splitted the agentd out is likely a better choice so that a machine have have the following scenario:- 1. zabbix server using zabbix port and zabbix agentd using zabbix_agentd port 2. zabbix proxy using zabbix port with +proxy variant and zabbix agentd using zabbix_agentd port 3. zabbix agentd only using zabbix_agentd port With another zabbix_agentd port, multiple startupitem for case 1 and 2 is feasible. -- Ticket URL: <https://trac.macports.org/ticket/31032> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #23117: spine port request (goes with cacti)
by MacPorts 26 Sep '14

26 Sep '14

#23117: spine port request (goes with cacti) -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.2 Keywords: | Port: spine, cacti -------------------------------------+-------------------------------------- We should have a port for spine, the high-performance C replacement for cacti's PHP polling script. http://www.cacti.net/spine_install_rhlnx.php http://www.cacti.net/downloads/spine/ http://www.cacti.net/downloads/docs/html/unix_configure_spine.html -- Ticket URL: <http://trac.macports.org/ticket/23117> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 1

[MacPorts] #34885: nagios-plugins does not list library dependencies
by MacPorts 26 Sep '14

26 Sep '14

#34885: nagios-plugins does not list library dependencies ------------------------------------------+--------------------------------- Reporter: dirk.schulz@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Keywords: missing library dependencies | Port: nagios-plugins ------------------------------------------+--------------------------------- sudo port deps nagios-plugins Full Name: nagios-plugins @1.4.15_4 Build Dependencies: fping, p5.12-net-snmp, p5.12-digest-sha1, p5.12 -digest-hmac, p5.12-crypt-des, openssl This leads to nagios plugins not working due to missing libraries when using port mpkg to package nagios-plugins for installation on macs without macports. -- Ticket URL: <https://trac.macports.org/ticket/34885> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #34702: Failed to install nagios-plugins
by MacPorts 26 Sep '14

26 Sep '14

#34702: Failed to install nagios-plugins -----------------------------+---------------------------------------------- Reporter: devinb@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.1 Keywords: | Port: -----------------------------+---------------------------------------------- Using: MacPorts 2.1.1 Attempting to get nagios installed via MacPorts and keep running into this problem {{{ $ sudo port install nagios ---> Computing dependencies for nagios ---> Dependencies to be installed: nagios-plugins ---> Building nagios-plugins Error: org.macports.build for port nagios-plugins returned: command execution failed Error: Failed to install nagios-plugins Please see the log file for port nagios-plugins for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_ports_net_nagios-plugins/nagios-plugins/main.log Error: The following dependencies were not installed: nagios-plugins To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port nagios failed }}} -- Ticket URL: <https://trac.macports.org/ticket/34702> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #33697: Incomplete uninstall script
by MacPorts 26 Sep '14

26 Sep '14

#33697: Incomplete uninstall script --------------------------------+------------------------------------------- Reporter: neville@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: MacPorts 2.0.5 Component: ports | Version: 2.0.4 Keywords: | Port: --------------------------------+------------------------------------------- The uninstall script at http://guide.macports.org/chunked/installing.macports.uninstalling.html fails to remove /private/var/db/dslocal/nodes/Default/users/macports.plist /private/var/db/dslocal/nodes/Default/groups/macports.plist which leaves user-name (macports), group (macports) and ID (typically 503) on the database causing confusion and minor inconvenience. Users become aware of this when changing permissions in Get Info or using AppleJack etc. Removing these 2 plist files works with Leopard and probably works with later OSs. Correcting and testing the script should be relatively easy. -- Ticket URL: <https://trac.macports.org/ticket/33697> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6

[MacPorts] #33479: p5.12-cgi-speedycgi fails to build with clang
by MacPorts 26 Sep '14

26 Sep '14

#33479: p5.12-cgi-speedycgi fails to build with clang ------------------------------------+--------------------------------------- Reporter: arno.barbier@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.4 Keywords: | Port: p5.12-cgi-speedycgi ------------------------------------+--------------------------------------- Hello, I couldn't build p5.12-cgi-speedycgi due to the following error: {{{ :info:build /usr/bin/clang -o speedy_backend speedy_backend_main.o speedy_perl.o speedy_util.o speedy_sig.o speedy_frontend.o speedy_backend.o speedy_file.o speedy_slot.o speedy_poll.o speedy_ipc.o speedy_group.o speedy_script.o speedy_opt.o speedy_optdefs.o xsinit.o -L/opt/local/lib -fstack-protector -L/opt/local/lib/perl5/5.12.3/darwin- multi-2level/CORE -lperl -ldl -lm -lutil -lc :info:build Undefined symbols for architecture x86_64: :info:build "_speedy_file_set_state", referenced from: :info:build _main in speedy_backend_main.o :info:build _start_child in speedy_backend_main.o :info:build _cleanup_after_perl in speedy_perl.o :info:build _speedy_perl_run in speedy_perl.o :info:build _speedy_file_fork_child in speedy_file.o :info:build _speedy_group_lock in speedy_group.o :info:build "_speedy_util_getpid", referenced from: :info:build _main in speedy_backend_main.o :info:build _start_child in speedy_backend_main.o :info:build _cleanup_after_perl in speedy_perl.o :info:build _speedy_perl_run in speedy_perl.o :info:build _file_lock in speedy_file.o :info:build "_speedy_util_stat_devino", referenced from: :info:build _speedy_perl_init in speedy_perl.o :info:build _quick_cd in speedy_perl.o :info:build _chdir_path in speedy_perl.o :info:build "_speedy_opt_script_fname", referenced from: :info:build _speedy_perl_init in speedy_perl.o :info:build _speedy_script_open_failure in speedy_script.o :info:build _speedy_script_open in speedy_script.o :info:build _speedy_script_getstat in speedy_script.o :info:build _speedy_script_find in speedy_script.o :info:build _speedy_script_mmap in speedy_script.o :info:build "_speedy_file_fd_is_suspect", referenced from: :info:build _cleanup_after_perl in speedy_perl.o :info:build "_speedy_util_open_stat", referenced from: :info:build _load_script in speedy_perl.o :info:build _speedy_script_open_failure in speedy_script.o :info:build "_speedy_util_time", referenced from: :info:build _file_lock in speedy_file.o :info:build _speedy_script_open_failure in speedy_script.o :info:build (maybe you meant: _speedy_util_time_invalidate) :info:build "_speedy_util_gettimeofday", referenced from: :info:build _file_lock in speedy_file.o :info:build "_speedy_util_geteuid", referenced from: :info:build _speedy_ipc_listen in speedy_ipc.o :info:build ld: symbol(s) not found for architecture x86_64 :info:build clang: error: linker command failed with exit code 1 (use -v to see invocation) :info:build make[1]: *** [speedy_backend] Error 1 }}} The package source name is p5.12-cgi- speedycgi-2.220.0_11.darwin_11.x86_64.tbz2 Thanks for your help -- Ticket URL: <https://trac.macports.org/ticket/33479> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6

[MacPorts] #32428: PortGroup muniversal not documented
by MacPorts 26 Sep '14

26 Sep '14

#32428: PortGroup muniversal not documented --------------------------------+------------------------------------------- Reporter: abarnert@… | Owner: markd@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: guide | Version: 2.0.3 Keywords: | Port: --------------------------------+------------------------------------------- While trying to work around #32427 I ran into the problem that I have no idea what exactly !PortGroup muniversal does, or how or why. While searching this site for muniversal, I found a number of other bugs that were either caused or fixed by changing a port to muniversal, but there's no mention of it in ProblemHotlist. The Guide describes a handful of portgroups (under 5.9): gnustep, haskell, perl5, python, python2, ruby, xcode), but not muniversal. It also has an explanation on how to set up universal builds, with no mention of muniversal. The manpage portgroup(7) describes a different set: gnustep, perl5, python24, python25, python30, ruby, xcode. Looking in $prefix/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/ there are 34 groups, many of which have brief comments explaining their purpose, but muniversal (which seems to be one of the more complex ones) doesn't. The PortfileRecipes page has some information on controlling -arch and related things; I don't know if muniversal is relevant here. A ticket search, a Google site search, a Google web search, etc. turned up lots and lots of discussion about applying muniversal to specific ports, but I couldn't find anything explaining muniversal. From the name, it's pretty obvious that it has something to do with universal builds, and a quick scan of the source confirms that. From what I can tell, just including the portgroup without doing anything else causes +universal builds to be done by building each architecture separately and then merging, instead of attempting a single build with multiple architectures. In summary, I think muniversal needs to be documented in: * Guide section 5.3.7.1 (Configure Universal) * Guide section 5.9 (!PortGroups) * Man page portgroup(7) * PortfileRecipes * ProblemHotlist * Header comments in the group file itself Ideally these should explain what it does, when and why you should (or shouldn't) use it, how to experiment with turning it on and off to resolve common problems with +universal builds, etc. -- Ticket URL: <https://trac.macports.org/ticket/32428> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #32034: snort: libsf_engine.dylib: No such file or directory
by MacPorts 26 Sep '14

26 Sep '14

#32034: snort: libsf_engine.dylib: No such file or directory -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: markd@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: haspatch | Port: snort -------------------------------------+-------------------------------------- Actually trying to use snort produces the error message: {{{ /opt/local/lib/snort_dynamicengine/libsf_engine.dylib: No such file or directory }}} as [http://lists.macosforge.org/pipermail/macports- users/2011-November/026101.html reported by Fyodor Vassiley with a reproduction recipe on the mailing list]. snort installs the file libsf_engine.so there, but then later looks for libsf_engine.dylib, which isn't there. So it would be best if the libraries were installed with the correct .dylib extension in the first place. [http://lists.macosforge.org/pipermail/macports- users/2011-November/026133.html Jean-Francois Gobin provided a patch on the mailing list], but it must be applied to the Makefile after the configure phase has run. I don't know if there's a way the patch could be done at the normal time, during the patch phase. Perhaps a patch to the configure script. -- Ticket URL: <https://trac.macports.org/ticket/32034> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4