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

[MacPorts] #20946: add license display to ports.php
by MacPorts 01 Oct '14

01 Oct '14

#20946: add license display to ports.php ------------------------------+--------------------------------------------- Reporter: snc@… | Owner: jmpp@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: website | Version: Keywords: | Port: ------------------------------+--------------------------------------------- Would it be beneficial to provide the license information in the information displayed about our available ports? -- Ticket URL: <http://trac.macports.org/ticket/20946> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #19300: ports.php: web site should have page about each port, not link to portfile
by MacPorts 01 Oct '14

01 Oct '14

#19300: ports.php: web site should have page about each port, not link to portfile -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: jmpp@… Type: defect | Status: new Priority: Normal | Milestone: Website & Documentation Component: website | Version: Keywords: | Port: -------------------------------------+-------------------------------------- Currently ports.php lets you search for a port, but once you click on one for more info, it just takes you to the portfile in the repository. Users should never need to see the portfile text. Instead, we should show a nicely-formatted page which would include the information you can see in such commands as "`port info`" and "`port variants`" This issue was sent to me via email by Mojca Miklavec. -- Ticket URL: <http://trac.macports.org/ticket/19300> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 9

[MacPorts] #19298: ports.php: category pages hard to navigate; consider by-letter navigation
by MacPorts 01 Oct '14

01 Oct '14

#19298: ports.php: category pages hard to navigate; consider by-letter navigation -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: jmpp@… Type: defect | Status: new Priority: Normal | Milestone: Website & Documentation Component: website | Version: Keywords: | Port: -------------------------------------+-------------------------------------- If you're on a category page, the only available navigation links let you go to pages by number. This is not useful if you want to, say, browse a category for all ports whose names start with a particular letter. This deficiency was pointed out to me via email by Mojca Miklavec. -- Ticket URL: <http://trac.macports.org/ticket/19298> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #31394: Error install subversion on OSX 10.5.8 iMac
by MacPorts 01 Oct '14

01 Oct '14

#31394: Error install subversion on OSX 10.5.8 iMac ----------------------------------+----------------------------------------- Reporter: norman.shi@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: MacPorts 2.0.4 Component: ports | Version: 2.0.3 Keywords: | Port: ----------------------------------+----------------------------------------- info:build /usr/bin/gcc-4.0 -arch i386 -arch i386 -dynamiclib -undefined error -o .libs/libdigestmd5.2.0.23.so digestmd5.lo digestmd5_init.lo plugin_common.lo -L/opt/local/lib -lresolv -lresolv -lpam -lc :info:build Undefined symbols: :info:build "_des_key_sched", referenced from: :info:build _init_3des in digestmd5.lo :info:build _init_3des in digestmd5.lo :info:build _init_3des in digestmd5.lo :info:build _init_3des in digestmd5.lo :info:build _init_des in digestmd5.lo :info:build _init_des in digestmd5.lo :info:build "_des_ede2_cbc_encrypt", referenced from: :info:build _dec_3des in digestmd5.lo :info:build _enc_3des in digestmd5.lo :info:build "_des_cbc_encrypt", referenced from: :info:build _dec_des in digestmd5.lo :info:build _enc_des in digestmd5.lo :info:build ld: symbol(s) not found :info:build collect2: ld returned 1 exit status :info:build make[2]: *** [libdigestmd5.la] Error 1 :info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local _var_macports_sources_rsync.macports.org_release_ports_security_cyrus- sasl2/cyru s-sasl2/work/cyrus-sasl-2.1.23/plugins' :info:build make[1]: *** [all-recursive] Error 1 :info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local _var_macports_sources_rsync.macports.org_release_ports_security_cyrus- sasl2/cyru : -- Ticket URL: <https://trac.macports.org/ticket/31394> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #28060: Error: Failed to install cyrus-sasl2
by MacPorts 01 Oct '14

01 Oct '14

#28060: Error: Failed to install cyrus-sasl2 -----------------------------+---------------------------------------------- Reporter: E3pO@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: subversion -----------------------------+---------------------------------------------- Last login: Thu Jan 20 06:56:32 on console E3pOs-Mac-mini:~ E3pO$ sudo port install subversion Password: ---> Computing dependencies for subversion ---> Dependencies to be installed: cyrus-sasl2 gettext neon serf ---> Building cyrus-sasl2 Error: Target org.macports.build returned: shell command failed (see log for details) Error: Failed to install cyrus-sasl2 Log for cyrus-sasl2 is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_ports_security_cyrus-sasl2/main.log Error: The following dependencies were not installed: cyrus-sasl2 gettext neon serf Error: Status 1 encountered during processing. To report a bug, see <http://guide.macports.org/#project.tickets> E3pOs-Mac-mini:~ E3pO$ tail /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_ports_security_cyrus-sasl2/main.log :error:build Target org.macports.build returned: shell command failed (see log for details) :debug:build Backtrace: shell command failed (see log for details) while executing "command_exec build" (procedure "portbuild::build_main" line 8) invoked from within "$procedure $targetname" :info:build Warning: the following items did not execute (for cyrus- sasl2): org.macports.activate org.macports.build org.macports.destroot org.macports.install :error:build Failed to install cyrus-sasl2 :notice:build Log for cyrus-sasl2 is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports .org_release_ports_security_cyrus-sasl2/main.log E3pOs-Mac-mini:~ E3pO$ -- Ticket URL: <https://trac.macports.org/ticket/28060> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #30616: xymon: use the right compiler and architectures
by MacPorts 29 Sep '14

29 Sep '14

#30616: xymon: use the right compiler and architectures -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: fclaire@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: xymon, xymon-server -------------------------------------+-------------------------------------- xymon doesn't ensure it's UsingTheRightCompiler; it ignores changes the user makes to build_arch in macports.conf; and if you install it with the +universal variant, the resulting software is not actually universal. -- Ticket URL: <https://trac.macports.org/ticket/30616> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[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] #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