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

[MacPorts] #15859: openjade 1.3.2, Revision 2: demo failure
by MacPorts 30 Jul '14

30 Jul '14

#15859: openjade 1.3.2, Revision 2: demo failure -----------------------------+---------------------------------------------- Reporter: tom.duck(a)dal.ca | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: openjade | -----------------------------+---------------------------------------------- Openjade has a demo program that can be used to test the installation. See http://olympus.het.brown.edu/cgi- bin/dwww?type=file&location=/usr/share/doc/openjade#using. Execution of the demo results in a bus error: {{{ $ openjade demo.sgm Bus error }}} This is on my 10.4 Tiger system with the updated openjade port. -- Ticket URL: <http://trac.macports.org/ticket/15859> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 7

[MacPorts] #16113: OpenSceneGraph should use MacPorts curl, not Mac OS X's
by MacPorts 28 Jul '14

28 Jul '14

#16113: OpenSceneGraph should use MacPorts curl, not Mac OS X's -------------------------------------+-------------------------------------- Reporter: ryandesign(a)macports.org | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: | -------------------------------------+-------------------------------------- Parts of OpenSceneGraph link with /usr/lib/libcurl.3.dylib. This should be changed so that it depends on libcurl as provided by MacPorts, and a dependency on port:curl should be added. -- Ticket URL: <http://trac.macports.org/ticket/16113> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #18044: py-postgresql-pqueue: update to 1.0.1
by MacPorts 21 Jul '14

21 Jul '14

#18044: py-postgresql-pqueue: update to 1.0.1 -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: | Port: py-postgresql-pqueue -------------------------------------+-------------------------------------- py-postgresql-pqueue is at version 0.1 but version 1.0.1 appears to be out so the port should probably be updated. -- Ticket URL: <http://trac.macports.org/ticket/18044> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #16336: Allow multiple ports to satisfy a single dependency
by MacPorts 25 Jun '14

25 Jun '14

#16336: Allow multiple ports to satisfy a single dependency ---------------------------------+------------------------------------------ Reporter: rhwood(a)macports.org | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Keywords: | ---------------------------------+------------------------------------------ Currently there is no mechanism to specify that multiple ports may satisfy a single dependency requirement. It would be nice to be able to do so. I can think of two ways this can be done: OR dependencies:: Allow dependencies to be specified in the following fashion:[[BR]]{{{port:able|baker|charlie}}}[[BR]]where the pipe is used to separate one or more ports that may satisfy a single dependency. The first port would be used if none of the ports are installed. There should be no limit to the number of pipes, nor should there be any requirement that any pipes be used (ie, no pipes = no alternate dependencies). This should also wotk with ''bin:'' and ''path:'' type dependencies. "provides" capability in ports:: Use a "provides" key to specify that a port satisfies a particular requirement. Use the name of the port if a provides keyword is not specified. For example, if port '''able-devel''' specifies that it {{{ provides able }}} then port '''able-devel''' would be able satisfy the dependency {{{ port:able }}} in another port, without that other port having to be aware of port '''able-devel''' -- Ticket URL: <http://trac.macports.org/ticket/16336> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 12

[MacPorts] #17366: mkvtoolnix - 2.4.0 - +wxwidgets variant produces unusable binary
by MacPorts 24 Jun '14

24 Jun '14

#17366: mkvtoolnix - 2.4.0 - +wxwidgets variant produces unusable binary ------------------------------+--------------------------------------------- Reporter: krunk7@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: | Port: mkvtoolnix ------------------------------+--------------------------------------------- The +wxwidgets variant produces a binary which does not properly bind to the osx Gui framework. The end result is a correctly rendered gui that does not respond to user mouse or keyboard input nor is capable of changing focus. The fix is to place the binary in an app bundle as described in the WxWidgets Mac OSX Issues wiki: http://wiki.wxwidgets.org/WxMac_Issues -- Ticket URL: <http://trac.macports.org/ticket/17366> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #18211: xprobe2-0.3: runtime error - ping modules cause errors
by MacPorts 13 Jun '14

13 Jun '14

#18211: xprobe2-0.3: runtime error - ping modules cause errors -------------------------------------------+-------------------------------- Reporter: simon@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: xprobe2 ping invalid argument | Port: xprobe2 -------------------------------------------+-------------------------------- The first three modules are broken in xprobe2-0.3 as they generate the following error when being executed: {{{ TX_IP::sendpack::sendto: Invalid argument }}} Unfortunately the program is useless with all "ping:" modules disabled as every machine seems to be down for it. Since there is a darwin 8 platform section I guess that this might be platform dependent and it might be worth checking this on different releases. This one is failing on 10.5.6 on an Intel iMac. -- Ticket URL: <http://trac.macports.org/ticket/18211> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #16598: ettercap do not work on Mac OS X 10.5.5
by MacPorts 12 Jun '14

12 Jun '14

#16598: ettercap do not work on Mac OS X 10.5.5 -------------------------------+-------------------------------------------- Reporter: monserg(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: ettercap mac ox x | Port: ettercap-ng -------------------------------+-------------------------------------------- ettercap do not work on Mac OS X 10.5.5. card: AirportExtreme ( (0x14E4, 0x88) (Broadcom 4328 (4.170.46.11) ) ) installation fine with: sudo port install ettercap-ng but, when executing a test: ettercap -Tzq -i en1 got this error: ettercap NG-0.7.3 copyright 2001-2004 ALoR & NaGA Listening on en1... (Ethernet) ERROR : 6, Device not configured [ec_send.c:send_init:114] libnet_init(LIBNET_RAW4_ADV) failed: libnet_init(): UID or EUID of 0 required -- Ticket URL: <http://trac.macports.org/ticket/16598> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #16110: libxml2: attempts to use libxslt.1.dylib
by MacPorts 06 Jun '14

06 Jun '14

#16110: libxml2: attempts to use libxslt.1.dylib -------------------------------------+-------------------------------------- Reporter: ryandesign(a)macports.org | Owner: cedric.luthi(a)gmail.com Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.7.0 Keywords: | -------------------------------------+-------------------------------------- I previously had libxml2 2.6.32_1 and libxslt 1.1.23_0 installed. I forcibly uninstalled libxml2 and reinstalled it, to test an issue. During the reinstall, this message appeared in the debug output, and also a Mac OS X Crash Reporter dialog appeared with similar information: {{{ dyld: lazy symbol binding failed: Symbol not found: _xmlXPathContextSetCache Referenced from: /mp/lib/libxslt.1.dylib Expected in: flat namespace dyld: Symbol not found: _xmlXPathContextSetCache Referenced from: /mp/lib/libxslt.1.dylib Expected in: flat namespace }}} `/mp` is my MacPorts prefix. So it seems that libxml2 is trying to load libxslt.1.dylib during the build. You must modify the port so that this does not happen, because libxml2 does not declare a dependency on libxslt (and it cannot, since libxslt declares a dependency on libxml2, and we cannot have circular dependencies). I am running Mac OS X 10.4.11 on an Intel Mac with Xcode 2.5 and MacPorts from trunk @38557. -- Ticket URL: <http://trac.macports.org/ticket/16110> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #16535: Add vertical split to screen as a variant
by MacPorts 01 May '14

01 May '14

#16535: Add vertical split to screen as a variant --------------------------------+------------------------------------------- Reporter: akira(a)macports.org | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Enhancements Component: ports | Version: 1.6.0 Keywords: | Port: screen --------------------------------+------------------------------------------- Please provide "Vertical Split for GNU Screen" as a new variant of screen port. http://fungi.yuggoth.org/vsp4s/ -- Ticket URL: <http://trac.macports.org/ticket/16535> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #17998: Linking to Python 2.5 framework is broken due to broken symlinks
by MacPorts 25 Apr '14

25 Apr '14

#17998: Linking to Python 2.5 framework is broken due to broken symlinks --------------------------------------------+------------------------------- Reporter: evert.rol@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: python boost framework symlink | Port: python25 --------------------------------------------+------------------------------- Linking to /opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/config/libpython2.5.a fails, because the file is a broken symlink (as an aside, the file identifies as a dynamically linked shared library, not a static one; is that a naming problem?). This is a result of libpython2.5.a being a symlink to ../../../Python, thereby crossing a symlinked directory: /opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5 points to /opt/local/lib/python2.5. Traversing this symlinked directory manually is no problem, but the symlinked file is broken. Comparing to the system installed variant, the symlinked directory is the other way around: {{{ ls -l /usr/lib/ lrwxr-xr-x 1 root wheel 75 9 Nov 2007 python2.5 -> ../../System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5 }}} Manually fixing this now results in proper linking with libpython2.5 (I also added a libpython2.5.dylib in the config/ directory, which is simply a copy of libpython2.5.a). The directory structure now reads {{{ ls -l /opt/local/lib lrwxr-xr-x 1 root admin 66 14 Jan 18:03 python2.5 -> ../Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/ ls -l /opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/config total 208 lrwxr-xr-x 1 root admin 15 14 Jan 18:02 libpython2.5.a -> ../../../Python lrwxr-xr-x 1 root admin 15 14 Jan 18:02 libpython2.5.dylib -> ../../../Python }}} This ticket originated from ticket [/ticket/17975 #17975] -- Ticket URL: <http://trac.macports.org/ticket/17998> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 9