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

[MacPorts] #16262: netcdf update 3.6.2 -> 4.0
by MacPorts 22 May '09

22 May '09

#16262: netcdf update 3.6.2 -> 4.0 --------------------------------+------------------------------------------- Reporter: mmoll(a)macports.org | Owner: fulton(a)cmu.edu Type: enhancement | Status: new Priority: Normal | Milestone: Port Updates Component: ports | Version: 1.6.0 Keywords: | --------------------------------+------------------------------------------- Patched Portfile for netcdf upgrade -- Ticket URL: <http://trac.macports.org/ticket/16262> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 27

[MacPorts] #15772: ccache support sets incompatible compiler
by MacPorts 22 May '09

22 May '09

#15772: ccache support sets incompatible compiler ----------------------------------+----------------------------------------- Reporter: landonf(a)macports.org | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Keywords: | ----------------------------------+----------------------------------------- Prior to the introduction of ccache-specific functionality, ccache could be enabled by setting the binpath in macports.conf. This would result in standard compiler names being found in /opt/local/libexec/ccache. With the introduction of ccache-specific functionality -- in of itself a layering violation -- the compiler is now munged at configure-time: {{{ CC=ccache /usr/bin/gcc-4.0 }}} This "two word" CC command breaks some otherwise valid Makefile that expect CC to be a single command. An example: {{{ ifndef $(CXX) CXX = c++ endif }}} Results in: {{{ Makefile:8: *** invalid syntax in conditional. Stop. }}} -- Ticket URL: <http://trac.macports.org/ticket/15772> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #17427: MacPorts 1.6 installation failure after Leopard hard drive replacement
by MacPorts 22 May '09

22 May '09

#17427: MacPorts 1.6 installation failure after Leopard hard drive replacement ------------------------------------+--------------------------------------- Reporter: equipoise1@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: | Port: ------------------------------------+--------------------------------------- I recently replaced a hard drive on my Core2Duo MacBook Pro. I had previously installed MacPorts on the old drive. After replacing the old drive and installing leopard, I had all of my Mac OS X user settings copied onto the new drive. I then installed Xcode and X11. Next I installed MacPorts on the new drive. Then I tried: port variants octave and port install octave This chugged away for a while but produced error msgs. The gist of these concerned Perl 5.8.8.something and the fact that /some/path/to/a2p is being used (is active?) by an earlier version of perl5. I've googled to some stuff about this, including the same error msg. This msg includes a suggestion about using the "-f" option. Question 1: Where do I read about the "-f" option, which I believe pertains to the "port" command, and information explaining other options? An hour of googling on this has been largely unproductive. I've also been unable to bring up a man page on "port". I believe these problems have to do with vestigial registry information from my earlier installation on the old drive. Now I'd like to revert my OS to where it stood after I installed it on the new drive but before I installed MacPorts. I'm concerned about losing things like gcc, which existed independent of what I've tried with MacPorts. Question 2: How can I remove everything related to MacPorts, including anything that it did install, while not endangering things that would have been come with the Leopard and Xcode installation I did? Question 3: Before removing things installed under MacPorts, is there a way to determine which of these components may be usable? Question 4: When I've purged the old things, should I be able to reinstall MacPorts according to the instructions in the guide, or will some alternative approach be required? Thanks. -- Ticket URL: <http://trac.macports.org/ticket/17427> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #17332: checksum error when installing jdom-1.6.1
by MacPorts 22 May '09

22 May '09

#17332: checksum error when installing jdom-1.6.1 ---------------------------------------+------------------------------------ Reporter: sgendler(a)appliedminds.com | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: dom4j | Port: dom4j ---------------------------------------+------------------------------------ I got repeated checksum errors, despite clean --all and other remedies. I compared Portfile to checksum of file retrieved from sourceforge URL in port output and the checksums matched. The checksum for the file downloaded by port, however, was utterly different: INCORRECT: [96] ...distfiles/dom4j %>openssl md5 dom4j-1.6.1.tar.gz MD5(dom4j-1.6.1.tar.gz)= 520b2f0cbfcabca66786d8da1d033ae5 CORRECT: ~/Downloads %>openssl md5 dom4j-1.6.1.tar.gz MD5(dom4j-1.6.1.tar.gz)= 1e7ef6d20939315714de4a8502f27b2d Both files were downloaded simultaneously - one via Safari and the other via port. I'd be inclined to blame some sort of caching between my computer and sourceforge, except that it appears to be dependent upon user-agent. I just checked, and got the correct file via mozilla, too. I'll probably simulate the port user-agent in a browser and sees what happens in a bit, but I need to get back to work for a while, first. I've been battling this problem for well over an hour already. It'd help if someone were to post the user-agent so that I don't have to go sniffing for it on the wire. -- Ticket URL: <http://trac.macports.org/ticket/17332> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #17087: Bad url for scsh-0.6.7
by MacPorts 22 May '09

22 May '09

#17087: Bad url for scsh-0.6.7 ---------------------------------+------------------------------------------ Reporter: jrh(a)theptrgroup.com | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: | Port: scsh ---------------------------------+------------------------------------------ In the Portfile, the line {{{ master_sites ftp://ftp.scsh.net/pub/scsh/0.6/ }}} should be changed to {{{ master_sites http://ftp.scsh.net/pub/scsh/0.6/ }}} to match the link as given at http://www.scsh.net/download/download.html (despite the server's name, it uses http and not ftp). -- Ticket URL: <http://trac.macports.org/ticket/17087> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #16333: postgres command not found
by MacPorts 22 May '09

22 May '09

#16333: postgres command not found -------------------------------+-------------------------------------------- Reporter: neridaj(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Keywords: | -------------------------------+-------------------------------------------- Hello, I'm new to macports and I just installed postgresql 8.3.3 with the command sudo port install postgresql83 and when I try to start the server with postgres -D /usr/local/pgsql/data I get a postgres command not found. Is there a post installation procedure I need to follow before starting the server? Thanks, Jason -- Ticket URL: <http://trac.macports.org/ticket/16333> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #15474: port upgrade: www/shttpd 1.34 -> 1.41
by MacPorts 22 May '09

22 May '09

#15474: port upgrade: www/shttpd 1.34 -> 1.41 -------------------------------+-------------------------------------------- Reporter: valenok(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Keywords: | -------------------------------+-------------------------------------------- -- Ticket URL: <http://trac.macports.org/ticket/15474> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 1

[MacPorts] #16432: diffstat uses unstable distfile name
by MacPorts 22 May '09

22 May '09

#16432: diffstat uses unstable distfile name ------------------------------------+--------------------------------------- Reporter: carl.shapiro(a)gmail.com | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: diffstat | ------------------------------------+--------------------------------------- The diffstat port routinely fails to build when a new version of diffstat has been released and MacPorts has not caught up. This problem is affecting the diffstat port as the most current version of diffstat is 1.46 and the port references 1.45. The reason for this is that the Portfile specifies a distfile name that is a soft link for the latest version. The distfile should use the specific distribution file name, not the soft link to the most recent version. A patch is provided below. -- Ticket URL: <http://trac.macports.org/ticket/16432> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #15364: otest-41 depends on nonexistent port sentestingkit
by MacPorts 19 May '09

19 May '09

#15364: otest-41 depends on nonexistent port sentestingkit ---------------------------------------------+------------------------------ Reporter: blb(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: port bug nonexistent dependency | ---------------------------------------------+------------------------------ devel/otest depends on {{{port:sentestingkit}}} which doesn't exist. -- Ticket URL: <http://trac.macports.org/ticket/15364> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #16246: sudo port activate does not work
by MacPorts 19 May '09

19 May '09

#16246: sudo port activate does not work --------------------------------------+------------------------------------- Reporter: robert(a)hellometro.com | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.6.0 Keywords: port activate activating | --------------------------------------+------------------------------------- sudo port activate kdeaccessibility3 ---> Activating kdeaccessibility3 Never finishes, never returns an error, never activates package sudo port activate gsed ---> Activating gsed 4.1.5_3 Never finishes, never returns an error, never activates package -- Ticket URL: <http://trac.macports.org/ticket/16246> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 8