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

[MacPorts] #31652: Checksum (rmd160)(sha256) mismatch for lame-3.99.tar.gz
by MacPorts 29 Dec '11

29 Dec '11

#31652: Checksum (rmd160)(sha256) mismatch for lame-3.99.tar.gz -------------------------------+-------------------------------------------- Reporter: seneru@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: -------------------------------+-------------------------------------------- /* I think the checksum still doesn't match even after the fixes. The log after port install lame is as bellow. */ ---> Computing dependencies for lame ---> Verifying checksum(s) for lame Error: Checksum (rmd160) mismatch for lame-3.99.tar.gz Error: Checksum (sha256) mismatch for lame-3.99.tar.gz Error: Target org.macports.checksum returned: Unable to verify file checksums -- Ticket URL: <https://trac.macports.org/ticket/31652> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6

[MacPorts] #31434: Update py27-pyfits to 3.0.2
by MacPorts 29 Dec '11

29 Dec '11

#31434: Update py27-pyfits to 3.0.2 ---------------------------------------+------------------------------------ Reporter: marshall.perrin@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: py27-pyfits ---------------------------------------+------------------------------------ The attached portfile updated pyfits to the latest version, 3.0.2. Despite this being a bump of the major version number, I found that it installed flawlessly with only trivial updates to the Portfile. The other py*-pyfits portfile variants should be updated. In addition, pyfits 3 now compiles under Python 3, so new variants py31-pyfits etc could now be created. -- Ticket URL: <https://trac.macports.org/ticket/31434> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 8

[MacPorts] #23704: ng-spice update to release 20
by MacPorts 29 Dec '11

29 Dec '11

#23704: ng-spice update to release 20 ------------------------------+--------------------------------------------- Reporter: soren@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.2 Keywords: | Port: ng-spice ------------------------------+--------------------------------------------- -- Ticket URL: <http://trac.macports.org/ticket/23704> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6

[MacPorts] #32516: Remove macfuse port
by MacPorts 29 Dec '11

29 Dec '11

#32516: Remove macfuse port --------------------------------------+------------------------------------- Reporter: anatol.pomozov@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: macfuse --------------------------------------+------------------------------------- Hi, I propose to remove macfuse port (or replace it with a dumb stub that installs fuse4x as a dependency). The reasons are following: - macfuse officially declared itself as a dead project. See its official page http://code.google.com/p/macfuse/ it recommends to use its forks instead. - fuse4x fork exists and actively used/developed for more that 6 months already. This is default fuse implementation both in macports and homebrew. - people still have problems on macports+macfuse. Here is a recent example of it https://groups.google.com/d/topic/osxfuse- group/WOT0x3gBN5Q/discussion some people complain that they cannot use CurlFtpFs+macports+macfuse and it was suggested to uninstall macports' version of macfuse and use macfusion application instead. The right answer here is to install fuse4x port instead of macfuse. fuse4x port fixes the issue described in the message. If that person had fuse4x then there should not be any issues. -- Ticket URL: <https://trac.macports.org/ticket/32516> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 6

[MacPorts] #32692: texlive-fonts-extra: rsfso font map is not enabled by default
by MacPorts 29 Dec '11

29 Dec '11

#32692: texlive-fonts-extra: rsfso font map is not enabled by default -----------------------------------+---------------------------------------- Reporter: vloodo@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Low | Milestone: Component: ports | Version: 2.0.3 Keywords: texlive, fonts, rsfso | Port: texlive-fonts-extra -----------------------------------+---------------------------------------- I am trying to use the rsfso font, but I get errors at compilation time: {{{ mktexpk: don't know how to create bitmap font for rrsfso10. mktexpk: perhaps rrsfso10 is missing from the map file. kpathsea: Appending font creation commands to missfont.log. }}} Apparently this used to be a [http://www.tug.org/pipermail/tex- live/2011-August/029945.html bug in texlive] that is now fixed, but not in MacPorts. The link also provides two workarounds that do the job for me, but they are slightly annoying. I either have to place {{{\pdfmapfile{+rsfso.map}}}} in my file or, every time I update texlive, I have to run {{{ sudo updmap-sys --enable MixedMap=rsfso.map }}} -- Ticket URL: <https://trac.macports.org/ticket/32692> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #31335: postgresql91 @9.1.0 cannot select as default postgresql
by MacPorts 29 Dec '11

29 Dec '11

#31335: postgresql91 @9.1.0 cannot select as default postgresql ------------------------------------------+--------------------------------- Reporter: md14-macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: postgresql91 ------------------------------------------+--------------------------------- After installing postgresql91, I could not select postgresql91 as the default postgresql. {{{ $ port installed 'name:^postgresql[0-9]+$' The following ports are currently installed: postgresql90 @9.0.4_0+python (active) postgresql91 @9.1.0_0+python (active) $ port select --list postgresql Available versions for postgresql: none postgresql90 (active) $ sudo port select --set postgresql postgresql91 Selecting 'postgresql91' for 'postgresql' failed: The specified version 'postgresql91' is not valid. }}} -- Ticket URL: <https://trac.macports.org/ticket/31335> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #22751: Config error: gnustep-base
by MacPorts 29 Dec '11

29 Dec '11

#22751: Config error: gnustep-base --------------------------------------+------------------------------------- Reporter: lisfolks.lists@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.1 Keywords: | Port: gnustep-base --------------------------------------+------------------------------------- Similar to gnustep-make error in ticket #22729... I'm getting the following error while updating gnustep-base: ***** Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports .org_release_ports_gnustep_gnustep-base/work/gnustep-base-1.19.1" && ./configure --prefix=/opt/local CC=gcc-mp-4.2 GNUSTEP_MAKEFILES=/opt/local/GNUstep/System/Library/Makefiles --disable- tls --enable-libffi --with-ffi-include=/opt/local/include/gcc42 --with- ffi-library=/opt/local/lib/gcc42 " returned error 77 Command output: checking build system type... i386-apple-darwin9.8.0 checking host system type... i386-apple-darwin9.8.0 checking target system type... i386-apple-darwin9.8.0 checking for gcc... gcc-mp-4.2 checking for C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details. Error: Unable to upgrade port: 1 ***** I've attached my config.log. The key text appears to be: configure:1915: gcc-mp-4.2 -V </dev/null >&5 '''gcc-mp-4.2: '-V' option must have argument''' configure:1918: $? = 1 configure:1941: checking for C compiler default output file name configure:1944: gcc-mp-4.2 -O2 -arch i386 -I/opt/local/include -I/opt/local/GNUstep/System/Library/Headers -I/opt/local/GNUstep/Local/Library/Headers -L/opt/local/lib -L/opt/local/GNUstep/System/Library/Libraries -L/opt/local/GNUstep/Local/Library/Libraries conftest.c >&5 '''cc1: error: unrecognized command line option "-arch"''' -- Ticket URL: <http://trac.macports.org/ticket/22751> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #32690: rxvt-unicode unrecognized options: --with-codeset
by MacPorts 28 Dec '11

28 Dec '11

#32690: rxvt-unicode unrecognized options: --with-codeset ----------------------------------+----------------------------------------- Reporter: jdforge@… | Owner: macports-tickets@… Type: request | Status: new Priority: Low | Milestone: Component: ports | Version: 2.0.3 Keywords: unrecognized options | Port: rxvt-unicode @9.11 ----------------------------------+----------------------------------------- please update Portfile for proper configure.args --with-codesets=all throws configure: WARNING: unrecognized options: --with-codeset -- Ticket URL: <https://trac.macports.org/ticket/32690> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 1

[MacPorts] #29508: ghostscript fails, 9.02 vs 9.00?
by MacPorts 28 Dec '11

28 Dec '11

#29508: ghostscript fails, 9.02 vs 9.00? -------------------------------------+-------------------------------------- Reporter: david.reitter@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: -------------------------------------+-------------------------------------- "port install ghostscript" fails for me. :debug:main Skipping completed org.macports.configure (ghostscript) :msg:main ---> Building ghostscript :debug:build build phase started at Thu May 19 12:06:28 EDT 2011 :debug:build Executing org.macports.build (ghostscript) :debug:build Environment: CPATH='/opt/local/include' CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_print_ghostscript/work/.CC_PRINT_OPTIONS' LIBRARY_PATH='/opt/local/lib' CC_PRINT_OPTIONS='YES' MACOSX_DEPLOYMENT_TARGET='10.6' :debug:build Assembled command: 'cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_print_ghostscript/work/ghostscript-9.02" && /usr/bin/make so' :info:build sh: line 0: cd: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_print_ghostscript/work/ghostscript-9.02: No such file or directory :info:build shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_print_ghostscript/work/ghostscript-9.02" && /usr/bin/make so " returned error 1 :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 ghostscript): org.macports.activate org.macports.build org.macports.destroot org.macports.install :notice:build Log for ghostscript is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_print_ghostscript/main.log Note, I have work/ghostscript-9.00 present on my machine after this. -- Ticket URL: <https://trac.macports.org/ticket/29508> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #30392: Variant conflict causes port info to fail
by MacPorts 28 Dec '11

28 Dec '11

#30392: Variant conflict causes port info to fail ------------------------------------------+--------------------------------- Reporter: macsforever2000@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 2.0.99 Keywords: | Port: ------------------------------------------+--------------------------------- I'm running the latest macports from trunk. I see the following strange error with the splash port: {{{ $ port info splash Error: splash: Variant gcc45 conflicts with gcc44 Error: Unable to open port: Error evaluating variants }}} In the portfile I see the following: {{{ default_variants +gcc44 +pgplot }}} And in my variants.conf file I have the following: {{{ +python26 +gcc45 }}} So it appears that variants with {{{conflicts}}} should not appear in {{{default_variants}}}. I'm not sure where the problem is exactly, base or the port. But certainly {{{port info}}} does not need to evaluate variants before executing. I'm Cc'ing the maintainer of the splash port. -- Ticket URL: <https://trac.macports.org/ticket/30392> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 8