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

[MacPorts] #23118: cacti logs and databases would be better stored under ${prefix}/var
by MacPorts 25 Sep '14

25 Sep '14

#23118: cacti logs and databases would be better stored under ${prefix}/var -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: markd@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: cacti -------------------------------------+-------------------------------------- cacti stores its log file in the log directory inside its directory. It would fit better with the MacPorts hierarchy if the log were stored in ${prefix}/var/log/${name}. Similarly, the round robin database is stored in the rra directory inside its directory. A better fit with the MacPorts mtree would be ${prefix}/var/db/${name} (or ${prefix}/var/db/${name}/rra if we anticipate there being other cacti databases other than those in the rra directory). -- Ticket URL: <http://trac.macports.org/ticket/23118> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 1

[MacPorts] #23116: cacti shows warnings for deprecated functions with php 5.3
by MacPorts 25 Sep '14

25 Sep '14

#23116: cacti shows warnings for deprecated functions with php 5.3 -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: markd@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.2 Keywords: | Port: cacti -------------------------------------+-------------------------------------- cacti doesn't work so well with php 5.3 because it uses functions which are now deprecated, and because cacti configures itself to show all errors, so if display_errors is on, like it is on my development machine, I get tons of "Deprecated: Function ereg_replace() is deprecated" messages in the browser window. This is already patched in svn something like [http://bugs.cacti.net/view.php?id=1568 this] but a simpler solution for now could be to patch global.php to set error_reporting to `E_ALL & ~E_DEPRECATED` instead of `E_ALL`. -- Ticket URL: <http://trac.macports.org/ticket/23116> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 1

[MacPorts] #23113: cacti should install a sample config file
by MacPorts 25 Sep '14

25 Sep '14

#23113: cacti should install a sample config file -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: markd@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.2 Keywords: | Port: cacti -------------------------------------+-------------------------------------- cacti currently installs a file config.php, then the port prints instructions advising the user to edit this file. The user's changes will be lost when the user upgrades the port. The port should instead install a sample config file, e.g. config.php.sample, and advise the user to copy this to config.php and edit it. -- Ticket URL: <http://trac.macports.org/ticket/23113> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #22923: nfsen: update to 1.3.2
by MacPorts 25 Sep '14

25 Sep '14

#22923: nfsen: update to 1.3.2 -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: markd@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.1 Keywords: haspatch | Port: nfsen -------------------------------------+-------------------------------------- Attached is a patch to make several changes to nfsen: * update to 1.3.2 * fix livecheck * add the license info to the portfile * fix a typo in the install.pl patchfile I can't test whether it works, however, because [ticket:22922 nfsen doesn't build]. -- Ticket URL: <http://trac.macports.org/ticket/22923> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #22922: nfsen: Can't locate NfSen.pm in @INC
by MacPorts 25 Sep '14

25 Sep '14

#22922: nfsen: Can't locate NfSen.pm in @INC -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: markd@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.1 Keywords: | Port: nfsen -------------------------------------+-------------------------------------- nfsen doesn't install: {{{ DEBUG: Executing org.macports.destroot (nfsen) Can't locate NfSen.pm in @INC (@INC contains: ./libexec ./installer-items /opt/local/lib/perl5/site_perl/5.8.9/darwin-2level /opt/local/lib/perl5/site_perl/5.8.9 /opt/local/lib/perl5/site_perl /opt/local/lib/perl5/vendor_perl/5.8.9/darwin-2level /opt/local/lib/perl5/vendor_perl/5.8.9 /opt/local/lib/perl5/vendor_perl /opt/local/lib/perl5/5.8.9/darwin-2level /opt/local/lib/perl5/5.8.9 . /opt/local/libexec/nfsen /opt/local/var/macports/build/_Users_rschmidt_macports_dports_net_nfsen/work/destroot/opt/local/libexec/nfsen) at /opt/local/var/macports/build/_Users_rschmidt_macports_dports_net_nfsen/work/nfsen-1.3.2/install.pl line 44. BEGIN failed--compilation aborted at /opt/local/var/macports/build/_Users_rschmidt_macports_dports_net_nfsen/work/nfsen-1.3.2/install.pl line 44. Error: Target org.macports.destroot returned: shell command "/opt/local/bin/perl /opt/local/var/macports/build/_Users_rschmidt_macports_dports_net_nfsen/work/nfsen-1.3.2/install.pl /opt/local/var/macports/build/_Users_rschmidt_macports_dports_net_nfsen/work/nfsen-1.3.2/etc /nfsen-dist.conf" returned error 2 }}} This was [http://lists.macosforge.org/pipermail/macports- users/2009-December/018000.html reported by Noah on the mailing list]. -- Ticket URL: <http://trac.macports.org/ticket/22922> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6

[MacPorts] #22449: StartupItems page could be clearer?
by MacPorts 25 Sep '14

25 Sep '14

#22449: StartupItems page could be clearer? ---------------------------------+------------------------------------------ Reporter: dreamcat4@… | Owner: markd@… Type: request | Status: new Priority: High | Milestone: MacPorts 1.8.2 Component: guide | Version: 1.8.1 Keywords: launchd startupitem | Port: ---------------------------------+------------------------------------------ Hi! The macports guide: http://ruderich.com/macports/chunked/ch05s07.html Just isn't quite clear enough when talking about startup items / daemondo / launchd plists. We hope it may be improved in three areas: 1) Daemondo command-line arguments (string quoting): The section 5.7.2 Note: ---- Do not wrap values in quotes if passing arguments to the daemon; “executable” StartupItem elements must be tagged individually so the spaces between arguments serve as delimiters for “string” tags. For example, this startupitem key/value pair: startupitem.executable ${prefix}/sbin/vm-pop3d -d 10 -t 600 ---- This explanatory note is well intentions, However it its just a little too unclear. A user may wrap the entire command string in quotes. The explanatory note says nothing against this (and execvp fails). TCL does not strip any outside quotes and therefore it would be better to say: "Do use quotes anywhere in the command string" rather than "Do not wrap values in quotes if passing arguments". BUT "A quoted string will be passed as-is.", "unlike regular shell command, quotes will not be stripped". etc. A clearer explanation (with examples) is provided on the mailing list thread. Please see the mailinglist thread for full details: http://www.mail-archive.com/macports- users(a)lists.macosforge.org/msg16988.html 2) port load / port unload command not documented. This is a new feature, recently introduced into MacPorts. But it isn't mentioned anywhere in section 5.7.4. It seem to be applicable to daemondo items only. So that would correspond to plists created by "startupitem.executable" and "startupitem <script>" methods. Or a manually created script that called daaemondo. "port load daemondo-label" "port unload daemondo-label" See the blog post: http://www.reasonablyopinionated.com/2009/06/intro-to-using-launchctl- with-macports.html It is also known that the command: "port load tagname" will work globally for all plist files. Or only daemondo plist files 3) Manual plists in files/ directory Users can only create one plist file per Portfile. It may be the case for a complex software service, multiple plists need to be used. It would be nice to see a mention at the end of the page that explains briefly how you can put extra manual plists into files/ directory of a port. Thank you. For all 1),2),3) Answers please see mailinglist dicussion: http://www.mail-archive.com/macports- users(a)lists.macosforge.org/msg16988.html We were all quite confused but got there in the end ! -- Ticket URL: <http://trac.macports.org/ticket/22449> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #22349: Addition to the MacPorts GUIDELINE
by MacPorts 25 Sep '14

25 Sep '14

#22349: Addition to the MacPorts GUIDELINE ----------------------------------+----------------------------------------- Reporter: dee@… | Owner: markd@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: guide | Version: 1.8.1 Keywords: XCode OpenGL | Port: ----------------------------------+----------------------------------------- Need to add.. OpenGL SDK to the list REQUIRED when installing XCode for use with MacPorts -- Ticket URL: <http://trac.macports.org/ticket/22349> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #21046: Guide: mention using -append/-delete in 4.2 Creating a Portfile
by MacPorts 25 Sep '14

25 Sep '14

#21046: Guide: mention using -append/-delete in 4.2 Creating a Portfile -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: markd@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: guide | Version: Keywords: | Port: -------------------------------------+-------------------------------------- Jim Busser sent this Guide feedback to macports-mgr: {{{ Under 4.2 Creating a Portfile > 14. Port dependencies where it says A port's dependencies are ports that must be installed before another port is installed. and gives the example depends_lib might it be worth cautioning to see 5.3.2.1 (bullet 2) on preferred use of the -append, -delete keyword modifiers }}} This should be considered not only for the `depends_lib` example but also for the `configure.args` example and the `categories` example, since portgroups commonly define those. -- Ticket URL: <http://trac.macports.org/ticket/21046> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #19367: ntop build succeeds but staging fails
by MacPorts 25 Sep '14

25 Sep '14

#19367: ntop build succeeds but staging fails -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: markd@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.1 Keywords: | Port: ntop -------------------------------------+-------------------------------------- On my Intel Mac with Mac OS X 10.4.11, Xcode 2.5 and MacPorts 1.7.1, ntop builds, but then fails to stage: {{{ DEBUG: Assembled command: 'cd "/mp/var/macports/build/_Users_rschmidt_macports_dports_net_ntop/work/ntop-3.3.8" && gnumake install install-data-as DESTDIR=/mp/var/macports/build/_Users_rschmidt_macports_dports_net_ntop/work/destroot' Making install in . test -z "/mp/lib" || /mp/bin/gmkdir -p "/mp/var/macports/build/_Users_rschmidt_macports_dports_net_ntop/work/destroot/mp/lib" /bin/sh ./libtool --mode=install /usr/bin/install -c 'libntop.la' '/mp/var/macports/build/_Users_rschmidt_macports_dports_net_ntop/work/destroot/mp/lib/libntop.la' /usr/bin/install -c .libs/libntop-3.3.8.dylib /mp/var/macports/build/_Users_rschmidt_macports_dports_net_ntop/work/destroot/mp/lib/libntop-3.3.8.dylib (cd /mp/var/macports/build/_Users_rschmidt_macports_dports_net_ntop/work/destroot/mp/lib && rm -f libntop.dylib && ln -s libntop-3.3.8.dylib libntop.dylib) /usr/bin/install -c .libs/libntop.lai /mp/var/macports/build/_Users_rschmidt_macports_dports_net_ntop/work/destroot/mp/lib/libntop.la /usr/bin/install -c .libs/libntop.a /mp/var/macports/build/_Users_rschmidt_macports_dports_net_ntop/work/destroot/mp/lib/libntop.a ranlib /mp/var/macports/build/_Users_rschmidt_macports_dports_net_ntop/work/destroot/mp/lib/libntop.a chmod 644 /mp/var/macports/build/_Users_rschmidt_macports_dports_net_ntop/work/destroot/mp/lib/libntop.a libtool: install: warning: remember to run `libtool --finish /mp/lib' /bin/sh ./libtool --mode=install /usr/bin/install -c 'libntopreport.la' '/mp/var/macports/build/_Users_rschmidt_macports_dports_net_ntop/work/destroot/mp/lib/libntopreport.la' libtool: install: warning: relinking `libntopreport.la' (cd /mp/var/macports/build/_Users_rschmidt_macports_dports_net_ntop/work/ntop-3.3.8; /bin/sh ./libtool --mode=relink /usr/bin/gcc-4.0 -g -no-cpp-precomp -O2 -I/mp/include -I/usr/local/include -I/opt/local/include -g -Wshadow -Wpointer-arith -Wmissing-prototypes -Wmissing-declarations -Wnested- externs -fno-common -DPIC -release 3.3.8 -export-dynamic -L/mp/lib -L/usr/local/lib -L/opt/local/lib -o libntopreport.la -rpath /mp/lib emitter.lo globals-report.lo graph.lo fcReport.lo http.lo perl.lo report.lo reportUtils.lo ssl.lo webInterface.lo libntop.la -lpthread -lc -lssl -lcrypto -lrrd_th -lpcre -lgdbm -lz -lpcap -L/mp/lib -L/usr/local/lib -L/mp/lib/perl5/5.8.9/darwin-2level/CORE -lperl -ldl -lm -lc -inst-prefix-dir /mp/var/macports/build/_Users_rschmidt_macports_dports_net_ntop/work/destroot) libtool: link: unable to infer tagged configuration libtool: link: specify a tag with `--tag' libtool: install: error: relink `libntopreport.la' with the above command before installing it gnumake[2]: *** [install-libLTLIBRARIES] Error 1 gnumake[1]: *** [install-am] Error 2 gnumake: *** [install-recursive] Error 1 }}} I do not know why /usr/local/include and /opt/local/include are being referenced above; my MacPorts is in /mp. Full log attached. -- Ticket URL: <http://trac.macports.org/ticket/19367> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #18386: Guide Has No PortGroup Invocation Example
by MacPorts 25 Sep '14

25 Sep '14

#18386: Guide Has No PortGroup Invocation Example ------------------------------------+--------------------------------------- Reporter: rmsfisher@… | Owner: markd@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: guide | Version: 1.7.0 Keywords: PortGroup | Port: ------------------------------------+--------------------------------------- The guide goes to lengths to explain what various PortGroups do but never explains how to write a PortGroup line in a Portfile. -- Ticket URL: <http://trac.macports.org/ticket/18386> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4