December 2013 - macports-tickets - lists.macosforge.org

[MacPorts] #40744: macports-built expect @5.45_4: crashes when used in a dejagnu testsuite
by MacPorts 26 Sep '14

26 Sep '14

#40744: macports-built expect @5.45_4: crashes when used in a dejagnu testsuite ---------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: | Port: expect ---------------------+-------------------------------- crash log is attached. I tried forcing the use of the system `expect`, but the Makefile must've ignored it, because it went back to using the Macports one... -- Ticket URL: <https://trac.macports.org/ticket/40744> MacPorts <http://www.macports.org/> Ports system for OS X

1 2

[MacPorts] #39667: ntopng: new port, to replace ntop port
by MacPorts 26 Sep '14

26 Sep '14

#39667: ntopng: new port, to replace ntop port --------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: ntopng --------------------------+-------------------------------- ntop has been rewritten as ntopng: http://www.ntop.org/ntop/ntop-is-back-ntopng-1-0-just-released/ -- Ticket URL: <https://trac.macports.org/ticket/39667> MacPorts <http://www.macports.org/> Ports system for OS X

1 3

[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] #41937: Cacti port fails on Mavericks
by MacPorts 26 Sep '14

26 Sep '14

#41937: Cacti port fails on Mavericks ----------------------------------------+-------------------------------- Reporter: palmj@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Keywords: cacti mysql mavericks 10.9 | Port: cacti ----------------------------------------+-------------------------------- The Cacti port is dependent on the MySQL5 port, which will not install under Mavericks. However, this piece has been fixed, replaced with MySQL56. The Cacti port needs to be updated to the right MySQL. -- Ticket URL: <https://trac.macports.org/ticket/41937> MacPorts <http://www.macports.org/> Ports system for OS X

1 6

[MacPorts] #41239: Error in MacPorts Guide section "2.1. Install X11"
by MacPorts 26 Sep '14

26 Sep '14

#41239: Error in MacPorts Guide section "2.1. Install X11" ---------------------------------+-------------------- Reporter: zhimingwangpublic@… | Owner: jmpp@… Type: defect | Status: new Priority: Normal | Milestone: Component: website | Version: 2.2.1 Keywords: guide | Port: ---------------------------------+-------------------- The section "2.1. Install X11" of MacPorts Guide (guide.macports.org) says: As of Mac OS X 10.5 Leopard, X11.app is included in the default installation. You can just skip this section for any later version of Mac OS X. However, starting from 10.7 Lion (or 10.8 Mountain Lion? I couldn't remember exactly), X11 is **not** included in OS X. Folks need to go to http://xquartz.macosforge.org/ to download XQuartz. More about this in Apple's knowledge base http://support.apple.com/kb/ht5293. -- Ticket URL: <https://trac.macports.org/ticket/41239> MacPorts <http://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #40700: Installing Nedi 1.0.7_3 at Mac OS X 10.8.5 failed
by MacPorts 26 Sep '14

26 Sep '14

#40700: Installing Nedi 1.0.7_3 at Mac OS X 10.8.5 failed --------------------------------------+-------------------------------- Reporter: Peter.Stange@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: NeDi (Network Discovery) | Port: --------------------------------------+-------------------------------- Hello installing Nedi 1.0.7_3 at Mac OS X 10.8.5 failed with following message. Any hints? Regards Peter 1 xxx@myMac $ sudo su[[BR]] 0 root@myMac $ port -v install nedi[[BR]] ---> Computing dependencies for nedi.[[BR]] ---> Installing nedi @1.0.7_3[[BR]] xinstall: /opt/local/var/macports/sources/rsync.macports.org/release/ports/net/nedi/files/org.macports.nedisyslog.plist -> \[[BR]] /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_nedi/nedi/work/destroot/opt/local/etc/LaunchDaemons/org.macports.nedisyslog//org.macports.nedisyslog.plist[[BR]] ln: ./org.macports.nedisyslog.plist: Operation not permitted[[BR]] Command failed: cd /Library/LaunchDaemons && ln -sf /opt/local/etc/LaunchDaemons/org.macports.nedisyslog/org.macports.nedisyslog.plist[[BR]] Exit code: 1[[BR]] Error: org.macports.install for port nedi returned: command execution failed[[BR]] Warning: targets not executed for nedi: org.macports.activate org.macports.install[[BR]] Please see the log file for port nedi for details:[[BR]] /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_nedi/nedi/main.log[[BR]] To report a bug, follow the instructions in the guide:[[BR]] http://guide.macports.org/#project.tickets[[BR]] Error: Processing of port nedi failed[[BR]] 1 root$ -- Ticket URL: <https://trac.macports.org/ticket/40700> MacPorts <http://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #40556: Missing dependency in SmokePing
by MacPorts 26 Sep '14

26 Sep '14

#40556: Missing dependency in SmokePing ------------------------+-------------------------------- Reporter: macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: MacPorts Future Component: ports | Version: 2.2.0 Keywords: | Port: smokeping ------------------------+-------------------------------- mod_fcgid Is required for SmokePing, but missing from the dependencies. A few notes on the documentation:- local0 and local1 for syslog facility need to be alligned (local1 IMHO) fping path:- /opt/local/sbin/fping Some startup errors I encountered:- $ sudo /opt/local/bin/smokeping --check Can't locate Smokeping.pm in @INC (@INC contains: /opt/local/lib/smokeping /opt/local/lib/perl5/vendor_perl/5.12.4/darwin-thread-multi- 2level/auto/RRDs /opt/local/lib/perl5/site_perl/5.12.4/darwin-thread- multi-2level /opt/local/lib/perl5/site_perl/5.12.4 /opt/local/lib/perl5/vendor_perl/5.12.4/darwin-thread-multi-2level /opt/local/lib/perl5/vendor_perl/5.12.4 /opt/local/lib/perl5/5.12.4 /darwin-thread-multi-2level /opt/local/lib/perl5/5.12.4 /opt/local/lib/perl5/site_perl /opt/local/lib/perl5/vendor_perl .) at /opt/local/bin/smokeping line 12. BEGIN failed--compilation aborted at /opt/local/bin/smokeping line 12. $ which perl /opt/local/bin/perl ==> it's actually in /opt/local/lib ERROR: can't open /opt/local/etc/smokeping/config: No such file or directory glaw@mm01.home.gateway:/opt/local/lib 2013-09-22 10:34:26 ... at which point I gave up... ==> docs and installation goes into /opt/local/etc (no subdir) -- Ticket URL: <https://trac.macports.org/ticket/40556> MacPorts <http://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #40353: Ticket Guidelines should include instructions for upgrade requests
by MacPorts 26 Sep '14

26 Sep '14

#40353: Ticket Guidelines should include instructions for upgrade requests -------------------------+--------------------- Reporter: tal@… | Owner: markd@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: guide | Version: 2.2.0 Keywords: | Port: -------------------------+--------------------- http://guide.macports.org/#project.tickets As a newcomer to MacPorts (but not to Macs, nor Ports :-) ), it wasn't clear how to report that a port is out of date. I learned by filing a badly formatted ticket, and being corrected. This wasted your time, for which I apologize. Since people that need to report out of dates this are often going to be newcomers, my suggestion is to make the docs "match the audience" a bit better by being more "hand-holding". Two points: (a) it wasn't obvious to set type=upgrade, component=ports. (b) people should be told to CC: the maintainers (and that "{{{port info --maintainers $portname}}}" reveals who that is). Suggested fix: Between 7.3.1 and 7.3.2 insert a new section similar to this: 7.3.x Reporting out-of-date ports / requesting updates to a port * Report out of date ports by opening a bug. See (link to 7.1.3. Trac Ticket Guidelines) * When creating the bug, set: * Summary: [port] [version] [concise description] * Example: "ghostscript @9.0.3_1 please upgrade to newest version 9.0.9" * Type: upgrade * Component: ports * CC: the maintainer. To determine this, see the output of: {{{port info --maintainers PORT}}} * Example: {{{port info --maintainers ghostscript}}} * Port: the name of the port [Note that the fields are listed in the same order as on the form, with the same capitalization. These things matter to newcomers.] Also, in section "7.1.3. Trac Ticket Guidelines" add to the end of the first paragraph: "... If you are reporting an out-of-date port, please see (link to the above section)." Thanks! -- Ticket URL: <https://trac.macports.org/ticket/40353> MacPorts <http://www.macports.org/> Ports system for OS X

1 1