Re: OpenSUSE on MacPorts' virtualbox with funny mouse behaviour
On Jan 30, 2012, at 11:40 PM, Marko Käning wrote: FWIW I use the propriority version of VBOX which has never caused me any problems at all including with SuSE 12.1 How lucky you are! :-) I eventually installed the Oracle's dmg and what shall I say, the problem persists there as well: the left mouse button doesn't work!!! That's the cause of all trouble. I believe I've seen something like this while googling two days ago… I obviously need more research here. :-( FWIW, I am not experiencing this issue with vmware and SUSE SLES 11. Regards, Bradley Giesbrecht (pixilla) ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
postgres launch daemon not working
Hi all, I've been unable to get launchctl to start the PostgreSQL server, even though the daemon appears to be loading. First I installed postgresql84 @8.4.10_0, but it appeared that a launch daemon plist file was not included with the installation. Google searches suggested that the plist file comes with the server, so I installed postgresql84-server @8.4.10_0, which indeed installed the plist file. In contrast with installing '84, '84-server took only moments to complete installation. Invoking launchctl to load the plist file, rebooting or not, then calling `psql` yields the familiar error: psql: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket /tmp/.s.PGSQL.5432? Thinking that the launch daemon was not loaded, I tried loading it again: % sudo launchctl load -w /Library/LaunchDaemons/org.macports.postgresql84-server.plist only to find that it was already loaded: org.macports.postgresql84-server: Already loaded The plist file specifies /opt/local/bin/daemondo, which I confirmed exists and is executable on my machine. I currently have both postgres variants active: postgresql84 @8.4.10_0 (active) postgresql84-server @8.4.10_0 (active) Any suggestions? Thanks in advance! Scott ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: postgres launch daemon not working
Forgot to mention that this is on OSX Lion (10.7.2). On Jan 31, 2012, at 9:55 AM, Scott Frankel wrote: Hi all, I've been unable to get launchctl to start the PostgreSQL server, even though the daemon appears to be loading. First I installed postgresql84 @8.4.10_0, but it appeared that a launch daemon plist file was not included with the installation. Google searches suggested that the plist file comes with the server, so I installed postgresql84-server @8.4.10_0, which indeed installed the plist file. In contrast with installing '84, '84-server took only moments to complete installation. Invoking launchctl to load the plist file, rebooting or not, then calling `psql` yields the familiar error: psql: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket /tmp/.s.PGSQL.5432? Thinking that the launch daemon was not loaded, I tried loading it again: % sudo launchctl load -w /Library/LaunchDaemons/org.macports.postgresql84-server.plist only to find that it was already loaded: org.macports.postgresql84-server: Already loaded The plist file specifies /opt/local/bin/daemondo, which I confirmed exists and is executable on my machine. I currently have both postgres variants active: postgresql84 @8.4.10_0 (active) postgresql84-server @8.4.10_0 (active) Any suggestions? Thanks in advance! Scott ___ 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: postgres launch daemon not working
On Jan 31, 2012, at 12:55 PM, Scott Frankel wrote: Google searches suggested that the plist file comes with the server, so I installed postgresql84-server @8.4.10_0, which indeed installed the plist file. In contrast with installing '84, '84-server took only moments to complete installation. Invoking launchctl to load the plist file, rebooting or not, then calling `psql` yields the familiar error: psql: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket /tmp/.s.PGSQL.5432? did you follow the instructions to create a database instance that the postgresql84-server port printed? (incidentally, they should be moved to notes instead of post-install so that port notes postgresql84-server would print them again). It would have said something like this: To create a database instance, after install do sudo mkdir -p /opt/local/var/db/postgresql84/defaultdb sudo chown postgres:postgres /opt/local/var/db/postgresql84/defaultdb sudo su postgres -c '$/opt/local/lib/postgresql84/bin/initdb -D /opt/local/var/db/postgresql84/defaultdb' To tweak your DBMS, consider increasing kern.sysv.shmmax by adding an increased kern.sysv.shmmax .. to /etc/sysctl.conf Any suggestions? I believe if launchd has trouble starting something it will print some error text in /var/log/system.log -- Daniel J. Luke ++ | * dl...@geeklair.net * | | *-- http://www.geeklair.net -* | ++ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | ++ ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
selfupdate from 2.0.1 to 2.0.3 fails on snow leo with mono installed
Hello, $port -v selfupdate does fail with the following error when mono is installed. Mono: http://www.mono-project.com/Mono:OSX I thought you would be interested in this. I have uninstalled Mono and then it worked very well. And no, I don't have any plans to reinstall it :-) May it be of use for you! Cheers Christian === making all in src/package1.0 === making all in src/pextlib1.0 /usr/bin/cc -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W -Wall -pedantic -DHAVE_CONFIG_H -I.. -I. -I/usr/include -fno-common Pextlib.c -o Pextlib.o /usr/bin/cc -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W -Wall -pedantic -DHAVE_CONFIG_H -I.. -I. -I/usr/include -fno-common strsed.c -o strsed.o /usr/bin/cc -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W -Wall -pedantic -DHAVE_CONFIG_H -I.. -I. -I/usr/include -fno-common fgetln.c -o fgetln.o /usr/bin/cc -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W -Wall -pedantic -DHAVE_CONFIG_H -I.. -I. -I/usr/include -fno-common md5cmd.c -o md5cmd.o /usr/bin/cc -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W -Wall -pedantic -DHAVE_CONFIG_H -I.. -I. -I/usr/include -fno-common setmode.c -o setmode.o /usr/bin/cc -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W -Wall -pedantic -DHAVE_CONFIG_H -I.. -I. -I/usr/include -fno-common xinstall.c -o xinstall.o /usr/bin/cc -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W -Wall -pedantic -DHAVE_CONFIG_H -I.. -I. -I/usr/include -fno-common fs-traverse.c -o fs-traverse.o /usr/bin/cc -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W -Wall -pedantic -DHAVE_CONFIG_H -I.. -I. -I/usr/include -fno-common strcasecmp.c -o strcasecmp.o /usr/bin/cc -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W -Wall -pedantic -DHAVE_CONFIG_H -I.. -I. -I/usr/include -fno-common vercomp.c -o vercomp.o /usr/bin/cc -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W -Wall -pedantic -DHAVE_CONFIG_H -I.. -I. -I/usr/include -fno-common filemap.c -o filemap.o /usr/bin/cc -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W -Wall -pedantic -DHAVE_CONFIG_H -I.. -I. -I/usr/include -fno-common base32cmd.c -o base32cmd.o /usr/bin/cc -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W -Wall -pedantic -DHAVE_CONFIG_H -I.. -I. -I/usr/include -fno-common sha1cmd.c -o sha1cmd.o /usr/bin/cc -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W -Wall -pedantic -DHAVE_CONFIG_H -I.. -I. -I/usr/include -fno-common curl.c -o curl.o /usr/bin/cc -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W -Wall -pedantic -DHAVE_CONFIG_H -I.. -I. -I/usr/include -fno-common rmd160cmd.c -o rmd160cmd.o /usr/bin/cc -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W -Wall -pedantic -DHAVE_CONFIG_H -I.. -I. -I/usr/include -fno-common sha256cmd.c -o sha256cmd.o /usr/bin/cc -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W -Wall -pedantic -DHAVE_CONFIG_H -I.. -I. -I/usr/include -fno-common readline.c -o readline.o /usr/bin/cc -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W -Wall -pedantic -DHAVE_CONFIG_H -I.. -I. -I/usr/include -fno-common uid.c -o uid.o /usr/bin/cc -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W -Wall -pedantic -DHAVE_CONFIG_H -I.. -I. -I/usr/include -fno-common tracelib.c -o tracelib.o /usr/bin/cc -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W -Wall -pedantic -DHAVE_CONFIG_H -I.. -I. -I/usr/include -fno-common tty.c -o tty.o /usr/bin/cc -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W -Wall -pedantic -DHAVE_CONFIG_H -I.. -I. -I/usr/include -fno-common readdir.c -o readdir.o /usr/bin/cc -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W -Wall -pedantic -DHAVE_CONFIG_H -I.. -I. -I/usr/include -fno-common pipe.c -o pipe.o /usr/bin/cc -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W -Wall -pedantic -DHAVE_CONFIG_H -I.. -I. -I/usr/include -fno-common flock.c -o flock.o /usr/bin/cc -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W -Wall -pedantic -DHAVE_CONFIG_H -I.. -I. -I/usr/include -fno-common system.c -o system.o /usr/bin/cc -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W -Wall -pedantic -DHAVE_CONFIG_H -I.. -I. -I/usr/include -fno-common mktemp.c -o mktemp.o /usr/bin/cc -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W -Wall -pedantic -DHAVE_CONFIG_H -I.. -I. -I/usr/include -fno-common realpath.c -o realpath.o /usr/bin/cc -dynamiclib -g -O2 -W -Wall -pedantic -Wl,-single_module Pextlib.o strsed.o fgetln.o md5cmd.o setmode.o xinstall.o fs-traverse.o strcasecmp.o vercomp.o filemap.o base32cmd.o sha1cmd.o curl.o rmd160cmd.o sha256cmd.o readline.o uid.o tracelib.o tty.o readdir.o pipe.o flock.o system.o mktemp.o realpath.o -o Pextlib.dylib -L/System/Library/Frameworks/Tcl.framework/Versions/8.5 -ltclstub8.5 -lcurl -lreadline === making all in src/registry2.0 /usr/bin/cc -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W -Wall -pedantic -I/Library/Frameworks/Mono.framework/Versions/2.10.5/include -DHAVE_CONFIG_H -I.. -I. -I/usr/include -fno-common registry.c -o registry.o In file
Unclear error message while getting started
$ sudo port selfupdate Password: Warning: No index(es) found! Have you synced your source indexes? --- Updating MacPorts base sources using rsync Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: shell command failed (see log for details) $ sudo port sync Password: Warning: No index(es) found! Have you synced your source indexes? Error: Synchronization of the local ports tree failed doing rsync port sync failed: Synchronization of 1 source(s) failed So several questions, but first note this is an absolutely fresh install: 1. what log file? How should I know where it is? 2. If I am doing a sync, how can it be that I haven't synced my source indexes? 3. Why don't the installation guides talk of what is needed to get started? 4. All I really want are a few command line tools (like guile). This is an awful lot of learning and futzing and struggling for such simple needs. Thank you! Regards, Bruce ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Unclear error message while getting started
2. If I am doing a sync, how can it be that I haven't synced my source indexes? Your ISP or firewall is blocking the actual process, otherwise it would just work, as you expected. You can see this by repeating your command with the debug flag (sudo port -d selfupdate). Please consider these alternatives: https://trac.macports.org/wiki/howto/PortTreeTarball https://trac.macports.org/wiki/howto/SyncingWithSVN smime.p7s Description: S/MIME cryptographic signature ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Unclear error message while getting started
Yeah, likely a firewall. The policy here is block everything first and ask questions later. I'll try again when I get home. Thank you. Suggestion: add you may be behind a firewall to the error message. :) Thank you! - Bruce On Tue, Jan 31, 2012 at 11:34 AM, Jeremy Lavergne jer...@lavergne.gotdns.org wrote: 2. If I am doing a sync, how can it be that I haven't synced my source indexes? Your ISP or firewall is blocking the actual process, otherwise it would just work, as you expected. You can see this by repeating your command with the debug flag (sudo port -d selfupdate). Please consider these alternatives: https://trac.macports.org/wiki/howto/PortTreeTarball https://trac.macports.org/wiki/howto/SyncingWithSVN ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: postgres launch daemon not working
Hi Daniel, On Jan 31, 2012, at 10:47 AM, Daniel J. Luke wrote: On Jan 31, 2012, at 12:55 PM, Scott Frankel wrote: Google searches suggested that the plist file comes with the server, so I installed postgresql84-server @8.4.10_0, which indeed installed the plist file. In contrast with installing '84, '84-server took only moments to complete installation. Invoking launchctl to load the plist file, rebooting or not, then calling `psql` yields the familiar error: psql: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket /tmp/.s.PGSQL.5432? did you follow the instructions to create a database instance that the postgresql84-server port printed? Yes, I should've mentioned that. The installation is perfectly functional once I start it manually; eg: % sudo su postgres -c /opt/local/lib/postgresql84/bin/pg_ctl -D /opt/local/var/postgresql84/defaultdb -l /opt/local/var/postgresql84/defaultdb/data/logfile.txt start Previous to this installation, I had postgresql83 running on MacOSX 10.5 (also via macports) and its server started automatically on machine reboots. Not sure why postgres84 on OSX 10.7 isn't behaving similarly. (incidentally, they should be moved to notes instead of post-install so that port notes postgresql84-server would print them again). That'd be nice. It would have said something like this: To create a database instance, after install do sudo mkdir -p /opt/local/var/db/postgresql84/defaultdb sudo chown postgres:postgres /opt/local/var/db/postgresql84/defaultdb sudo su postgres -c '$/opt/local/lib/postgresql84/bin/initdb -D /opt/local/var/db/postgresql84/defaultdb' To tweak your DBMS, consider increasing kern.sysv.shmmax by adding an increased kern.sysv.shmmax .. to /etc/sysctl.conf Any suggestions? I believe if launchd has trouble starting something it will print some error text in /var/log/system.log Thanks for the tip! Jan 31 08:26:02 tiento org.macports.postgresql84-server[1920]: server starting Jan 31 08:29:07 tiento com.apple.SystemStarter[53]: Starting PostgreSQL database server Jan 31 08:29:07 tiento com.apple.SystemStarter[53]: pg_ctl: could not open PID file /Library/PostgreSQL8/data/postmaster.pid: Permission denied Jan 31 08:29:08 tiento SystemStarter[53]: PostgreSQL database server (90) did not complete successfully Looks like pg_ctl is trying to open a postmaster.pid file it doesn't have permissions for. How can I point launchd invocations of pg_ctl to the correct postgres data dir? I initialized my db according to info I gleaned from searches; eg: % sudo su postgres \ -c '/opt/local/lib/postgresql84/bin/initdb -D /opt/local/var/postgresql84/defaultdb' Prior to that, I reinstated the postgres user name with: % sudo dscl . -append /Users/postgres UniqueID 401 I assigned the postgres username to UID 401, as my previous installation's postgres files seemed to be owned by user 401 of group postgres. I wonder if this is the source of the permissions problem. Thanks! Scott -- Daniel J. Luke ++ | * dl...@geeklair.net * | | *-- http://www.geeklair.net -* | ++ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | ++ ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: postgres launch daemon not working
On Jan 31, 2012, at 13:52, Scott Frankel wrote: Jan 31 08:26:02 tiento org.macports.postgresql84-server[1920]: server starting Jan 31 08:29:07 tiento com.apple.SystemStarter[53]: Starting PostgreSQL database server Jan 31 08:29:07 tiento com.apple.SystemStarter[53]: pg_ctl: could not open PID file /Library/PostgreSQL8/data/postmaster.pid: Permission denied Jan 31 08:29:08 tiento SystemStarter[53]: PostgreSQL database server (90) did not complete successfully Looks like pg_ctl is trying to open a postmaster.pid file it doesn't have permissions for. How can I point launchd invocations of pg_ctl to the correct postgres data dir? I initialized my db according to info I gleaned from searches; eg: % sudo su postgres \ -c '/opt/local/lib/postgresql84/bin/initdb -D /opt/local/var/postgresql84/defaultdb' Prior to that, I reinstated the postgres user name with: % sudo dscl . -append /Users/postgres UniqueID 401 I assigned the postgres username to UID 401, as my previous installation's postgres files seemed to be owned by user 401 of group postgres. I wonder if this is the source of the permissions problem. It should not have caused a problem, though it was also unnecessary to create your own postgres user, since that (along with creating the server directories, and the launchd plist) is the purpose of installing the postgresql*-server ports. I'm more concerned about /Library/PostgreSQL8 -- what is that? That doesn't sound like a normal MacPorts location, though I am not actually familiar with postgres so I could be mistaken. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: selfupdate from 2.0.1 to 2.0.3 fails on snow leo with mono installed
On Jan 31, 2012, at 13:15, Christian Grobmeier wrote: /Library/Frameworks/Mono.framework/Versions/2.10.5/include/sqlite3.h:252: Your big problem is you have Frameworks being pulled in from /Library/Frameworks. If you can temporary move them away while building, that will help a lot. As mentioned, I have permanently removed them and I am happy again. I thought this information might be useful (or not) for the port devs. We are already aware that installing a binary package provided by mono will mess up MacPorts, and any other attempts to compile software, because mono's binary package installs things in places it should not. This has come up many times before. For example, it installs a symlink at /usr/bin/pkg-config pointing to mono's copy of pkg-config; only Apple should install things in /usr/bin. Only the developers of mono can fix how they distribute their binary packages. Meanwhile, I have a recollection that some months ago we modified MacPorts base to look in the known OS X location for sqlite first, only falling back to pkg-config if it's not found. However, I can't find that modification in the sources now, and I can't find a ticket about it either. Does anybody else remember this? ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: selfupdate from 2.0.1 to 2.0.3 fails on snow leo with mono installed
On Jan 31, 2012, at 3:49 PM, Ryan Schmidt wrote: Meanwhile, I have a recollection that some months ago we modified MacPorts base to look in the known OS X location for sqlite first, only falling back to pkg-config if it's not found. However, I can't find that modification in the sources now, and I can't find a ticket about it either. Does anybody else remember this? https://trac.macports.org/ticket/30932 I added a patch that should help, but didn't test it (and I don't think it was integrated). -- Daniel J. Luke ++ | * dl...@geeklair.net * | | *-- http://www.geeklair.net -* | ++ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | ++ ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: postgres launch daemon not working
On Jan 31, 2012, at 2:52 PM, Scott Frankel wrote: % sudo su postgres -c /opt/local/lib/postgresql84/bin/pg_ctl -D /opt/local/var/postgresql84/defaultdb -l /opt/local/var/postgresql84/defaultdb/data/logfile.txt start Jan 31 08:29:07 tiento com.apple.SystemStarter[53]: pg_ctl: could not open PID file /Library/PostgreSQL8/data/postmaster.pid: Permission denied Jan 31 08:29:08 tiento SystemStarter[53]: PostgreSQL database server (90) did not complete successfully This looks like you are pointing to a different directory than the one you set up when you installed postgresql84-server (and also a different one than the one you're pointed to when you manually start postgres). Looks like pg_ctl is trying to open a postmaster.pid file it doesn't have permissions for. How can I point launchd invocations of pg_ctl to the correct postgres data dir? If you look at the plist that macports installed, you'll see that it uses a wrapper script to launch the postgres server process. That script will default to using the environment variable $POSTGRESQL84DATA for the data dir (and fall back on the one you show that you're using). It's very likely that you have $POSTGRESQL84DATA set, and you don't want it set. -- Daniel J. Luke ++ | * dl...@geeklair.net * | | *-- http://www.geeklair.net -* | ++ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | ++ ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: How to install a port update ?
On 31/01/2012, at 11:01 PM, macports-users-requ...@lists.macosforge.org wrote: Lastfm port for amarok has updated. I have downloaded a file from this url : https://trac.macports.org/changeset/89263 I don't know how to install it The only thing you need to do is: sudo port selfupdate Since it didn't get a revision update (not sure why not?), if you have liblastfm installed, then you can reinstall it. The committer simply forgot to increment the port's revision in r89263, and did so afterward in r89264. I tried to build amarok with dismal results, but http://code.google.com/p/clementine-player/ is an amorok 1.4 fork that works a treat. It has a dmg package. James ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: How to install a port update ?
On Jan 31, 2012, at 15:15, Michael Parchet wrote: Le 30.01.12 22:02, Jeremy Lavergne a écrit : otool -L /opt/local/lib/liblastfm*dylib otool -L /opt/local/lib/liblastfm*dylib Do you understand something ? As I said in a previous message, this should already be fixed. sudo port selfupdate and sudo port upgrade outdated to receive the fix. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: How to install a port update ?
On Jan 31, 2012, at 15:51, James Linder wrote: I tried to build amarok with dismal results What problem did you encounter? ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: How to install a port update ?
Le 31.01.12 22:51, James Linder a écrit : On 31/01/2012, at 11:01 PM, macports-users-requ...@lists.macosforge.org wrote: Lastfm port for amarok has updated. I have downloaded a file from this url : https://trac.macports.org/changeset/89263 I don't know how to install it The only thing you need to do is: sudo port selfupdate Since it didn't get a revision update (not sure why not?), if you have liblastfm installed, then you can reinstall it. The committer simply forgot to increment the port's revision in r89263, and did so afterward in r89264. I tried to build amarok with dismal results, but http://code.google.com/p/clementine-player/ is an amorok 1.4 fork that works a treat. It has a dmg package. James Tanks james but I wold like lessen podcast with and clementine haven't this feature. So I need amarok to lessen podact online and keep the links. Best regards mparchet ___ 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: How to install a port update ?
On 01/02/2012, at 6:41 AM, Ryan Schmidt wrote: On Jan 31, 2012, at 15:51, James Linder wrote: I tried to build amarok with dismal results What problem did you encounter? Since it was in the early days of using macports (a year ago) I cannot give you a useful answer, just to say the error messages looked so overwhelming that I spent time getting iTunes to play my oggs. I did not try recently, but clementine is kewl and suits my needs and works. Now if you can solve my didikam woes ... (not serious, this looks like a significant issue) James ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: postgres launch daemon not working
Hi Daniel, It works! Details follow below. On Jan 31, 2012, at 1:13 PM, Daniel J. Luke wrote: On Jan 31, 2012, at 2:52 PM, Scott Frankel wrote: % sudo su postgres -c /opt/local/lib/postgresql84/bin/pg_ctl -D /opt/local/var/postgresql84/defaultdb -l /opt/local/var/postgresql84/defaultdb/data/logfile.txt start Jan 31 08:29:07 tiento com.apple.SystemStarter[53]: pg_ctl: could not open PID file /Library/PostgreSQL8/data/postmaster.pid: Permission denied Jan 31 08:29:08 tiento SystemStarter[53]: PostgreSQL database server (90) did not complete successfully This looks like you are pointing to a different directory than the one you set up when you installed postgresql84-server (and also a different one than the one you're pointed to when you manually start postgres). That's exactly what I was trying to explain in my last email. I'm doing nothing explicit to point to the /Library/PostgreSQL8/ directory. Looks like pg_ctl is trying to open a postmaster.pid file it doesn't have permissions for. How can I point launchd invocations of pg_ctl to the correct postgres data dir? If you look at the plist that macports installed, you'll see that it uses a wrapper script to launch the postgres server process. That script will default to using the environment variable $POSTGRESQL84DATA for the data dir (and fall back on the one you show that you're using). It's very likely that you have $POSTGRESQL84DATA set, and you don't want it set. Looks like that env var gets set directly in the wrapper. Thanks for pointing to the script! A quick edit of the script's paths and now the server starts on reboot! Thanks! Scott -- Daniel J. Luke ++ | * dl...@geeklair.net * | | *-- http://www.geeklair.net -* | ++ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | ++ ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: postgres launch daemon not working
On Tue, Jan 31, 2012 at 04:47:09PM -0800, Scott Frankel wrote: On Jan 31, 2012, at 12:34 PM, Ryan Schmidt wrote: It should not have caused a problem, though it was also unnecessary to create your own postgres user, since that (along with creating the server directories, and the launchd plist) is the purpose of installing the postgresql*-server ports. Good to know. How would I have been able to find that out myself? Knowing that ahead of time would've saved me significant effort. It probably wouldn't hurt if the postgresql*-server ports had a more descriptive description... Dan -- Dan R. K. Ports MIT CSAILhttp://drkp.net/ ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: postgres launch daemon not working
That'd be great! Happy to contribute to the effort if I can. Thanks Scott On Jan 31, 2012, at 7:13 PM, Dan Ports wrote: On Tue, Jan 31, 2012 at 04:47:09PM -0800, Scott Frankel wrote: On Jan 31, 2012, at 12:34 PM, Ryan Schmidt wrote: It should not have caused a problem, though it was also unnecessary to create your own postgres user, since that (along with creating the server directories, and the launchd plist) is the purpose of installing the postgresql*-server ports. Good to know. How would I have been able to find that out myself? Knowing that ahead of time would've saved me significant effort. It probably wouldn't hurt if the postgresql*-server ports had a more descriptive description... Dan -- Dan R. K. Ports MIT CSAILhttp://drkp.net/ ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
