January 2009 - macports-tickets - lists.macosforge.org

Re: [MacPorts] #15207: gtk28 build failure on osx 10.5.2 - gtkiconfactory.c:2943: error: conflicting types for 'g_hash_table_get_keys'
by MacPorts 20 Jan '09

20 Jan '09

#15207: gtk28 build failure on osx 10.5.2 - gtkiconfactory.c:2943: error: conflicting types for 'g_hash_table_get_keys' -----------------------------+---------------------------------------------- Reporter: pieter@… | Owner: jeremyhu@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: gtk28 | Port: -----------------------------+---------------------------------------------- Comment(by pieter@…): I've no need for the gkt28 port -- Ticket URL: <http://trac.macports.org/ticket/15207#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 0

Re: [MacPorts] #15207: gtk28 build failure on osx 10.5.2 - gtkiconfactory.c:2943: error: conflicting types for 'g_hash_table_get_keys'
by MacPorts 20 Jan '09

20 Jan '09

#15207: gtk28 build failure on osx 10.5.2 - gtkiconfactory.c:2943: error: conflicting types for 'g_hash_table_get_keys' -----------------------------+---------------------------------------------- Reporter: pieter@… | Owner: jeremyhu@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: gtk28 | Port: -----------------------------+---------------------------------------------- Changes (by jeremyhu@…): * owner: macports-tickets@… => jeremyhu@… Comment: If you don't respond about your need for this port, I think we're just gonna nuke the port. -- Ticket URL: <http://trac.macports.org/ticket/15207#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 0

[MacPorts] #18077: tesseract: upgrade to 2.03
by MacPorts 20 Jan '09

20 Jan '09

#18077: tesseract: upgrade to 2.03 -----------------------------------+---------------------------------------- Reporter: steven@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: | Port: tesseract -----------------------------------+---------------------------------------- Hi, tesseract 2.03 is out since April 2008, but in macports only 2.01 is available? Is it possible to update this? Thanks, Steven -- Ticket URL: <http://trac.macports.org/ticket/18077> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #18109: py25-configobj build error
by MacPorts 20 Jan '09

20 Jan '09

#18109: py25-configobj build error ---------------------------------------+------------------------------------ Reporter: carson@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: | Port: py25-configobj ---------------------------------------+------------------------------------ In trying to build py25-configobg (which is a dependency of py25-matplotlib) the following error is encountered: {{{ $ sudo port build py25-configobj ---> Fetching py25-configobj ---> Verifying checksum(s) for py25-configobj ---> Extracting py25-configobj ---> Configuring py25-configobj ---> Building py25-configobj Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_python_py25-configobj/work/configobj-4.5.2" && /opt/local/bin/python2.5 setup.py --no-user-cfg build " returned error 1 Command output: usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: option --no-user-cfg not recognized Error: Status 1 encountered during processing. }}} -- Ticket URL: <http://trac.macports.org/ticket/18109> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

Re: [MacPorts] #13627: vtk5: fails to build ("ld: cycle in dylib re-exports with /usr/X11R6/lib/libGL.dylib")
by MacPorts 20 Jan '09

20 Jan '09

#13627: vtk5: fails to build ("ld: cycle in dylib re-exports with /usr/X11R6/lib/libGL.dylib") -----------------------------------+---------------------------------------- Reporter: chris@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: invalid | Keywords: Port: vtk5 | -----------------------------------+---------------------------------------- Changes (by mcalhoun@…): * status: new => closed * resolution: => invalid Comment: Adding an XCode version check does not seem to be in wide use (especially on unmaintained ports).[[BR]] Since the solution is to upgrade XCode, mark as invalid. -- Ticket URL: <http://trac.macports.org/ticket/13627#comment:8> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 0

Re: [MacPorts] #13493: xorg-renderproto and render conflict
by MacPorts 20 Jan '09

20 Jan '09

#13493: xorg-renderproto and render conflict ---------------------------------------+------------------------------------ Reporter: mww@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.5.2 Resolution: fixed | Keywords: render xorg-renderproto xorg Port: xorg-renderproto, render | ---------------------------------------+------------------------------------ Changes (by mcalhoun@…): * status: reopened => closed * resolution: => fixed Comment: render was removed in r44924. -- Ticket URL: <http://trac.macports.org/ticket/13493#comment:27> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 0

[MacPorts] #18012: py25-cairo-1.8.0 update to 1.8.2
by MacPorts 20 Jan '09

20 Jan '09

#18012: py25-cairo-1.8.0 update to 1.8.2 --------------------------------+------------------------------------------- Reporter: stromnov@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Port Updates Component: ports | Version: 1.7.0 Keywords: | Port: py25-cairo --------------------------------+------------------------------------------- -- Ticket URL: <http://trac.macports.org/ticket/18012> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

Re: [MacPorts] #421: Feature request: bug and user_notes keywords
by MacPorts 20 Jan '09

20 Jan '09

#421: Feature request: bug and user_notes keywords --------------------------------------+------------------------------------- Reporter: gwright@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: MacPorts 1.8.0 Component: base | Version: Resolution: | Keywords: Port: | --------------------------------------+------------------------------------- Comment(by perry@…): Replying to [comment:10 raimue@…]: > But I don't understand what `bugs` should contain. Port bugs should be filed in Trac with a correct 'Port' field. Other stuff can be added as comments. If you want to improve/update the Portfile you have to look at it anyway. That makes sense to me -- should the bugs portion of this ticket be removed then? For now, I've implemented the following (r45686): * I added a new field (notes) to PortInfo in portutil.tcl. * I added a new action (action_notes) in port.tcl that displays notes set in the Portfile ('''not''' PortIndex, though an option that reads notes from the index can be added -- much like in action_info). * At the end of activate_main in portactivate.tcl, notes are displayed. Note that action_activate does '''not''' call this procedure (it uses portimage::activate instead). This means that notes are only displayed when `port install` or `port upgrade` is called -- '''not''' during `port activate`. To test the implementation, I created an example Portfile (foo) that contains the following lines in particular: {{{ notes This message is stored in notes. It is displayed at\ \nthe end of the activation phase and when action_notes\ \nis invoked. }}} When `port install foo` or `port upgrade foo` is called: {{{ ---> Installing foo @0.2.1_0+darwin_9 ---> Activating foo @0.2.1_0+darwin_9 This message is stored in notes. It is displayed at the end of the activation phase and when action_notes is invoked. ---> Cleaning foo }}} When `port notes elinks foo git-core` is called: {{{ elinks has no notes. foo has the following notes: This message is stored in notes. It is displayed at the end of the activation phase and when action_notes is invoked. git-core has no notes. }}} -- Ticket URL: <http://trac.macports.org/ticket/421#comment:11> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 0

[MacPorts] #16968: tiff-3.8.2 build fails under Tiger (PPC)
by MacPorts 20 Jan '09

20 Jan '09

#16968: tiff-3.8.2 build fails under Tiger (PPC) ----------------------------------+----------------------------------------- Reporter: macports(a)dotgray.com | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: | Port: ----------------------------------+----------------------------------------- tiff-3.8.2 fails to compile under 10.4.11 on a PPC machine. Previous tickets seemed to deal with X11 compatibilities under Leopard or other library problems; this seems to hang up in tif_stream.cxx. Make output: {{{ Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_tiff/work/tiff-3.8.2" && make all " returned error 2 Command output: tif_stream.cxx:196: error: 'class tiffis_data' has no member named 'myIS' tif_stream.cxx:196: error: 'ios' has not been declared tif_stream.cxx:196: error: 'end' was not declared in this scope tif_stream.cxx:197: error: 'class tiffis_data' has no member named 'myIS' tif_stream.cxx:198: error: 'class tiffis_data' has no member named 'myIS' tif_stream.cxx: In function 'TIFF* _tiffStreamOpen(const char*, const char*, void*)': tif_stream.cxx:240: error: 'class tiffos_data' has no member named 'myOS' tif_stream.cxx:240: error: 'ostream' was not declared in this scope tif_stream.cxx:240: error: expected primary-expression before ')' token tif_stream.cxx:240: error: expected `;' before 'fd' tif_stream.cxx:241: error: 'class tiffos_data' has no member named 'myOS' tif_stream.cxx:252: error: 'class tiffis_data' has no member named 'myIS' tif_stream.cxx:252: error: 'istream' was not declared in this scope tif_stream.cxx:252: error: expected primary-expression before ')' token tif_stream.cxx:252: error: expected `;' before 'fd' tif_stream.cxx:253: error: 'class tiffis_data' has no member named 'myIS' tif_stream.cxx: At global scope: tif_stream.cxx:267: error: 'ostream' has not been declared tif_stream.cxx: In function 'TIFF* TIFFStreamOpen(const char*, int*)': tif_stream.cxx:273: error: request for member 'fail' in '* os', which is of non-class type 'int' tif_stream.cxx:273: error: request for member 'tellp' in '* os', which is of non-class type 'int' tif_stream.cxx:275: error: request for member 'seekp' in '* os', which is of non-class type 'int' tif_stream.cxx: At global scope: tif_stream.cxx:283: error: 'istream' has not been declared tif_stream.cxx: In function 'TIFF* TIFFStreamOpen(const char*, int*)': tif_stream.cxx:283: error: redefinition of 'TIFF* TIFFStreamOpen(const char*, int*)' tif_stream.cxx:267: error: 'TIFF* TIFFStreamOpen(const char*, int*)' previously defined here make[2]: *** [tif_stream.lo] Error 1 make[1]: *** [all] Error 2 make: *** [all-recursive] Error 1 }}} -- Ticket URL: <http://trac.macports.org/ticket/16968> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6

[MacPorts] #17987: msmtp: enable OS X keychain support
by MacPorts 20 Jan '09

20 Jan '09

#17987: msmtp: enable OS X keychain support ----------------------------------+----------------------------------------- Reporter: jaysoffian@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.7.0 Keywords: keychain | Port: msmtp ----------------------------------+----------------------------------------- I provided a patch to msmtp to support the OS X authentication. This was included in upstream msmtp version 1.4.14. However, it looks like the support never got enabled in the msmtp Portfile. The attached trivial patch does so (I see no reason to make this a variant, but I'll ultimately leave that up to the msmtp Portfile maintainer. See related http://trac.macports.org/ticket/14189. -- Ticket URL: <http://trac.macports.org/ticket/17987> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2