September 2008 - macports-tickets - lists.macosforge.org

[MacPorts] #15426: BUG: py25-* fail with parallel building enabled
by MacPorts 19 Dec '09

19 Dec '09

#15426: BUG: py25-* fail with parallel building enabled ---------------------------------+------------------------------------------ Reporter: raimue(a)macports.org | Owner: afb(a)macports.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.7.0 Keywords: parallel | ---------------------------------+------------------------------------------ There was a new bug introduced while fixing #15295. {{{ ---> Building py25-bz2 with target build DEBUG: Executing org.macports.build (py25-bz2) DEBUG: port allows a parallel build DEBUG: Environment: "MACOSX_DEPLOYMENT_TARGET"='10.5' DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/_Users_raim_src_macports_trunk_dports_python_py25-bz2/work/Python-2.5.2/Modules" && /opt/local/bin/python2.5 setup.py build' 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 -j not recognized Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_Users_raim_src_macports_trunk_dports_python_py25-bz2/work/Python-2.5.2/Modules" && /opt/local/bin/python2.5 setup.py build -j3" returned error 1 }}} The python port groups just set build.cmd (and do not overwrite build.type), so [build_getmaketype] still assumes this is a standard make. With the previous implementation overwriting build.cmd was enough. -- Ticket URL: <http://trac.macports.org/ticket/15426> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #15405: xcode.project variable handles strings as lists
by MacPorts 19 Dec '09

19 Dec '09

#15405: xcode.project variable handles strings as lists ---------------------------------+------------------------------------------ Reporter: rhwood(a)macports.org | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.6.0 Keywords: | ---------------------------------+------------------------------------------ The xcode.project portfile variable treats strings as lists. The variable takes a single project file as an argument to be passed to xcode, but if a space is in the name, it passes the name wrapped in curly braces. Expected result: setting {{{xcode.project "Chat Core.xcodeproj"}}} does not lead to an error Returned result: {{{ --> Building ChatCore Error: Target org.macports.build returned: shell command "cd "/opt/local/var/macports/build/_Users_Shared_Developer_MacPorts_Repository_trunk_dports_irc_ChatCore/work/trunk" && xcodebuild -project {Chat Core.xcodeproj} -target "ChatCore (Application)" -configuration Release build OBJROOT=build/ SYMROOT=build/ " returned error 1 Command output: xcodebuild: Error: the project name {Chat does not have a valid extension. }}} Note that '''''{'''Chat Core.xcodeproj'''}''''' is passed instead of ''Chat Core.xcodeproj'' This issue is covered in #12429 which I did not reopen due to its commentary. I found at least one portfile (source:trunk/dports/aqua/IcyJuice/Portfile) that has workarounds in it to address this behavior. -- Ticket URL: <http://trac.macports.org/ticket/15405> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #16383: gnustep portgroup should use destroot.violate_mtree yes
by MacPorts 12 Dec '09

12 Dec '09

#16383: gnustep portgroup should use destroot.violate_mtree yes -------------------------------------+-------------------------------------- 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: | -------------------------------------+-------------------------------------- When using the gnustep layout, the gnustep portgroup should indicate that it intends to violate the mtree by using the `destroot.violate_mtree yes` keyword. -- Ticket URL: <http://trac.macports.org/ticket/16383> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #16536: port registry is not including files created by destroot.keepdirs
by MacPorts 09 Dec '09

09 Dec '09

#16536: port registry is not including files created by destroot.keepdirs ------------------------------------------+--------------------------------- Reporter: macsforever2000(a)macports.org | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: ports | Version: 1.7.0 Keywords: | Port: ------------------------------------------+--------------------------------- In the sane-backends port, I created a directory (${prefix}/var/lock) with xinstall -d and added it to destroot.keepdirs. MacPorts created the file .turd_sane-backends so the directory does not get automatically deleted after the destroot phase. But that file does not appear in "port contents sane-backends". Consequently, when the port is uninstalled, the file and the directory remain. -- Ticket URL: <http://trac.macports.org/ticket/16536> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #16140: ImageMagick uninstall does not remove /opt/bin/local/animate
by MacPorts 09 Dec '09

09 Dec '09

#16140: ImageMagick uninstall does not remove /opt/bin/local/animate ---------------------------------+------------------------------------------ Reporter: jburt(a)depersico.com | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: | ---------------------------------+------------------------------------------ After an aborted/failed install, uninstalling and cleaning ImageMagick does not remove the directory /opt/bin/local/animate or the files therein The next install fails because the directory already exists Mac OS Leopard MacPorts 1.60 -- Ticket URL: <http://trac.macports.org/ticket/16140> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #15683: Building failing for no apparent reason even though manual builds work
by MacPorts 09 Dec '09

09 Dec '09

#15683: Building failing for no apparent reason even though manual builds work ---------------------------+------------------------------------------------ Reporter: cems(a)lanl.gov | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Keywords: | ---------------------------+------------------------------------------------ I've been installing scipy and matplot lib on 10.5.3 leopard w/xcode 3.0 into a fresh 1.6.0 port install. A number of the dependent packages fail at "setup.py build" however if you run that command from the command line they build without errors. Here is one example: 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-tkinter/work/Python-2.5.2/Modules" && /opt/local/bin/python2.5 setup.py build " returned error 1 Command output: running build running build_ext building '_tkinter' extension creating build creating build/temp.macosx-10.3-i386-2.5 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -DWITH_APPINIT=1 -I/opt/local/include -I/opt/local/include/ python2.5 -c _tkinter.c -o build/temp.macosx-10.3-i386-2.5/_tkinter.o unable to execute -DNDEBUG: No such file or directory error: command '-DNDEBUG' failed with exit status 1 Error: The following dependencies failed to build: py25-tkinter Error: Status 1 encountered during processing. and yet if I run the same command from the command line I get: bash-3.2$ cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_python_py25-tkinter/work/Python-2.5.2/Modules" bash-3.2$ sudo /opt/local/bin/python2.5 setup.py build Password: running build running build_ext building '_tkinter' extension /usr/bin/gcc-4.0 -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -DWITH_APPINIT=1 -I/opt/local/include -I/opt/local/include/python2.5 -c _tkinter.c -o build/temp.macosx-10.3-i386-2.5/_tkinter.o /usr/bin/gcc-4.0 -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -DWITH_APPINIT=1 -I/opt/local/include -I/opt/local/include/python2.5 -c tkappinit.c -o build/temp.macosx-10.3-i386-2.5/tkappinit.o creating build/lib.macosx-10.3-i386-2.5 /usr/bin/gcc-4.0 -L/opt/local/lib -bundle -undefined dynamic_lookup build/temp.macosx-10.3-i386-2.5/_tkinter.o build/temp.macosx-10.3-i386-2.5/tkappinit.o -L/opt/local/lib -ltcl8.5 -ltk8.5 -o build/lib.macosx-10.3-i386-2.5/_tkinter.so bash-3.2$ If I then re-rerun the installer, the installer proceeds just fine. this happens on some but not all packages. I have downloaded and re-installed macports from scratch as of yeasterday but this did not fix the issue. here is another example: Error: Target org.macports.activate returned: Image error: /Applications/MacPorts/AquaTerm.app/Contents/Info.plist already exists and does not belong to a registered port. Unable to activate port aquaterm. Error: The following dependencies failed to build: gnuplot aquaterm fontconfig freetype gd2 jpeg libpng pdflib py25-zlib Error: Status 1 encountered during processing. -- Ticket URL: <http://trac.macports.org/ticket/15683> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #15534: New port: p5-mail-sender
by MacPorts 09 Dec '09

09 Dec '09

#15534: New port: p5-mail-sender --------------------------------+------------------------------------------- Reporter: hagedorn(a)tcnj.edu | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Submissions Component: ports | Version: 1.6.0 Keywords: mail, sender, perl | --------------------------------+------------------------------------------- Port of Perl Mail::Sender -- Ticket URL: <http://trac.macports.org/ticket/15534> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #15498: Port of Perl Module Mail::Sender
by MacPorts 09 Dec '09

09 Dec '09

#15498: Port of Perl Module Mail::Sender -------------------------------+-------------------------------------------- Reporter: hagedorn(a)tcnj.edu | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: MacPorts base enhancements Component: ports | Version: 1.6.0 Keywords: Mail, sender | -------------------------------+-------------------------------------------- Port of Perl Module Mail::Sender {{{ sudo port install p5-mail-sender ---> Fetching p5-mail-sender ---> Verifying checksum(s) for p5-mail-sender ---> Extracting p5-mail-sender ---> Configuring p5-mail-sender ---> Building p5-mail-sender with target all ---> Staging p5-mail-sender into destroot ---> Installing p5-mail-sender 0.8.13_0 ---> Activating p5-mail-sender 0.8.13_0 ---> Cleaning p5-mail-sender }}} -- Ticket URL: <http://trac.macports.org/ticket/15498> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #15470: distfile mirror should have files for all variants
by MacPorts 09 Dec '09

09 Dec '09

#15470: distfile mirror should have files for all variants ------------------------------+--------------------------------------------- Reporter: jmr(a)macports.org | Owner: wsiegrist(a)apple.com Type: enhancement | Status: new Priority: Normal | Milestone: MacPorts base enhancements Component: server/hosting | Version: Keywords: | ------------------------------+--------------------------------------------- Currently, distfiles.macports.org appears to have only those files that are required to build each port with its default variants. Ideally, the files needed for all platforms and variants would be there. -- Ticket URL: <http://trac.macports.org/ticket/15470> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #15390: Error: Checksum (md5) mismatch for ImageMagick-6.4.1-2.tar.bz2
by MacPorts 09 Dec '09

09 Dec '09

#15390: Error: Checksum (md5) mismatch for ImageMagick-6.4.1-2.tar.bz2 -------------------------------------+-------------------------------------- Reporter: cmillet(a)milletgroup.com | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: ports | Version: 1.6.0 Keywords: ImageMagick | -------------------------------------+-------------------------------------- I read through ticket 15341 and followed the instructions (and waited 24 hours) and even cleaned ImageMagick... however, I still get the following errors. Error: Checksum (md5) mismatch for ImageMagick-6.4.1-2.tar.bz2 Error: Checksum (sha1) mismatch for ImageMagick-6.4.1-2.tar.bz2 Error: Checksum (rmd160) mismatch for ImageMagick-6.4.1-2.tar.bz2 Error: Target org.macports.checksum returned: Unable to verify file checksums Error: Status 1 encountered during processing. -- Ticket URL: <http://trac.macports.org/ticket/15390> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5