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

[MacPorts] #16004: IDLE (installed with python25) fails to launch without py25-tkinter
by MacPorts 23 Dec '09

23 Dec '09

#16004: IDLE (installed with python25) fails to launch without py25-tkinter -------------------------------------+-------------------------------------- Reporter: jon.hermansen(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.7.0 Keywords: | -------------------------------------+-------------------------------------- = Python 2.5 is installed, and some other stuff = {{{ Emmett:~ Amy$ port installed | egrep -i "py[thon]*25" py25-mutagen @1.13_0 (active) py25-pyqt4 @4.4.2_0 (active) py25-sip @4.7.6_0 (active) py25-zlib @2.5.2_0 (active) python25 @2.5.2_4+darwin_9 (active) Emmett:~ Amy$ /opt/local/bin/python2.5 -V Python 2.5.2 Emmett:~ Amy$ file /Applications/MacPorts/MacPython\ 2.5/IDLE.app/Contents/MacOS/IDLE /Applications/MacPorts/MacPython 2.5/IDLE.app/Contents/MacOS/IDLE: a /opt/local/Library/Frameworks/Python.framework/Versions/2.5/Resources/Python.app/Contents/MacOS/Python script text executable }}} = IDLE.app (comes with MacPorts package 'python25') does not run at all without 'py25-tkinter' being installed (see below). = {{{ Emmett:~ Amy$ /Applications/MacPorts/MacPython\ 2.5/IDLE.app/Contents/MacOS/IDLE Traceback (most recent call last): File "/Applications/MacPorts/MacPython 2.5/IDLE.app/Contents/Resources/idlemain.py", line 6, in <module> from idlelib.PyShell import main File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/idlelib/PyShell.py", line 14, in <module> import macosxSupport File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/idlelib/macosxSupport.py", line 6, in <module> import Tkinter File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5 /lib-tk/Tkinter.py", line 38, in <module> import _tkinter # If this fails your Python may not be configured for Tk ImportError: No module named _tkinter = Running current install of python2.5 to interactively check for Tkinter = Emmett:~ Amy$ /opt/local/bin/python2.5 -i Python 2.5.2 (r252:60911, Jul 10 2008, 10:49:04) [GCC 4.0.1 (Apple Inc. build 5465)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import _tkinter Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: No module named _tkinter >>> import Tkinter Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/opt/local/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5 /lib-tk/Tkinter.py", line 38, in <module> import _tkinter # If this fails your Python may not be configured for Tk ImportError: No module named _tkinter >>> quit() }}} = So, I install the package... = {{{ Emmett:~ Amy$ sudo port install py25-tkinter ---> Unpacking tgz archive for py25-tkinter 2.5.2_0 ---> Installing py25-tkinter @2.5.2_0 ---> Activating py25-tkinter @2.5.2_0 ---> Cleaning py25-tkinter }}} = I see that it is installed... = {{{ Emmett:~ Amy$ port installed | egrep -i "py[thon]*25" py25-mutagen @1.13_0 (active) py25-pyqt4 @4.4.2_0 (active) py25-sip @4.7.6_0 (active) py25-tkinter @2.5.2_0 (active) py25-zlib @2.5.2_0 (active) python25 @2.5.2_4+darwin_9 (active) }}} = And the application works now, automatically launching X11.app as well = {{{ Emmett:~ Amy$ /Applications/MacPorts/MacPython\ 2.5/IDLE.app/Contents/MacOS/IDLE }}} = It works! = I was able to reproduce this bug by uninstalling the py25-tkinter package (after I'd noticed the bug.) -- Ticket URL: <http://trac.macports.org/ticket/16004> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #16353: Update autopsy to 2.10
by MacPorts 21 Dec '09

21 Dec '09

#16353: Update autopsy to 2.10 --------------------------------+------------------------------------------- Reporter: dersh(a)alum.mit.edu | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Updates Component: ports | Version: 1.6.0 Keywords: | --------------------------------+------------------------------------------- I just downloaded and installed autopsy 2.10 from sleuthkit.org. It built, on my Macbook Pro, OS 10.5.4, "out of the box" with no changes and no problems at all. So I would think that it is probably very easy to update this port to the current version. Thanks, -- Ticket URL: <http://trac.macports.org/ticket/16353> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 7

[MacPorts] #17076: Being in an soon-to-be-deactivated directory causes port to error
by MacPorts 20 Dec '09

20 Dec '09

#17076: Being in an soon-to-be-deactivated directory causes port to error ------------------------------+--------------------------------------------- Reporter: blb(a)macports.org | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Low | Milestone: MacPorts base bugs Component: base | Version: 1.7.0 Keywords: cwd | Port: ------------------------------+--------------------------------------------- This is an extremely esoteric bug, but for tracking purposes (while sitting in /opt/local/lib/erlang, which is exclusively from the erlang port): {{{ $ sudo port deactivate erlang Password: ---> Deactivating erlang cd couldn't change working directory to "/opt/local/lib/erlang": no such file or directory while executing "cd $savedir" (procedure "foreachport" line 17) invoked from within "foreachport $portlist { if { [catch {portimage::deactivate $portname [composite_version $portversion [array get variations]] [array get option..." (procedure "action_deactivate" line 6) invoked from within "$action_proc $action $portlist [array get global_options]" (procedure "process_cmd" line 86) invoked from within "process_cmd $remaining_args" invoked from within "if { [llength $remaining_args] > 0 } { # If there are remaining arguments, process those as a command # Exit immediately, by default, unless..." (file "/opt/local/bin/port" line 3225) }}} -- Ticket URL: <http://trac.macports.org/ticket/17076> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #16806: unarchive.args for xar in portunarchive.tcl is wrong
by MacPorts 20 Dec '09

20 Dec '09

#16806: unarchive.args for xar in portunarchive.tcl is wrong -----------------------------------+---------------------------------------- Reporter: blb(a)macports.org | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Low | Milestone: MacPorts base bugs Component: base | Version: 1.7.0 Keywords: archive unarchive xar | Port: -----------------------------------+---------------------------------------- Attaching a really simple patch to fix unarchive.args for xar in base/src/package1.0/portunarchive.tcl (xar interprets the dot as a file to extract so this fails). -- Ticket URL: <http://trac.macports.org/ticket/16806> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #16311: category office is not in portlint.tcl
by MacPorts 20 Dec '09

20 Dec '09

#16311: category office is not in portlint.tcl ----------------------------------+----------------------------------------- Reporter: rene(a)macports.org | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Low | Milestone: MacPorts base bugs Component: base | Version: 1.6.0 Keywords: lint category office | ----------------------------------+----------------------------------------- A category office has been created in #36308 but has not yet been added to portlint.tcl.[[BR]] Therefore lint complains every time a port in office is updated. -- Ticket URL: <http://trac.macports.org/ticket/16311> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #18214: muniversal portgroup uses host core2-apple-darwin
by MacPorts 20 Dec '09

20 Dec '09

#18214: muniversal portgroup uses host core2-apple-darwin -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: mcalhoun@… Type: defect | Status: new Priority: Normal | Milestone: MacPorts Future Component: base | Version: 1.7.0 Keywords: | Port: -------------------------------------+-------------------------------------- When building universal on a PowerPC Mac, the muniversal portgroup uses the host core2-apple-darwin to build the Intel parts, but at least on my Power Mac G4 with Mac OS X 10.4.11 and Xcode 2.5, it doesn't know any such host. Here is the output I get from cairo @1.8.6_3: {{{ universal: Running configure for architecture ppc universal: Running configure for architecture i386 Error: Target org.macports.configure returned: configure failure: shell command " cd "/mp/var/macports/build/_Volumes_data_macports_ports_graphics_cairo/work/i386" && ./configure --prefix=/mp --disable-glitz --disable-xcb --enable-ft --enable-pdf --enable-png --enable-ps --enable-svg --enable-xlib --enable- xlib-xrender --with-x --disable-dependency-tracking --enable-quartz --enable-quartz-font --enable-quartz-image --host=core2-apple-darwin " returned error 1 Command output: configure: WARNING: If you wanted to set the --build type, don't use --host. If a cross compiler is detected then cross compile mode will be used. checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... build/install-sh -c -d checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for core2-apple-darwin-strip... no checking for strip... strip checking build system type... powerpc-apple-darwin8.11.0 checking host system type... Invalid configuration `core2-apple-darwin': machine `core2-apple' not recognized configure: error: /bin/sh build/config.sub core2-apple-darwin failed Error: Status 1 encountered during processing. }}} I get [comment:ticket:18190:1 the same output] from libiconv @1.12_2 if I use the original patch that was in #18190. I had never heard of "core2-apple-darwin" before seeing it in the muniversal portgroup code, and [http://www.google.com/search?q=%22core2 -apple-darwin%22 searching Google], there are no hits for "core2-apple- darwin" except as part of the muniversal portgroup. Shouldn't it be "i686 -apple-darwin" for which [http://www.google.com/search?q=%22i686-apple- darwin%22 Google has] thousands of results? If I change core2-apple-darwin to i686-apple-darwin in the muniversal portgroup, then I can build libiconv universal (2-way 32-bit) without needing to set merger_host in the libiconv portfile. Maybe that doesn't properly take 64-bit into account. So the portgroup should set host to i686-apple-darwin or x86_64 -apple-darwin accordingly. All I know is "`locate i686-apple-darwin`" and "`locate x86_64-apple-darwin`" return plenty of results on my Power Mac whereas "`locate core2-apple-darwin`" returns none. -- Ticket URL: <http://trac.macports.org/ticket/18214> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #17979: startupitems using launchd and needing a wrapper fail to create the wrapper
by MacPorts 20 Dec '09

20 Dec '09

#17979: startupitems using launchd and needing a wrapper fail to create the wrapper ---------------------------------+------------------------------------------ Reporter: blb@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: MacPorts Future Component: base | Version: 1.7.0 Keywords: startupitem launchd | Port: ---------------------------------+------------------------------------------ When a start, stop, restart, or init (but not both start and stop) option is given to startupitem and the system supports launchd, it wants to use a wrapper script ([browser:trunk/base/src/port1.0/portstartupitem.tcl#L416 beginning of section]) and a startup script. The code creates a launchd wrapper which references this startup script ([browser:trunk/base/src/port1.0/portstartupitem.tcl#L424 block which references the startup script]). However, nowhere in {{{proc startupitem_create_darwin_launchd}}} does it actually create this script, {{{${scriptdir}/${portname}.sh}}}. If a port is expected to create this startup script itself, it needs to be documented since the directory for it, {{{${prefix}/etc/startup}}}, does not appear in any documentation I can find. -- Ticket URL: <http://trac.macports.org/ticket/17979> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #17972: RFE: Add a PortGroup with a different universal build mechanism
by MacPorts 20 Dec '09

20 Dec '09

#17972: RFE: Add a PortGroup with a different universal build mechanism -----------------------------------+---------------------------------------- Reporter: mcalhoun@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: MacPorts Future Component: base | Version: 1.7.0 Keywords: | Port: -----------------------------------+---------------------------------------- To facilitate the building of more 32/64-bit universal binaries,[[BR]] I would like to propose a PortGroup which builds the packages[[BR]] separately and then merges them together. It is intended to be an improvement of the [http://trac.macports.org/browser/trunk/base/src/port1.0/portutil.tcl#L2188 merge] function. -- Ticket URL: <http://trac.macports.org/ticket/17972> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 7

[MacPorts] #17262: A few Perl mirrors have problems
by MacPorts 20 Dec '09

20 Dec '09

#17262: A few Perl mirrors have problems ----------------------------------------------+----------------------------- Reporter: stolen-from-macports-trac(a)l2g.to | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: MacPorts base enhancements Component: base | Version: 1.6.0 Keywords: perl, mirrors | Port: ----------------------------------------------+----------------------------- In the list of mirror sites (mirror_sites.tcl), the Perl section has a few items on the list that need attention. This mirror: ftp://ftp.is.co.za/programming/perl/CPAN/modules/by-module/ ...has reorganized slightly; the URL should now be: ftp://ftp.is.co.za/programming/perl/modules/by-module/ Also, I have had repeated trouble connecting to the FTP servers below in any way (not just the given directories). I would imagine that the best course of action is to keep watching these two, and if they haven't started working again in a week or two, delete them from the list. ftp://ftp.bora.net/pub/CPAN/modules/by-module/ ftp://ftp.mirror.ac.uk/sites/ftp.funet.fi/pub/languages/perl/CPAN/modules /by-module/ -- Ticket URL: <http://trac.macports.org/ticket/17262> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #17098: reinplace fails if filename has spaces
by MacPorts 20 Dec '09

20 Dec '09

#17098: reinplace fails if filename has spaces -------------------------------------+-------------------------------------- Reporter: ryandesign(a)macports.org | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.7.0 Keywords: | Port: -------------------------------------+-------------------------------------- If a filename has spaces in it, trying to use reinplace fails. e.g.: {{{ PortSystem 1.0 name reinplace-spaces version 1.0 fetch {} checksum {} extract.mkdir yes extract { xinstall "${filespath}/filename with spaces.txt" ${worksrcpath} } configure { reinplace s/foo/bar/ "${worksrcpath}/filename with spaces.txt" } }}} {{{ $ port configure ---> Fetching reinplace-spaces ---> Verifying checksum(s) for reinplace-spaces ---> Extracting reinplace-spaces ---> Configuring reinplace-spaces Error: reinplace: cp: /tmp/filename: No such file or directory Error: Target org.macports.configure returned: reinplace copy failed Error: Status 1 encountered during processing. $ }}} This was [http://lists.macosforge.org/pipermail/macports- users/2008-November/012229.html reported on macports-users] by Scott Haneda. -- Ticket URL: <http://trac.macports.org/ticket/17098> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4