June 2013 - 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] #39451: qt4-creator-mac cannot install for arch(s) 'i386 x86_64'
by MacPorts 29 Sep '14

29 Sep '14

#39451: qt4-creator-mac cannot install for arch(s) 'i386 x86_64' ------------------------------+-------------------------------- Reporter: jamesfmarshall@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: ------------------------------+-------------------------------- This is the entire error message when I attempt a port upgrade outdated: {{{ ---> Computing dependencies for qt4-creator-mac. Error: Cannot install qt4-creator-mac for the arch(s) 'i386 x86_64' because Error: its dependency botan does not build for the required arch(s) by default Error: and does not have a universal variant. Error: Unable to upgrade port: architecture mismatch To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets }}} Any other info somewhere? -- Ticket URL: <https://trac.macports.org/ticket/39451> MacPorts <http://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #38158: afflib @3.6.12 Build failure - autoreconf
by MacPorts 29 Sep '14

29 Sep '14

#38158: afflib @3.6.12 Build failure - autoreconf ----------------------+-------------------------------- Reporter: djvasi@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: afflib ----------------------+-------------------------------- afflib fails to build with the following error: {{{ ---> Configuring afflib configure.ac:15: error: 'AM_CONFIG_HEADER': this macro is obsolete. You should use the 'AC_CONFIG_HEADERS' macro instead. /opt/local/share/aclocal-1.13/obsolete-err.m4:12: AM_CONFIG_HEADER is expanded from... configure.ac:15: the top level autom4te: /opt/local/bin/gm4 failed with exit status: 1 aclocal: error: echo failed with exit status: 1 autoreconf: aclocal failed with exit status: 1 Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_security_afflib/afflib/work/afflib-3.6.12" && autoreconf --install Exit code: 1 }}} I'm on OS X 10.7.5. The current autoconf on my system is from MacPorts, and is version 2.69. -- Ticket URL: <https://trac.macports.org/ticket/38158> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #36812: new port: pocketsphinx 0.7
by MacPorts 26 Sep '14

26 Sep '14

#36812: new port: pocketsphinx 0.7 ------------------------+-------------------------------- Reporter: qqshfox@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: | Port: pocketsphinx ------------------------+-------------------------------- Another speech recognition system from CMU. -- Ticket URL: <https://trac.macports.org/ticket/36812> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[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] #39412: Please document active_variant portgroup
by MacPorts 26 Sep '14

26 Sep '14

#39412: Please document active_variant portgroup -------------------------+--------------------- Reporter: thibaut@… | Owner: markd@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: guide | Version: 2.1.3 Keywords: | Port: -------------------------+--------------------- Hi, The ability to depend on a specific variant of a port has often been sought for. It is now provided by means of the active_variant port group, but this is not documented in the guide. It would be good to have: 1. a mention of the fact in Sect. 5.3, (dependencies); 2. complete documentation of the portgroup in 5.9 (portgroups). Kind regards, Thibaut. -- Ticket URL: <https://trac.macports.org/ticket/39412> MacPorts <http://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #39083: Add information about configure.sdkroot and configure.macosx_deployment_target
by MacPorts 26 Sep '14

26 Sep '14

#39083: Add information about configure.sdkroot and configure.macosx_deployment_target -------------------------+--------------------- Reporter: william@… | Owner: markd@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: guide | Version: 2.1.3 Keywords: | Port: -------------------------+--------------------- At present the guide has only a placeholder for the configure.macosx_deployment_target and related variables, and no mention at all of configure.sdkroot. It would be very useful if these (and any others that are missing) had /at least/ placeholders (even without any meaningful documentation), so that they may be discovered. I recently /guessed/ at the existence of the configure.sdkroot variable, and this was exactly what I needed to use to get round a problem while testing a port which didn't compile! It would have been quicker if I could have seen it somewhere in the guide. Also, an explanation of how to discover the list of valid variables directly from an installed port tree (for use when the documentation is outdated) would also be helpful. -- Ticket URL: <https://trac.macports.org/ticket/39083> MacPorts <http://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #38829: Nagios should use a separate group for the "command group"
by MacPorts 26 Sep '14

26 Sep '14

#38829: Nagios should use a separate group for the "command group" ------------------------+-------------------------------- Reporter: cubranic@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: ------------------------+-------------------------------- The installation instructions for [[http://nagios.sourceforge.net/docs/nagioscore/3/en/quickstart- fedora.html|Nagios]] create two Nagios-related groups: `nagios` for the daemon itself, and `nagcmd` for the command files. The port, however, uses the same group for both: {{{ add_users nagios group=nagios configure.args [...]\ --with-command-grp=nagios }}} The web server should be added to the command group as well. -- Ticket URL: <https://trac.macports.org/ticket/38829> MacPorts <http://www.macports.org/> Ports system for OS X

1 2