Inkscape as non-root? (- gnome-vs - gconf - policykit - fail)

2009-05-28 Thread Kevin Reid
I run MacPorts as a dedicated non-root non-admin user. Attempting to  
install Inkscape eventually installs policykit, which fails because it  
tries to create a user. What should be changed in order to be able to  
use Inkscape without any users or other administrative changes involved?


--
Kevin Reidhttp://homepage.mac.com/kpreid/


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Inkscape as non-root? (- gnome-vs - gconf - policykit - fail)

2009-05-28 Thread Alex Zavatone
Kevin, do you have any tips in how to set it up?  I've had no luck,  
even after reading the tutorials.  Currently, trying to hit the apache  
server causes an error at printf and ntop bails.


I'm on a Quad G5 with 10.5.7

Thanks in advance,

- Alex Zavatone

On May 28, 2009, at 11:33 AM, Kevin Reid wrote:

I run MacPorts as a dedicated non-root non-admin user. Attempting to  
install Inkscape eventually installs policykit, which fails because  
it tries to create a user. What should be changed in order to be  
able to use Inkscape without any users or other administrative  
changes involved?


--
Kevin Reidhttp://homepage.mac.com/ 
kpreid/



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Inkscape as non-root? (- gnome-vs - gconf - policykit - fail)

2009-05-28 Thread Kevin Reid

On May 28, 2009, at 12:35, Alex Zavatone wrote:

Kevin, do you have any tips in how to set it up?  I've had no luck,  
even after reading the tutorials.  Currently, trying to hit the  
apache server causes an error at printf and ntop bails.


Sorry, I'm not sure what you're asking about. If you mean running  
MacPorts as non-root, I don't use Apache or ntop via MacPorts so I  
can't comment on those ports.


--
Kevin Reidhttp://homepage.mac.com/kpreid/


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Installing nagios +monarch I receive the error: The following dependencies failed to build: monarch

2009-05-28 Thread Lance Lakey
I've tried uninstalling and cleaning and reinstalling. The only error
I receive is below.

$ sudo port install -duc nagios +monarch
Error: The following dependencies failed to build: monarch
Error: Status 1 encountered during processing.

I've tried cleaning the above ports and then installing nagios only
without +monarch and it never finishes Activating

What could I investigate to figure out what's causing either of these
problems? Thanks in advance.


$ sudo port install -duc nagios
---  Fetching nagios
---  Attempting to fetch nagios-3.0.6.tar.gz from
http://superb-east.dl.sourceforge.net/nagios
---  Verifying checksum(s) for nagios
---  Extracting nagios
---  Configuring nagios
---  Building nagios
---  Staging nagios into destroot
---  Creating launchd control script
###
# A startup item has been generated that will aid in
# starting nagios with launchd. It is disabled
# by default. Execute the following command to start it,
# and to cause it to launch at startup:
#
# sudo launchctl load -w /Library/LaunchDaemons/org.macports.nagios.plist
###
---  Installing nagios @3.0.6_0
---  Activating nagios @3.0.6_0
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: building py-pyobjc2 gives $MACOSX_DEPLOYMENT_TARGET mismatch

2009-05-28 Thread Ryan Schmidt

On May 28, 2009, at 11:06, Harry van der Wolf wrote:


I have the following settings in my  macports.conf:
# MACOSX_DEPLOYMENT_TARGET
universal_target10.4

# the SDK sysroot to use
universal_sysroot   /Developer/SDKs/MacOSX10.4u.sdk

# machine architectures
universal_archs ppc i386

I'm now trying to build py-game which needs py-pyobjc2 as  
dependency. Universal didn't work, but that's no problem as I only  
need this one on my own macbook. So, I tried to built py-game with - 
universal.


All went fine to py-pyobjc2 which menations  
distutils.errors.DistutilsPlatformError: $MACOSX_DEPLOYMENT_TARGET  
mismatch: now 10.5 but 10.4 during configure.
I did a port clean of py-pyobjc2 and changed the 10.4 setting to  
10.5 and tried to build py-pyobjc2 again. The same error still  
occurred, so I changed it back to 10.4.


What can I do about this?


My understanding is that PyObjC 2.x requires Mac OS X 10.5.x or  
greater (thus the 10.5 or greater SDK and MACOSX_DEPLOYMENT_TARGET  
set to 10.5 or greater), while PyObjC 1.x requires Mac OS X 10.4.x or  
earlier.


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Installing nagios +monarch I receive the error: The following dependencies failed to build: monarch

2009-05-28 Thread Ryan Schmidt

On May 28, 2009, at 12:21, Lance Lakey wrote:


I've tried uninstalling and cleaning and reinstalling. The only error
I receive is below.

$ sudo port install -duc nagios +monarch
Error: The following dependencies failed to build: monarch
Error: Status 1 encountered during processing.

I've tried cleaning the above ports and then installing nagios only
without +monarch and it never finishes Activating

What could I investigate to figure out what's causing either of these
problems? Thanks in advance.


$ sudo port install -duc nagios
---  Fetching nagios
---  Attempting to fetch nagios-3.0.6.tar.gz from
http://superb-east.dl.sourceforge.net/nagios
---  Verifying checksum(s) for nagios
---  Extracting nagios
---  Configuring nagios
---  Building nagios
---  Staging nagios into destroot
---  Creating launchd control script
###
# A startup item has been generated that will aid in
# starting nagios with launchd. It is disabled
# by default. Execute the following command to start it,
# and to cause it to launch at startup:
#
# sudo launchctl load -w /Library/LaunchDaemons/ 
org.macports.nagios.plist

###
---  Installing nagios @3.0.6_0
---  Activating nagios @3.0.6_0


We would need to see debug output to know why either of these is  
failing.


The -d flag gives you debug output, but you're not seeing it because  
you've put the flag in the wrong place. It needs to be before, not  
after, the verb. For example, it needs to be


sudo port -d install nagios

and not

sudo port install -d nagios

Note that -u (uninstall old version) only has effect for the  
upgrade verb, and -c (clean) is the default unless you have  
changed the value of portautoclean in your macports.conf.




___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Installing nagios +monarch I receive the error: The following dependencies failed to build: monarch

2009-05-28 Thread Lance Lakey
Thanks for the help. Below is the debug output.

I haven't looked at macports debug output before so I don't know what
to expect but this line looks odd to me:

DEBUG: Requested variant monarch is not provided by port monarch.


$ sudo port -d install nagios +monarch
DEBUG: Found port in
file:///Users/my_user/.macports/var/macports/sources/rsync.macports.org/release/ports/net/nagios
DEBUG: Changing to port directory:
/Users/my_user/.macports/var/macports/sources/rsync.macports.org/release/ports/net/nagios
DEBUG: setting option os.universal_supported to yes
DEBUG: org.macports.load registered provides 'load', a pre-existing
procedure. Target override will not be provided
DEBUG: org.macports.distfiles registered provides 'distfiles', a
pre-existing procedure. Target override will not be provided
DEBUG: adding the default universal variant
DEBUG: Requested variant darwin is not provided by port nagios.
DEBUG: Requested variant i386 is not provided by port nagios.
DEBUG: Requested variant macosx is not provided by port nagios.
DEBUG: Executing variant monarch provides monarch
DEBUG: Found port in
file:///Users/my_user/.macports/var/macports/sources/rsync.macports.org/release/ports/devel/openssl
DEBUG: Changing to port directory:
/Users/my_user/.macports/var/macports/sources/rsync.macports.org/release/ports/devel/openssl
DEBUG: setting option os.universal_supported to yes
DEBUG: org.macports.load registered provides 'load', a pre-existing
procedure. Target override will not be provided
DEBUG: org.macports.distfiles registered provides 'distfiles', a
pre-existing procedure. Target override will not be provided
DEBUG: Using group file
/Users/my_user/.macports/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/muniversal-1.0.tcl
DEBUG: universal variant already exists, so not adding the default one
DEBUG: Requested variant monarch is not provided by port openssl.
DEBUG: Requested variant i386 is not provided by port openssl.
DEBUG: Requested variant macosx is not provided by port openssl.
DEBUG: Executing variant darwin provides darwin
DEBUG: Searching for dependency: openssl
DEBUG: Found Dependency: receipt exists for openssl
DEBUG: Found port in
file:///Users/my_user/.macports/var/macports/sources/rsync.macports.org/release/ports/net/nagios-plugins
DEBUG: Changing to port directory:
/Users/my_user/.macports/var/macports/sources/rsync.macports.org/release/ports/net/nagios-plugins
DEBUG: setting option os.universal_supported to yes
DEBUG: org.macports.load registered provides 'load', a pre-existing
procedure. Target override will not be provided
DEBUG: org.macports.distfiles registered provides 'distfiles', a
pre-existing procedure. Target override will not be provided
DEBUG: Using group file
/Users/my_user/.macports/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/perl5-1.0.tcl
DEBUG: adding the default universal variant
DEBUG: Requested variant monarch is not provided by port nagios-plugins.
DEBUG: Requested variant darwin is not provided by port nagios-plugins.
DEBUG: Requested variant i386 is not provided by port nagios-plugins.
DEBUG: Requested variant macosx is not provided by port nagios-plugins.
DEBUG: Searching for dependency: nagios-plugins
DEBUG: Found Dependency: receipt exists for nagios-plugins
DEBUG: Found port in
file:///Users/my_user/.macports/var/macports/sources/rsync.macports.org/release/ports/net/monarch
DEBUG: Changing to port directory:
/Users/my_user/.macports/var/macports/sources/rsync.macports.org/release/ports/net/monarch
DEBUG: setting option os.universal_supported to yes
DEBUG: org.macports.load registered provides 'load', a pre-existing
procedure. Target override will not be provided
DEBUG: org.macports.distfiles registered provides 'distfiles', a
pre-existing procedure. Target override will not be provided
DEBUG: not using configure, so not adding the default universal variant
DEBUG: Requested variant monarch is not provided by port monarch.
DEBUG: Requested variant darwin is not provided by port monarch.
DEBUG: Requested variant i386 is not provided by port monarch.
DEBUG: Requested variant macosx is not provided by port monarch.
DEBUG: Executing variant server provides server
DEBUG: Searching for dependency: monarch
DEBUG: Didn't find receipt, going to depspec regex for: monarch
DEBUG: Found port in
file:///Users/my_user/.macports/var/macports/sources/rsync.macports.org/release/ports/graphics/gd2
DEBUG: Changing to port directory:
/Users/my_user/.macports/var/macports/sources/rsync.macports.org/release/ports/graphics/gd2
DEBUG: setting option os.universal_supported to yes
DEBUG: org.macports.load registered provides 'load', a pre-existing
procedure. Target override will not be provided
DEBUG: org.macports.distfiles registered provides 'distfiles', a
pre-existing procedure. Target override will not be provided
DEBUG: Using group file

Re: Inkscape as non-root? (- gnome-vs - gconf - policykit - fail)

2009-05-28 Thread Alex Zavatone

Sorry, sorry, I was being a retard.

I was referring to NTOP and having just deleted an NTOP email, I had  
mistakenly replied to yours while not realizing while I was physically  
typing the word, MacPorts, that MacPorts is not NTOP.


The spelling should have made it clear to my but obviously, I had not  
engaged my brain before typing.


I've put myself on Double Secret Probation as punishment.

me.tardness == true

My mother used to drop me as a child.  In those days it was the thing  
to do.


- Zav


On May 28, 2009, at 11:58 AM, Kevin Reid wrote:


On May 28, 2009, at 12:35, Alex Zavatone wrote:

Kevin, do you have any tips in how to set it up?  I've had no luck,  
even after reading the tutorials.  Currently, trying to hit the  
apache server causes an error at printf and ntop bails.


Sorry, I'm not sure what you're asking about. If you mean running  
MacPorts as non-root, I don't use Apache or ntop via MacPorts so I  
can't comment on those ports.


--
Kevin Reidhttp://homepage.mac.com/ 
kpreid/



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Installing nagios +monarch I receive the error: The following dependencies failed to build: monarch

2009-05-28 Thread Daniel J. Luke

On May 28, 2009, at 1:59 PM, Lance Lakey wrote:

Thanks for the help. Below is the debug output.

I haven't looked at macports debug output before so I don't know what
to expect but this line looks odd to me:

DEBUG: Requested variant monarch is not provided by port monarch.



That is not a problem.

It looks like the problem is the +monarch varaint of nagios which  
cannot ever work (it adds a dependency on the monarch port which  
already depends on nagios). Cycles aren't allowed in the dependency  
graph, so this breaks MacPorts.


As a workaround for you, I think you will get what you want by just  
doing `port install monarch`


(I don't use nagios or monarch, so I'm not sure if that will actually  
do what you want, though).

--
Daniel J. Luke
++
| * dl...@geeklair.net * |
| *-- http://www.geeklair.net -* |
++
|   Opinions expressed are mine and do not necessarily   |
|  reflect the opinions of my employer.  |
++





PGP.sig
Description: This is a digitally signed message part
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Installing nagios +monarch I receive the error: The following dependencies failed to build: monarch

2009-05-28 Thread Ryan Schmidt


On May 28, 2009, at 13:15, Daniel J. Luke wrote:

It looks like the problem is the +monarch varaint of nagios which  
cannot ever work (it adds a dependency on the monarch port which  
already depends on nagios). Cycles aren't allowed in the dependency  
graph, so this breaks MacPorts.


I have filed a ticket for this problem:

http://trac.macports.org/ticket/19800


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: building py-pyobjc2 gives $MACOSX_DEPLOYMENT_TARGET mismatch

2009-05-28 Thread Ryan Schmidt


On May 28, 2009, at 13:30, Harry van der Wolf wrote:

My understanding is that PyObjC 2.x requires Mac OS X 10.5.x or  
greater (thus the 10.5 or greater SDK and MACOSX_DEPLOYMENT_TARGET  
set to 10.5 or greater), while PyObjC 1.x requires Mac OS X 10.4.x  
or earlier.


I'm affraid you are right. I had already seen that the Portfile  
mentioned:

if {${os.major}  9} {
pre-fetch {
return -code error PyObjC 2.0 requires Mac OS X 10.5
}
}

But being ON 10.5 I assumed it would work.


Ok, got it, so you were on 10.5 but had your deployment target and  
SDK set to 10.4 in macports.conf.



So I also tried to install the py-pyobjc version:
sudo port install py-pyobjc
---  Computing dependencies for py-pyobjc
---  Fetching py-pyobjc
Error: Target org.macports.fetch returned: PyObjC 1.4 is for Mac OS  
X 10.4 and lower. On 10.5, use py-pyobjc2 instead.

Error: Status 1 encountered during processing.

As that one sensed it was on 10.5 instead of 10.4, I (again)  
assumed that objc2 could also sense that it was on 10.5 despite  
the deployment setting and the 10.4u.sdk.  So I switched back to py- 
pyobjc2.


Yes. As you see, the ports only check the OS version. They don't  
check the SDK version or the deployment target. But if a port says it  
requires 10.5, then it's likely that means it requires the 10.5 SDK  
and the deployment target set to 10.5 as well.



On your reply I also tried to change the macports.conf and set the  
deployment target to 10.5 and the SDK to 10.5 as well.
But again: distutils.errors.DistutilsPlatformError:  
$MACOSX_DEPLOYMENT_TARGET mismatch: now 10.5 but 10.4 during  
configure


So, I'm affraid I'm in some dead-lock.


Did you clean the port after changing your macports.conf, so that it  
runs the configure phase again?


sudo port clean py-pyobjc2



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Specifying PostgreSQL data on startup

2009-05-28 Thread Alexy Khrabrov

I'd like to use the startup scripts for PostgreSQL 8.3 server, in

/opt/local/etc/LaunchDaemons/org.macports.postgresql83-server

with Lingon: http://tuppis.com/lingon/

Now the scripts allow for an environment variable to specify where  
your data is:


   su postgres -c ${PGCTL} -D ${POSTGRESQL83DATA:=/opt/local/var/ 
db/postgresql83/defaultdb} start -l /opt/local/var/log/postgresql83/ 
postgres.log


However, it the server is started on boot, where does  
$POSTGRESQL83DATA come from?


Cheers,
Alexy___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: building py-pyobjc2 gives $MACOSX_DEPLOYMENT_TARGET mismatch

2009-05-28 Thread William Davis

try :
sudo port -d clean py-pyobjc2
and then try to build it again
WSD
On May 28, 2009, at 12:06 PM, Harry van der Wolf wrote:


Hi,

I have the following settings in my  macports.conf:
# MACOSX_DEPLOYMENT_TARGET
universal_target10.4

# the SDK sysroot to use
universal_sysroot   /Developer/SDKs/MacOSX10.4u.sdk

# machine architectures
universal_archs ppc i386

I'm now trying to build py-game which needs py-pyobjc2 as  
dependency. Universal didn't work, but that's no problem as I only  
need this one on my own macbook. So, I tried to built py-game with - 
universal.


All went fine to py-pyobjc2 which menations  
distutils.errors.DistutilsPlatformError: $MACOSX_DEPLOYMENT_TARGET  
mismatch: now 10.5 but 10.4 during configure.
I did a port clean of py-pyobjc2 and changed the 10.4 setting to  
10.5 and tried to build py-pyobjc2 again. The same error still  
occurred, so I changed it back to 10.4.


What can I do about this?


Below the error message.



---  Building py-pyobjc2
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_py-pyobjc2/work/pyobjc-core  / 
opt/local/bin/python2.4 setup.py build  returned error 1

Command output: Traceback (most recent call last):
  File setup.py, line 4, in ?
ez_setup.use_setuptools()
  File /opt/local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_python_py-pyobjc2/work/pyobjc-core/ 
ez_setup/__init__.py, line 81, in use_setuptools

import setuptools
  File /opt/local/lib/python2.4/site-packages/setuptools/ 
__init__.py, line 2, in ?

from setuptools.extension import Extension, Library
  File /opt/local/lib/python2.4/site-packages/setuptools/ 
extension.py, line 2, in ?

from dist import _get_unpatched
  File /opt/local/lib/python2.4/site-packages/setuptools/dist.py,  
line 5, in ?

from setuptools.command.install import install
  File /opt/local/lib/python2.4/site-packages/setuptools/command/ 
__init__.py, line 13, in ?

from distutils.command.bdist import bdist
  File /Library/Frameworks/Python.framework/Versions/2.4/lib/ 
python2.4/distutils/command/bdist.py, line 29, in ?

class bdist (Command):
  File /Library/Frameworks/Python.framework/Versions/2.4/lib/ 
python2.4/distutils/command/bdist.py, line 33, in bdist

user_options = [('bdist-base=', 'b',
  File /Library/Frameworks/Python.framework/Versions/2.4/lib/ 
python2.4/distutils/util.py, line 78, in get_platform

cfgvars = get_config_vars()
  File /Library/Frameworks/Python.framework/Versions/2.4/lib/ 
python2.4/distutils/sysconfig.py, line 488, in get_config_vars

func()
  File /Library/Frameworks/Python.framework/Versions/2.4/lib/ 
python2.4/distutils/sysconfig.py, line 373, in _init_posix

raise DistutilsPlatformError(my_msg)
distutils.errors.DistutilsPlatformError: $MACOSX_DEPLOYMENT_TARGET  
mismatch: now 10.5 but 10.4 during configure



Harry
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users




William Davis
frstanATbellsouthDOTnet
Mac OS X.5.7 Darwin 9.7.0
XQuartz 2.3.3.2 (xorg-server 1.4.2-apple42)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: building py-pyobjc2 gives $MACOSX_DEPLOYMENT_TARGET mismatch

2009-05-28 Thread Harry van der Wolf
Thanks,

but that didn't help either.

I finally managed to build it by setting all SDK settings and deployment
settings in both the macports.conf and the python Makefile to 10.5.
I had to use that settings as well for dependency build py-pyobjc2-cocoa and
py-game itself.

Another complexing factor is that some packages depend on python2.4 and
others on 2.5.
It means that both are on my system and active.

Thanks all for helping me.

Harry

2009/5/28 William Davis frs...@bellsouth.net

 try :sudo port -d clean py-pyobjc2
 *and then try to build it again*
 *WSD
 *
 On May 28, 2009, at 12:06 PM, Harry van der Wolf wrote:

 Hi,

 I have the following settings in my  macports.conf:
 # MACOSX_DEPLOYMENT_TARGET
 universal_target10.4

 # the SDK sysroot to use
 universal_sysroot   /Developer/SDKs/MacOSX10.4u.sdk

 # machine architectures
 universal_archs ppc i386

 I'm now trying to build py-game which needs py-pyobjc2 as dependency.
 Universal didn't work, but that's no problem as I only need this one on my
 own macbook. So, I tried to built py-game with -universal.

 All went fine to py-pyobjc2 which menations
 distutils.errors.DistutilsPlatformError: $MACOSX_DEPLOYMENT_TARGET
 mismatch: now 10.5 but 10.4 during configure.
 I did a port clean of py-pyobjc2 and changed the 10.4 setting to 10.5 and
 tried to build py-pyobjc2 again. The same error still occurred, so I changed
 it back to 10.4.

 What can I do about this?


 Below the error message.



 ---  Building py-pyobjc2
 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_py-pyobjc2/work/pyobjc-core
  /opt/local/bin/python2.4 setup.py build  returned error 1
 Command output: Traceback (most recent call last):
   File setup.py, line 4, in ?
 ez_setup.use_setuptools()
   File
 /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_python_py-pyobjc2/work/pyobjc-core/ez_setup/__init__.py,
 line 81, in use_setuptools
 import setuptools
   File /opt/local/lib/python2.4/site-packages/setuptools/__init__.py,
 line 2, in ?
 from setuptools.extension import Extension, Library
   File /opt/local/lib/python2.4/site-packages/setuptools/extension.py,
 line 2, in ?
 from dist import _get_unpatched
   File /opt/local/lib/python2.4/site-packages/setuptools/dist.py, line 5,
 in ?
 from setuptools.command.install import install
   File
 /opt/local/lib/python2.4/site-packages/setuptools/command/__init__.py,
 line 13, in ?
 from distutils.command.bdist import bdist
   File
 /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/distutils/command/bdist.py,
 line 29, in ?
 class bdist (Command):
   File
 /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/distutils/command/bdist.py,
 line 33, in bdist
 user_options = [('bdist-base=', 'b',
   File
 /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/distutils/util.py,
 line 78, in get_platform
 cfgvars = get_config_vars()
   File
 /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/distutils/sysconfig.py,
 line 488, in get_config_vars
 func()
   File
 /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/distutils/sysconfig.py,
 line 373, in _init_posix
 raise DistutilsPlatformError(my_msg)
 distutils.errors.DistutilsPlatformError: $MACOSX_DEPLOYMENT_TARGET
 mismatch: now 10.5 but 10.4 during configure


 Harry
 ___
 macports-users mailing list
 macports-users@lists.macosforge.org
 http://lists.macosforge.org/mailman/listinfo.cgi/macports-users




 William Davis
 frstanATbellsouthDOTnet
 Mac OS X.5.7 Darwin 9.7.0
 XQuartz 2.3.3.2 (xorg-server 1.4.2-apple42)
 Mac Mini Intel Duo @ 1.86 GHz

 Mundus vult decepi, ego non


___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Specifying PostgreSQL data on startup

2009-05-28 Thread Bryan Blackburn
On Thu, May 28, 2009 at 02:42:44PM -0400, Alexy Khrabrov said:
 I'd like to use the startup scripts for PostgreSQL 8.3 server, in

 /opt/local/etc/LaunchDaemons/org.macports.postgresql83-server

 with Lingon: http://tuppis.com/lingon/

 Now the scripts allow for an environment variable to specify where your 
 data is:

su postgres -c ${PGCTL} -D ${POSTGRESQL83DATA:=/opt/local/var/ 
 db/postgresql83/defaultdb} start -l /opt/local/var/log/postgresql83/ 
 postgres.log

 However, it the server is started on boot, where does $POSTGRESQL83DATA 
 come from?

Note that the ${POSTGRESQL83DATA:=/opt/local/var/db/postgresql83/defaultdb}
is an either/or; if POSTGRESQL83DATA is defined use it, otherwise use that
path.  I don't see POSTGRESQL83DATA being defined anywhere so it's falling
back to that hardcoded path.

If you need to set it you should be able to so with the launchd plist, but
note that any changes to it are going to be lost the next time you upgrade
the postgresql83-server port.

Bryan



 Cheers,
 Alexy
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


gnome missing file

2009-05-28 Thread William Davis

when I tried to upgrade the gnome metaport got this error:
DEBUG: Executing org.macports.destroot (gnome)
Error: Target org.macports.destroot returned: error copying /opt/ 
local/var/macports/sources/rsync.macports.org/release/ports/gnome/ 
gnome/files/README.gnome.txt.in: no such file or directory
Warning: the following items did not execute (for gnome):  
org.macports.destroot

DEBUG: invalid command name ::ui_init
while executing
::ui_init $priority $prefix $channels $message
(uplevel body line 2)
invoked from within
uplevel 1 $body
Error: Unable to upgrade port: 1



William Davis
frstanATbellsouthDOTnet
Mac OS X.5.7 Darwin 9.7.0
XQuartz 2.3.3.2 (xorg-server 1.4.2-apple42)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: gnome missing file

2009-05-28 Thread David Evans

William Davis wrote:

when I tried to upgrade the gnome metaport got this error:
DEBUG: Executing org.macports.destroot (gnome)
Error: Target org.macports.destroot returned: error copying 
/opt/local/var/macports/sources/rsync.macports.org/release/ports/gnome/gnome/files/README.gnome.txt.in: 
no such file or directory
Warning: the following items did not execute (for gnome): 
org.macports.destroot

DEBUG: invalid command name ::ui_init
while executing
::ui_init $priority $prefix $channels $message
(uplevel body line 2)
invoked from within
uplevel 1 $body
Error: Unable to upgrade port: 1


Fixed in r51602.  Thanks.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: building py-pyobjc2 gives $MACOSX_DEPLOYMENT_TARGET mismatch

2009-05-28 Thread Joshua Root
On 2009-5-29 03:51, Ryan Schmidt wrote:
 On May 28, 2009, at 11:06, Harry van der Wolf wrote:
 All went fine to py-pyobjc2 which menations
 distutils.errors.DistutilsPlatformError: $MACOSX_DEPLOYMENT_TARGET
 mismatch: now 10.5 but 10.4 during configure.
 I did a port clean of py-pyobjc2 and changed the 10.4 setting to 10.5
 and tried to build py-pyobjc2 again. The same error still occurred, so
 I changed it back to 10.4.

 What can I do about this?
 
 My understanding is that PyObjC 2.x requires Mac OS X 10.5.x or greater
 (thus the 10.5 or greater SDK and MACOSX_DEPLOYMENT_TARGET set to 10.5
 or greater), while PyObjC 1.x requires Mac OS X 10.4.x or earlier.

That's right. The upcoming 2.2 release should work on both Tiger and
Leopard.

- Josh
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Upgrade errors.

2009-05-28 Thread Frank J. R. Hanstick

Hello,
I got the following errors following:

sudo port selfupdate
sudo port sync
sudo port upgrade installed

---  Cleaning subversion
Error: No port perl5.9 found.
Portfile changed since last build; discarding previous state.
---  Fetching qemu
---  Attempting to fetch qemu-0.10.5.tar.gz from http:// 
mirror.its.uidaho.edu/pub/savannah//qemu

---  Verifying checksum(s) for qemu
---  Extracting qemu
---  Configuring qemu
---  Building qemu
Error: Target org.macports.build returned: shell command  cd /opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync.macports.org_release_ports_emulato 
rs_qemu/work/qemu-0.10.5  make all  returned error 2
Command output: audio/coreaudio.c:67: warning: assignment discards  
qualifiers from pointer target type
audio/coreaudio.c:71: warning: assignment discards qualifiers from  
pointer target type
audio/coreaudio.c:75: warning: assignment discards qualifiers from  
pointer target type
audio/coreaudio.c:79: warning: assignment discards qualifiers from  
pointer target type
audio/coreaudio.c:83: warning: assignment discards qualifiers from  
pointer target type
audio/coreaudio.c:87: warning: assignment discards qualifiers from  
pointer target type
audio/coreaudio.c:91: warning: assignment discards qualifiers from  
pointer target type
audio/coreaudio.c:95: warning: assignment discards qualifiers from  
pointer target type
audio/coreaudio.c:99: warning: assignment discards qualifiers from  
pointer target type
audio/coreaudio.c:103: warning: assignment discards qualifiers from  
pointer target type

  CCaudio/wavcapture.o
  CCcurses.o
  CCvnc.o
  CCd3des.o
  OBJC  cocoa.o
cocoa.m:233: warning: no previous prototype for 'cocoa_keycode_to_qemu'
cocoa.m:318:5: warning: __LITTLE_ENDIAN__ is not defined
cocoa.m: In function '-[QemuCocoaView toggleFullScreen:]':
cocoa.m:426: warning: 'QemuCocoaView' may not respond to '- 
exitFullScreenModeWithOptions:'

cocoa.m:426: warning: (Messages without a matching method signature
cocoa.m:426: warning: will be assumed to return 'id' and accept
cocoa.m:426: warning: '...' as arguments.)
cocoa.m:444: error: 'NSFullScreenModeAllScreens' undeclared (first  
use in this function)

cocoa.m:444: error: (Each undeclared identifier is reported only once
cocoa.m:444: error: for each function it appears in.)
cocoa.m:445: error: 'NSFullScreenModeSetting' undeclared (first use  
in this function)
cocoa.m:446: warning: 'QemuCocoaView' may not respond to '- 
enterFullScreenMode:withOptions:'
cocoa.m: In function '-[QemuCocoaAppController  
openPanelDidEnd:returnCode:contextInfo:]':
cocoa.m:786: warning: initialization discards qualifiers from pointer  
target type

make: *** [cocoa.o] Error 1

Error: Unable to upgrade port: 1
---  Building qemu
Error: Target org.macports.build returned: shell command  cd /opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync.macports.org_release_ports_emulato 
rs_qemu/work/qemu-0.10.5  make all  returned error 2

Command output:   OBJC  cocoa.o
cocoa.m:233: warning: no previous prototype for 'cocoa_keycode_to_qemu'
cocoa.m:318:5: warning: __LITTLE_ENDIAN__ is not defined
cocoa.m: In function '-[QemuCocoaView toggleFullScreen:]':
cocoa.m:426: warning: 'QemuCocoaView' may not respond to '- 
exitFullScreenModeWithOptions:'

cocoa.m:426: warning: (Messages without a matching method signature
cocoa.m:426: warning: will be assumed to return 'id' and accept
cocoa.m:426: warning: '...' as arguments.)
cocoa.m:444: error: 'NSFullScreenModeAllScreens' undeclared (first  
use in this function)

cocoa.m:444: error: (Each undeclared identifier is reported only once
cocoa.m:444: error: for each function it appears in.)
cocoa.m:445: error: 'NSFullScreenModeSetting' undeclared (first use  
in this function)
cocoa.m:446: warning: 'QemuCocoaView' may not respond to '- 
enterFullScreenMode:withOptions:'
cocoa.m: In function '-[QemuCocoaAppController  
openPanelDidEnd:returnCode:contextInfo:]':
cocoa.m:786: warning: initialization discards qualifiers from pointer  
target type

make: *** [cocoa.o] Error 1

Error: Unable to upgrade port: 1
---  Fetching quartz-wm
---  Verifying checksum(s) for quartz-wm
---  Extracting quartz-wm
---  Configuring quartz-wm
---  Building quartz-wm
---  Staging quartz-wm into destroot
---  Deactivating quartz-wm @1.0.3_0
---  Installing quartz-wm @1.0.3_1
---  Activating quartz-wm @1.0.3_1
---  Cleaning quartz-wm
Error: No port render found.
Error: No port render found.

The qemu error I understand; but, I am not sure what the:

Error: No port perl5.9 found.
Error: No port render found.
Error: No port render found.

are about.  I may have seen these before; but, cannot remember when  
or why.

Frank J. R. Hanstick
tro...@comcast.net



___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: Upgrade errors.

2009-05-28 Thread Bryan Blackburn
On Thu, May 28, 2009 at 09:35:57PM -0700, Frank J. R. Hanstick said:
 Hello,
   I got the following errors following:
[...]

 Error: No port perl5.9 found.
 Error: No port render found.
 Error: No port render found.

 are about.  I may have seen these before; but, cannot remember when or 
 why.

perl5.9 was renamed perl5.9-devel over a year ago [1], then deleted about a
month after that [2] in favor of the release-status perl5.10.  Depending on
what you're doing with it, going with perl5.10 is probably the best choice.

The render port was removed [3] in favor of xorg-renderproto after being a
stub port for a while.  Just force-uninstall render and you should be fine
as it should have been only a build-time dependency and xorg-renderproto
takes care of that now.

Unfortunately MacPorts doesn't have any sort of support for
renaming/deleting ports so this kind of issue occasionally surfaces.

Bryan

[1] - http://trac.macports.org/changeset/32171
[2] - http://trac.macports.org/changeset/32638
[3] - http://trac.macports.org/changeset/44924


 Frank J. R. Hanstick
 tro...@comcast.net

___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users