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

Re: [MacPorts] #13444: In Leopard man page for 'port' is missing or not accessable
by MacPorts 06 Aug '08

06 Aug '08

#13444: In Leopard man page for 'port' is missing or not accessable ----------------------------------+----------------------------------------- Reporter: dergaspode(a)gmx.info | Owner: jmpp(a)macports.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.6.0 Resolution: | Keywords: man ----------------------------------+----------------------------------------- Comment (by blb(a)macports.org) It definitely should be smart about it; [http://paste.lisp.org/display/62957 the patch] isn't too complicated. -- Ticket URL: <http://trac.macports.org/ticket/13444#comment:10> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 0

Re: [MacPorts] #13444: In Leopard man page for 'port' is missing or not accessable
by MacPorts 06 Aug '08

06 Aug '08

#13444: In Leopard man page for 'port' is missing or not accessable ----------------------------------+----------------------------------------- Reporter: dergaspode(a)gmx.info | Owner: jmpp(a)macports.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.6.0 Resolution: | Keywords: man ----------------------------------+----------------------------------------- Comment (by jokkel(a)gmail.com) ''.bash_profile takes precedence over .profile. MacPorts only attempts to modify .profile, not .bash_profile. ''[[BR]] [[BR]] Well, I didn't know that. Could the installer not check for .bash_profile and write to it too, if it's found? I know lots of people using .bash_profile to get color coding for folders, files, links. Or at least this should be mentioned in the docs somewhere. -- Ticket URL: <http://trac.macports.org/ticket/13444#comment:9> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 0

Re: [MacPorts] #13444: In Leopard man page for 'port' is missing or not accessable
by MacPorts 06 Aug '08

06 Aug '08

#13444: In Leopard man page for 'port' is missing or not accessable ----------------------------------+----------------------------------------- Reporter: dergaspode(a)gmx.info | Owner: jmpp(a)macports.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.6.0 Resolution: | Keywords: man ----------------------------------+----------------------------------------- Comment (by jokkel(a)gmail.com) Replying to [comment:7 ryandesign(a)macports.org] > @jokkel: it sounds like you're saying that you have a .profile and a .bash_profile, and setting MANPATH in .profile had no effect, while setting MANPATH in .bash_profile worked. And that's exactly right. .bash_profile takes precedence over .profile. MacPorts only attempts to modify .profile, not .bash_profile. -- Ticket URL: <http://trac.macports.org/ticket/13444#comment:8> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 0

Re: [MacPorts] #13444: In Leopard man page for 'port' is missing or not accessable
by MacPorts 06 Aug '08

06 Aug '08

#13444: In Leopard man page for 'port' is missing or not accessable ----------------------------------+----------------------------------------- Reporter: dergaspode(a)gmx.info | Owner: jmpp(a)macports.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.6.0 Resolution: | Keywords: man ----------------------------------+----------------------------------------- Changes (by ryandesign(a)macports.org) * cc: jokkel(a)gmail.com, ryandesign(a)macports.org (added) Comment: @jokkel: it sounds like you're saying that you have a .profile and a .bash_profile, and setting MANPATH in .profile had no effect, while setting MANPATH in .bash_profile worked. And that's exactly right. .bash_profile takes precedence over .profile. MacPorts only attempts to modify .profile, not .bash_profile. -- Ticket URL: <http://trac.macports.org/ticket/13444#comment:7> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 0

Re: [MacPorts] #14876: nethack build failure
by MacPorts 05 Aug '08

05 Aug '08

#14876: nethack build failure -----------------------------+---------------------------------------------- Reporter: tietze(a)mail.dk | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: nethack build error -----------------------------+---------------------------------------------- Comment (by tietze(a)mail.dk) Very cool after editing the Portfile the directory reported by "port dir nethack" and installing two times it build without problems :-) Great! -- Ticket URL: <http://trac.macports.org/ticket/14876#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 0

Re: [MacPorts] #13293: php5: calling curl_version() results in bus error
by MacPorts 05 Aug '08

05 Aug '08

#13293: php5: calling curl_version() results in bus error --------------------------------+------------------------------------------- Reporter: joe(a)slagwerks.com | Owner: ryandesign(a)macports.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.5.0 Resolution: | Keywords: php curl --------------------------------+------------------------------------------- Changes (by ryandesign(a)macports.org) * cc: gage(a)math.rochester.edu (added) Comment: Replying to [comment:12 gage(a)math.rochester.edu] > Has this issue of bus errors occuring when both apache2 and curl are in use been resolved? I am experiencing the same problem when running perl scripts. Scripts that include system calls to curl or to lwp-request cause a bus error. I still cannot reproduce this problem on my systems, either with 10.4.11 or 10.5.4. If you can attach a minimal perl script which I can run on my systems to see the problem, I can attempt to look into this further. -- Ticket URL: <http://trac.macports.org/ticket/13293#comment:13> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 0

Re: [MacPorts] #13293: php5: calling curl_version() results in bus error
by MacPorts 05 Aug '08

05 Aug '08

#13293: php5: calling curl_version() results in bus error --------------------------------+------------------------------------------- Reporter: joe(a)slagwerks.com | Owner: ryandesign(a)macports.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.5.0 Resolution: | Keywords: php curl --------------------------------+------------------------------------------- Comment (by gage(a)math.rochester.edu) Has this issue of bus errors occuring when both apache2 and curl are in use been resolved? I am experiencing the same problem when running perl scripts. Scripts that include system calls to curl or to lwp-request cause a bus error. I am running Leopard (10.5.4) on macbook and am using the apache2, curl and lwp-request downloaded from macports. Another description of this problem is at http://webwork.maa.org/moodle/mod/forum/discuss.php?d=6043 I have seen similar reports dating from November 2007 about macports and the (then new ) leopard installation. I have also seen reports from debian builds from earlier years that were fixed by "upgrading to the newest release". Unfortunately I wasn't able to find any details about the fix. Thank you for your attention. Take care, Mike Gage U. of Rochester -- Ticket URL: <http://trac.macports.org/ticket/13293#comment:12> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 0

[MacPorts] #15916: Updated portfile for logtalk 2.32.1
by MacPorts 05 Aug '08

05 Aug '08

#15916: Updated portfile for logtalk 2.32.1 --------------------------------+------------------------------------------- Reporter: pmoura(a)logtalk.org | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Port Updates Component: ports | Version: 1.6.0 Keywords: | --------------------------------+------------------------------------------- Updated portfile for logtalk 2.32.1. Supersedes ticket #15641. -- Ticket URL: <http://trac.macports.org/ticket/15916> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #15964: file 4.2.5 fails to fetch
by MacPorts 05 Aug '08

05 Aug '08

#15964: file 4.2.5 fails to fetch ------------------------------------------+--------------------------------- Reporter: macsforever2000(a)macports.org | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: | ------------------------------------------+--------------------------------- When i run the following: {{{ sudo port -d upgrade file }}} I see the following error: {{{ ---> Attempting to fetch file-4.25.tar.gz from ftp://ftp.astron.com/pub/file/ % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 58222 100 58222 0 0 39980 0 0:00:01 0:00:01 --:--:-- 145k DEBUG: Fetching failed:: Transferred a partial file }}} But if I manually download the file, it works fine. I'm not sure where the problem lies, the Portfile seems correct on this. -- Ticket URL: <http://trac.macports.org/ticket/15964> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

Re: [MacPorts] #14968: openmpi-1.2.6 compilation error on OS 10.5.2
by MacPorts 05 Aug '08

05 Aug '08

#14968: openmpi-1.2.6 compilation error on OS 10.5.2 ------------------------------------+--------------------------------------- Reporter: wallchuck(a)hotmail.com | Owner: mww(a)macports.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: openmpi conflicting types compilation error ------------------------------------+--------------------------------------- Comment (by macsforever2000(a)macports.org) See also ticket #16150 which describes a possible workaround of uninstalling MPICH first. -- Ticket URL: <http://trac.macports.org/ticket/14968#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 0