date:20120429

That link came up non-existent, but I checked the mysql site and found the published solution about checking for the existence of the .sock file and moving it if it's in the wrong place.So, I found that there was mysql.sock in /private/tmp, but the error indicates it's being looked for in /opt/local/var/run/mysql5, so I moved it there, and I changed the group from 'wheel' to '_mysql'. Once moved, mysql would not start. I did a 'which -a "mysql5"' and it is in /opt/local/bin. However, moving the .sock file back to /private/tmp immediately caused mysql to start again. So, the question is if mysql is looking for the .sock file in the port path, and the mysql process running is from the port path, why does having the socket where it's being looked for break mysql rather than allowing me to run the command line program?

Your best bet is to read the official MySQL reference docs at:

http://dev.mysql.com/doc/refman/5.5/en/connecting-disconnecting.html;




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

Re: mysql problem with socket (was Help with conjoined apaches)

2012-04-29 Thread Phil Dobbin

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 29/04/2012 18:33, j...@ayendesigns.com wrote:

 That link came up non-existent

[snip]

 
 http://dev.mysql.com/doc/refman/5.5/en/connecting-disconnecting.html

 
http://dev.mysql.com/doc/refman/5.5/en/connecting-disconnecting.html;

trailing bracket caused that.

Cheers,

  Phil...

- -- 
But masters, remember that I am an ass.
Though it be not written down,
yet forget not that I am an ass.

Wm. Shakespeare - Much Ado About Nothing


-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: Â§auto-key-locate cert pka ldap hkp://keys.gnupg.net
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPnYJEAAoJEKpMeDHWT5ADjDMH/ihNeFs+EfX4F4qxflnc9M7L
UM0ZrMH6H6owIzkX2Io/p9Fg9EvgRdB86h4jikyD6WL8VB6kEyoyEwMeswOlq2pP
y7ww9Ff/OrMJ4rpbeaevGRhnDYjC+NamQ4avU7urCjMF0fhnG3cyFKq7KYpHTj0L
klC+nvDw8q6wzIgoh1q45wDVO2WyNLBCURbSStB735Cc7bemLl85fmByyQCdx7pn
76082i68FwkepDfI83qM30i41EL0q2DkogwPZPItS0kEhLbQFwi6KwhzO7AR/kAJ
m6pEOKOT2TOMyhpL75z/TgCopOmiQ8qoouxAfebilgwx2rClQKoa2iDYq3QYaFA=
=rC5/
-END PGP SIGNATURE-



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: error message: Couldn't determine your Xcode version

2012-04-29 Thread Marcelo Chiapparini

2012/4/29 Jeremy Lavergne jer...@lavergne.gotdns.org

  Hi Jeremy, thanks for the reply. Here is the result of the command:
 
  marcelo$ sudo xcodebuild -version
  Password:
  error: can't exec '/Applications/Xcode.app/usr/bin/xcodebuild' (No such
 file or directory)
 
  May be a problem with a path?

 Yes, looks like Xcode has its path wrong.

 See what it is, just in case:
 sudo xcode-select -print-path

 Then switch it to the expected one again:
 sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer


Before implementing your advice:

Yggdrasill3:~ marcelo$ sudo xcode-select -print-path
Password:
/Applications/Xcode.app

After your advice:

Yggdrasill3:~ marcelo$ sudo xcode-select -switch
/Applications/Xcode.app/Contents/Developer
Yggdrasill3:~ marcelo$ sudo xcodebuild -version
Xcode 4.3.2
Build version 4E2002

Now port is running fine. The problem was fixed! Thanks a lot t Jeremy

Regards,

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

Re: New port: postgis2 (PostGIS 2.0)

2012-04-29 Thread vincent habchi

Hi Puneet,

 I’ve committed this morning in r92462 a new port corresponding to PostGIS v 
 2.0 and up.
 This port is incompatible with postgis, that is to say PostGIS 1.x. Both 
 install the same files at the same place.
 
 
 Hmmm... That's a deal breaker for me. I don't have two machines to test it 
 out. Since the two different versions can haooily coexist, why not make it so 
 instead of requiring uninstalling PostGIS 1.5?

Because PostGIS 2.0 won’t compile with PostGIS 1.5 installed. There are several 
include files that PostGIS 1.5/2.0 installs in ${prefix}/include that take 
precedence over the ones furnished with the distribution (because 
-I${prefix}/include appears before other -I… during compilation). Thus, if you 
have PostGIS 1.5 installed, PostGIS 2.0 will mistakenly use the already 
installed headers to compile and fail.

Besides, I am not sure that the libraries installed by PostGIS 1.5 and PostGIS 
2.0, albeit bearing the same name, have the same API.

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

Re: gnuplot on MacPorts with aqua?


On Apr 29, 2012, at 13:27, Mojca Miklavec wrote:

 (Are there any guidelines/suggestions
 about filenames of patchfiles? I've seen everything from *.diff to
 *.patch to patch-filename to patch-filename.diff. This is a trivial
 issue though.)

The guideline is that the patchfile name should be patch-FILE.diff where FILE 
is the path to the file being patched, relative to ${patch.dir} (which unless 
you've changed it is the same as ${worksrcpath}). Replace slashes with dashes. 
For example if you're patching the file src/lib/foo.h then the patchfile name 
would be patch-src-lib-foo.h.diff.

If you're patching more than one file but all the patches are to solve the same 
issue then it might make more sense to have a single patchfile, in which case 
you can name it patch-ISSUE.diff where ISSUE is some short identifier 
describing the issue being fixed. For example, many ports are needing patches 
these days to be compatible with glib 2.32, so often that patch will get named 
patch-glib-2.32.diff.

Running port lint --nitpick will let you know if any patchfile names aren't 
following the recommendations. But as you say patchfile naming is trivial, and 
we have many ports whose patchfile names don't follow these recommendations, 
and I'm not overly concerned about that.




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

Re: Help with conjoined apaches


On Apr 28, 2012, at 22:00, Jeremy Lavergne wrote:

 None of these files are provided by MacPorts and files provided by apache2 
 and mysql5 are missing so somehow apache2 and mysql5 were most likely 
 uninstalled by port.
 
 Do you try to do a forced upgrade apache2 and mysql5 that failed? I think 
 that would have uninstalled apache2 and mysql5 before building and 
 installing.
 
 I'd check the code for that one; pretty sure uninstall should never happen 
 until immediately before activate (unless the port itself commands otherwise).

Whether intentionally or not, MacPorts was changed a few versions ago so that 
running

sudo port -n upgrade --force foo

will FIRST uninstall the current version of foo, THEN build the new version of 
foo, which might fail, leaving you with no installed version of foo.



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

Re: Help with conjoined apaches

2012-04-29 Thread Jeremy Lavergne

 Whether intentionally or not, MacPorts was changed a few versions ago so that 
 running
 
 sudo port -n upgrade --force foo
 
 will FIRST uninstall the current version of foo, THEN build the new version 
 of foo, which might fail, leaving you with no installed version of foo.

Huh. I guess that's handy for when a package will pick up its own headers that 
were installed instead of using the ones that are in the source.

I must have forgotten about it happening :-)



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: mysql problem with socket


On Apr 29, 2012, at 12:33, j...@ayendesigns.com wrote:

 That link came up non-existent, but I checked the mysql site and found the 
 published solution about checking for the existence of the .sock file and 
 moving it if it's in the wrong place.
 
 So, I found that there was mysql.sock in /private/tmp, but the error 
 indicates it's being looked for in /opt/local/var/run/mysql5, so I moved it 
 there, and I changed the group from 'wheel' to '_mysql'.
 
 Once moved, mysql would not start. I did a 'which -a mysql5' and it is in 
 /opt/local/bin. However, moving the .sock file back to /private/tmp 
 immediately caused mysql to start again.
 
 So, the question is if mysql is looking for the .sock file in the port path, 
 and the mysql process running is from the port path, why does having the 
 socket where it's being looked for break mysql rather than allowing me to run 
 the command line program?

Do not move a socket file. MySQL needs it to be where it put it.

For a normal MacPorts mysql5 install the socket file is supposed to be at 
/opt/local/var/run/mysql5/mysqld.sock.

If it's in /private/tmp instead, then you probably asked for it to be there by 
modifying your my.cnf file to say so. I recommend you don't do that, and 
instead use the socket at its default location.

It's up to you of course. You can have MySQL put the socket wherever you want. 
But then you also have to tell all other software that uses MySQL (php, etc) 
where the socket is, so it can find it.




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

Re: postfix databases

2012-04-29 Thread Bjarne D Mathiesen

Bjarne D Mathiesen wrote:
 It seems as if postfix could use mariadb and mysql55 variants ;-)
 

I've done some work on adding variant for all the other mysql
implementation to postfix. before I submit at patch I'ld like someone to
just go over my code to see if it's correct :-)

variant mysql5 \
conflicts mysql55 mariadb \
description add mysql support via mysql5.1 {
depends_lib-append path:lib/mysql5/bin/mysql_config:mysql5
lappend CCARGS  -DHAS_MYSQL -I${prefix}/include/mysql5/mysql
lappend AUXLIBS -L${prefix}/lib/mysql5/mysql -lmysqlclient -lz -lm
}

variant mysql55 \
conflicts mysql5 mariadb \
description add mysql support via mysql5.5 {
depends_lib-append path:lib/mysql55/bin/mysql_config:mysql55
lappend CCARGS  -DHAS_MYSQL -I${prefix}/include/mysql55/mysql
lappend AUXLIBS -L${prefix}/lib/mysql55/mysql -lmysqlclient
-lz -lm
}

variant mariadb \
conflicts mysql5 mysql55 \
description add mysql support via mariadb {
depends_lib-append path:lib/mariadb/bin/mysql_config:mariadb
lappend CCARGS  -DHAS_MYSQL -I${prefix}/include/mariadb/mysql
lappend AUXLIBS -L${prefix}/lib/mariadb/mysql -lmysqlclient
-lz -lm
}

variant percona \
conflicts mysql5 mysql55 \
description add mysql support via percona {
depends_lib-append path:lib/percona/bin/mysql_config:percona
lappend CCARGS  -DHAS_MYSQL -I${prefix}/include/percona/mysql
lappend AUXLIBS -L${prefix}/lib/percona/mysql -lmysqlclient
-lz -lm
}

thanks,
-- 
Bjarne D Mathiesen
København N ; Danmark ; Europa
--
denne besked er skrevet i et totalt M$-frit miljø
MacOS X 10.7.3 Lion ; 2.8GHz Intel Core i7 ; 16GB 1067MHz DDR3
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

RE: mysql problem with socket

That would be a nice easy fix, to undo a change I made to my.cnf :-) but in looking at the two lines in /opt/local/etc/mysql5/my.cnf (2 lines?! is there another and that's the problem?), I see:[client]socket = /opt/local/var/run/mysql5/mysqld.sock yet mysql is looking in /private/tmp.I also see a my.cnf at /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/databases/mysql4/files/my.cnf /usr/local/mysql-5.5.15-osx10.6-x86_64/mysql-test/suite/federated/my.cnf/usr/local/mysql-5.5.15-osx10.6-x86_64/mysql-test/suite/rpl/my.cnf 

 Original Message 
Subject: Re: mysql problem with socket
From: Ryan Schmidt ryandes...@macports.org
Date: Sun, April 29, 2012 2:08 pm
To: j...@ayendesigns.com
Cc: macports-users@lists.macosforge.org

On Apr 29, 2012, at 12:33, j...@ayendesigns.com wrote:

 That link came up non-existent, but I checked the mysql site and found the published solution about checking for the existence of the .sock file and moving it if it's in the wrong place.

 So, I found that there was mysql.sock in /private/tmp, but the error indicates it's being looked for in /opt/local/var/run/mysql5, so I moved it there, and I changed the group from 'wheel' to '_mysql'.

 Once moved, mysql would not start. I did a 'which -a "mysql5"' and it is in /opt/local/bin. However, moving the .sock file back to /private/tmp immediately caused mysql to start again.

 So, the question is if mysql is looking for the .sock file in the port path, and the mysql process running is from the port path, why does having the socket where it's being looked for break mysql rather than allowing me to run the command line program?

Do not move a socket file. MySQL needs it to be where it put it.

For a normal MacPorts mysql5 install the socket file is supposed to be at /opt/local/var/run/mysql5/mysqld.sock.

If it's in /private/tmp instead, then you probably asked for it to be there by modifying your my.cnf file to say so. I recommend you don't do that, and instead use the socket at its default location.

It's up to you of course. You can have MySQL put the socket wherever you want. But then you also have to tell all other software that uses MySQL (php, etc) where the socket is, so it can find it.

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

Re: Group file and registry warnings when upgrading swig-python

On Apr 23, 2012, at 12:11, Adam Mercer wrote:

 On updating a couple of my machines today I saw the following:
 
 ---  Computing dependencies for swig-python
 ---  Fetching swig-python
 ---  Verifying checksum(s) for swig-python
 ---  Extracting swig-python
 ---  Configuring swig-python
 ---  Building swig-python
 ---  Staging swig-python into destroot
 ---  Installing swig-python @2.0.5_0
 ---  Cleaning swig-python
 ---  Computing dependencies for swig-python
 Warning: Group file could not be located.
 Warning: Failed to open Portfile from registry for swig-python @2.0.4_0
 ---  Deactivating swig-python @2.0.4_0
 ---  Activating swig-python @2.0.5_0
 ---  Cleaning swig-python
 Warning: Group file could not be located.
 Warning: Failed to open Portfile from registry for swig-python @2.0.4_0
 ---  Uninstalling swig-python @2.0.4_0

Me too.


 Are these warnings anything to worry about?

No, it's only because the old port had been installed before you were using the 
sqlite registry (i.e. before you upgraded to MacPorts 2).



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

RE: mysql problem with socket

Well,  let's back up a second. I installed mysql and mysql-server yesterday,  and didn't make any manual changes, so should the my.cnf in the standard  ports path (/opt/local/etc) only have 2 entries in it normally? Is it a matter then of adding the path to the front of $PATH or renaming the other instances to .old?

 Original Message 
Subject: Re: mysql problem with socket
From: Ryan Schmidt ryandes...@macports.org
Date: Sun, April 29, 2012 3:33 pm
To: j...@ayendesigns.com
Cc: macports-users@lists.macosforge.org

On Apr 29, 2012, at 17:21, j...@ayendesigns.com wrote:

 That would be a nice easy fix, to undo a change I made to my.cnf :-) but in looking at the two lines in /opt/local/etc/mysql5/my.cnf (2 lines?! is there another and that's the problem?)

There are many locations where mysql will look for a my.cnf. I don't know what all they are nor what order they're checked in, but I'm sure the MySQL documentation will tell you.

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

Re: mysql problem with socket

On Apr 29, 2012, at 17:39, j...@ayendesigns.com wrote:

Well, let's back up a second. I installed mysql and mysql-server yesterday,
and didn't make any manual changes, so should the my.cnf in the standard
ports path (/opt/local/etc) only have 2 entries in it normally?

It's normal for /opt/local/etc/mysql5/my.cnf not to exist. MacPorts MySQL
doesn't install it for you. If it exists, it's because you created it and put
things into it. It can contain whatever you need or want in order to configure
MySQL. As long as you do not set socket=whatever in a my.cnf file, it should
use the default socket location I mentioned earlier.

/etc is another place where a my.cnf would be found.

RE: mysql problem with socket

I stopped mysql, renamed the other 3 cnf files to cnf.old, and restarted it. It is still using the sock in /private/tmp even though the only cnf file points to /opt/local. I'm at a loss...should I grep for /private/tmp to try and find where it's buried??

 Original Message 
Subject: Re: mysql problem with socket
From: Ryan Schmidt ryandes...@macports.org
Date: Sun, April 29, 2012 3:50 pm
To: j...@ayendesigns.com
Cc: macports-users@lists.macosforge.org

On Apr 29, 2012, at 17:39, j...@ayendesigns.com wrote:

 Well, let's back up a second. I installed mysql and mysql-server yesterday, and didn't make any manual changes, so should the my.cnf in the standard ports path (/opt/local/etc) only have 2 entries in it normally?

It's normal for /opt/local/etc/mysql5/my.cnf not to exist. MacPorts MySQL doesn't install it for you. If it exists, it's because you created it and put things into it. It can contain whatever you need or want in order to configure MySQL. As long as you do not set "socket=whatever" in a my.cnf file, it should use the default socket location I mentioned earlier.

/etc is another place where a my.cnf would be found.

More documentation at:

http://dev.mysql.com/doc/refman/5.1/en/option-files.html

 Is it a matter then of adding the path to the front of $PATH

$PATH has nothing to do with where MySQL looks for my.cnf or where it puts the socket file.

 or renaming the other instances to .old?

If you find other my.cnf files on your drive and you don't wish for them to be used, you can delete them or rename them as you like.

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

Re: mysql problem with socket


On Apr 29, 2012, at 17:59, j...@ayendesigns.com wrote:

 I stopped mysql, renamed the other 3 cnf files to cnf.old, and restarted it. 
 It is still using the sock in /private/tmp even though the only cnf file 
 points to /opt/local. I'm at a loss...should I grep for /private/tmp to try 
 and find where it's buried??

If you have not already done so, you could try to locate all my.cnf files using:

find / -name my.cnf

Are you sure the mysql that's being started is the one MacPorts installed, and 
not the one you installed in /usr/local? How are you starting / stopping mysql?


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

RE: mysql problem with socket

I had checked with 'find', and /opt/locale/etc/mysql5 is the only my.cnf file. I'm not sure that the mysqld process is port's, only that 'which' shows mysql5 being port's. I start it and stop it via the settings panel.


On Apr 29, 2012, at 17:59, j...@ayendesigns.com wrote:

 I stopped mysql, renamed the other 3 cnf files to cnf.old, and restarted it. It is still using the sock in /private/tmp even though the only cnf file points to /opt/local. I'm at a loss...should I grep for /private/tmp to try and find where it's buried??

If you have not already done so, you could try to locate all my.cnf files using:

find / -name my.cnf

Are you sure the mysql that's being started is the one MacPorts installed, and not the one you installed in /usr/local? How are you starting / stopping mysql?





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

Re: mysql problem with socket


On Apr 29, 2012, at 6:07 PM, Ryan Schmidt wrote:

 Are you sure the mysql that's being started is the one MacPorts installed, 
 and not the one you installed in /usr/local? How are you starting / stopping 
 mysql?


The above is possibly the commonest mistake, and it is easy to check and 
correct.

One can easily determine which program is actually running by typing the 
following

$ ps -ax | grep mysql

For example, if I run the above for postgres (I don't have mysql running to 
demonstrate that), I get

$ps -ax | grep postgres   
61697 ?? 0:00.11 /opt/local/bin/daemondo --label=postgresql91-server 
--start-cmd 
/opt/local/etc/LaunchDaemons/org.macports.postgresql91-server/postgresql91-server.wrapper
 start ; --stop-cmd 
/opt/local/etc/LaunchDaemons/org.macports.postgresql91-server/postgresql91-server.wrapper
 stop ; --restart-cmd 
/opt/local/etc/LaunchDaemons/org.macports.postgresql91-server/postgresql91-server.wrapper
 restart ; --pid=none
62940 ttys0000:00.00 grep postgres


As is visible, it is the postgres version installed by MacPorts that is 
running. MacPorts installs *everything* under /opt/local and nothing anywhere 
else.

The next thing is to figure out which program will launch if you just type it 
on the command line. The easiest way to determine that is to type

$ which program name

For example, with `pg_ctl` I get

$which pg_ctl
/opt/local/lib/postgresql91/bin/pg_ctl 

Also, check your path by typing the following

$echo $PATH


That too will indicate which program will be launched if it were fired without 
explicitly specifying the path.

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

Re: Help with conjoined apaches

2012-04-29 Thread Bradley Giesbrecht


On Apr 28, 2012, at 8:00 PM, Jeremy Lavergne wrote:

 None of these files are provided by MacPorts and files provided by apache2 
 and mysql5 are missing so somehow apache2 and mysql5 were most likely 
 uninstalled by port.
 
 Do you try to do a forced upgrade apache2 and mysql5 that failed? I think 
 that would have uninstalled apache2 and mysql5 before building and 
 installing.
 
 I'd check the code for that one; pretty sure uninstall should never happen 
 until immediately before activate (unless the port itself commands otherwise).

I have done force upgrades several times recently and I seem to recall that the 
active port is force uninstalled before its replacement is built. I was on a 
live server and remembered thinking how unfortunate this is.

Here is a quick test with bash-completion showing uninstall happening first:

$ sudo port clean --all bash-completion
---  Cleaning bash-completion
$ port installed bash-completion
The following ports are currently installed:
  bash-completion @1.3_4
  bash-completion @1.3_5 (active)
$ sudo port -s upgrade --force bash-completion
---  Cleaning bash-completion
---  Unable to uninstall bash-completion @1.3_5, the following ports depend on 
it:
---git-core @1.7.9.2_0+bash_completion+doc+pcre+python27
---git-core 
@1.7.9.4_0+bash_completion+credential_osxkeychain+doc+pcre+python27
---git-core 
@1.7.9.5_0+bash_completion+credential_osxkeychain+doc+pcre+python27
---mercurial @2.1_0+bash_completion
---mercurial @2.1.2_0+bash_completion
---subversion @1.7.3_1+bash_completion
---subversion @1.7.4_0+bash_completion
Warning: Uninstall forced.  Proceeding despite dependencies.
---  Deactivating bash-completion @1.3_5
---  Unable to deactivate bash-completion @1.3_5, the following ports depend 
on it:
---git-core 
@1.7.9.5_0+bash_completion+credential_osxkeychain+doc+pcre+python27
---mercurial @2.1.2_0+bash_completion
---subversion @1.7.4_0+bash_completion
Warning: Deactivate forced.  Proceeding despite dependencies.
---  Cleaning bash-completion
---  Uninstalling bash-completion @1.3_5
---  Cleaning bash-completion
---  Fetching distfiles for bash-completion
---  Attempting to fetch bash-completion-1.3.tar.bz2 from 
http://distfiles.macports.org/bash-completion
---  Verifying checksum(s) for bash-completion
---  Extracting bash-completion
---  Applying patches to bash-completion
---  Configuring bash-completion
---  Building bash-completion
---  Staging bash-completion into destroot
---  Installing bash-completion @1.3_5
---  Activating bash-completion @1.3_5

To use bash_completion, add the following lines at the end of your 
.bash_profile:
  if [ -f /opt/local/etc/bash_completion ]; then
  . /opt/local/etc/bash_completion
  fi

---  Cleaning bash-completion
---  Updating database of binaries: 100.0%
---  Scanning binaries for linking errors: 100.0%
---  No broken files found.



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: mysql problem with socket


On Apr 29, 2012, at 18:22, j...@ayendesigns.com wrote:

 I had checked with 'find', and /opt/locale/etc/mysql5 is the only my.cnf 
 file. I'm not sure that the mysqld process is port's, only that 'which' shows 
 mysql5 being port's. I start it and stop it via the settings panel.

What settings panel? MacPorts MySQL doesn't include any GUI components.


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

RE: mysql problem with socket

Jeez. No idea. Settings has a MySQL, and, I believe, osx doesn't come with mysql... looking at the other message that just came and will check the process

 Original Message 
Subject: Re: mysql problem with socket
From: Ryan Schmidt ryandes...@macports.org
Date: Sun, April 29, 2012 4:30 pm
To: j...@ayendesigns.com
Cc: macports-users@lists.macosforge.org

On Apr 29, 2012, at 18:22, j...@ayendesigns.com wrote:

 I had checked with 'find', and /opt/locale/etc/mysql5 is the only my.cnf file. I'm not sure that the mysqld process is port's, only that 'which' shows mysql5 being port's. I start it and stop it via the settings panel.

What "settings panel"? MacPorts MySQL doesn't include any GUI components.

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

RE: mysql problem with socket

'which' shows nothing for mysqld or mysql, but for mysql5 shows /opt/local...ps reveals  2025 ?? 0:00.24 /opt/local/bin/daemondo --label=mysql5 --start-cmd /opt/local/etc/LaunchDaemons/org.macports.mysql5/mysql5.wrapper start ; --stop-cmd /opt/local/etc/LaunchDaemons/org.macports.mysql5/mysql5.wrapper stop ; --restart-cmd /opt/local/etc/LaunchDaemons/org.macports.mysql5/mysql5.wrapper restart ; --pid=none26834 ?? 0:00.02 /bin/sh /usr/local/mysql/bin/mysqld_safe --datadir=/usr/local/mysql/data --pid-file=/usr/local/mysql/data/MacBook-Pro.local.pid26906 ?? 0:01.38 /usr/local/mysql/bin/mysqld --basedir=/usr/local/mysql --datadir=/usr/local/mysql/data --plugin-dir=/usr/local/mysql/lib/plugin --user=mysql --log-error=/usr/local/mysql/data/MacBook-Pro.local.err --pid-file=/usr/local/mysql/data/MacBook-Pro.local.pid28475 ttys0000:00.00 grep mysql 


 Are you sure the mysql that's being started is the one MacPorts installed, and not the one you installed in /usr/local? How are you starting / stopping mysql?


The above is possibly the commonest mistake, and it is easy to check and correct.

One can easily determine which program is actually running by typing the following

	$ ps -ax | grep mysql

For example, if I run the above for postgres (I don't have mysql running to demonstrate that), I get

	$ps -ax | grep postgres   
61697 ?? 0:00.11 /opt/local/bin/daemondo --label=postgresql91-server --start-cmd /opt/local/etc/LaunchDaemons/org.macports.postgresql91-server/postgresql91-server.wrapper start ; --stop-cmd /opt/local/etc/LaunchDaemons/org.macports.postgresql91-server/postgresql91-server.wrapper stop ; --restart-cmd /opt/local/etc/LaunchDaemons/org.macports.postgresql91-server/postgresql91-server.wrapper restart ; --pid=none
62940 ttys0000:00.00 grep postgres


As is visible, it is the postgres version installed by MacPorts that is running. MacPorts installs *everything* under /opt/local and nothing anywhere else.

The next thing is to figure out which program will launch if you just type it on the command line. The easiest way to determine that is to type

	$ which program name

For example, with `pg_ctl` I get

	$which pg_ctl
	/opt/local/lib/postgresql91/bin/pg_ctl 

Also, check your path by typing the following

	$echo $PATH


That too will indicate which program will be launched if it were fired without explicitly specifying the path.

--
Puneet Kishor
___
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: mysql problem with socket

Yup, you are running the mysql version *not* installed by MacPorts. If you look 
below, you are running `/usr/local/mysql/bin/mysqld` which either you knowingly 
installed, or was installed by some other program without you realizing.

The reason `which mysqld` shows nothing is because /opt/local/lib/mysql5/bin is 
not in your path.

You should not start mysql via the Control Panel. That was not installed by 
MacPorts, and starting that is causing the issues that you are facing.


On Apr 29, 2012, at 6:40 PM, j...@ayendesigns.com wrote:

 'which' shows nothing for mysqld or mysql, but for mysql5 shows /opt/local...
 
 ps reveals 
 
 2025 ?? 0:00.24 /opt/local/bin/daemondo --label=mysql5 --start-cmd 
 /opt/local/etc/LaunchDaemons/org.macports.mysql5/mysql5.wrapper start ; 
 --stop-cmd /opt/local/etc/LaunchDaemons/org.macports.mysql5/mysql5.wrapper 
 stop ; --restart-cmd 
 /opt/local/etc/LaunchDaemons/org.macports.mysql5/mysql5.wrapper restart ; 
 --pid=none
 26834 ?? 0:00.02 /bin/sh /usr/local/mysql/bin/mysqld_safe 
 --datadir=/usr/local/mysql/data 
 --pid-file=/usr/local/mysql/data/MacBook-Pro.local.pid
 26906 ?? 0:01.38 /usr/local/mysql/bin/mysqld --basedir=/usr/local/mysql 
 --datadir=/usr/local/mysql/data --plugin-dir=/usr/local/mysql/lib/plugin 
 --user=mysql --log-error=/usr/local/mysql/data/MacBook-Pro.local.err 
 --pid-file=/usr/local/mysql/data/MacBook-Pro.local.pid
 28475 ttys000 0:00.00 grep mysql
 
  Are you sure the mysql that's being started is the one MacPorts installed, 
  and not the one you installed in /usr/local? How are you starting / 
  stopping mysql?
 
 
 The above is possibly the commonest mistake, and it is easy to check and 
 correct.
 
 One can easily determine which program is actually running by typing the 
 following
 
 $ ps -ax | grep mysql
 
 For example, if I run the above for postgres (I don't have mysql running to 
 demonstrate that), I get
 
 $ps -ax | grep postgres 
 61697 ?? 0:00.11 /opt/local/bin/daemondo --label=postgresql91-server 
 --start-cmd 
 /opt/local/etc/LaunchDaemons/org.macports.postgresql91-server/postgresql91-server.wrapper
  start ; --stop-cmd 
 /opt/local/etc/LaunchDaemons/org.macports.postgresql91-server/postgresql91-server.wrapper
  stop ; --restart-cmd 
 /opt/local/etc/LaunchDaemons/org.macports.postgresql91-server/postgresql91-server.wrapper
  restart ; --pid=none
 62940 ttys000 0:00.00 grep postgres
 
 
 As is visible, it is the postgres version installed by MacPorts that is 
 running. MacPorts installs *everything* under /opt/local and nothing anywhere 
 else.
 
 The next thing is to figure out which program will launch if you just type it 
 on the command line. The easiest way to determine that is to type
 
 $ which program name
 
 For example, with `pg_ctl` I get
 
 $which pg_ctl
 /opt/local/lib/postgresql91/bin/pg_ctl 
 
 Also, check your path by typing the following
 
 $echo $PATH
 
 
 That too will indicate which program will be launched if it were fired 
 without explicitly specifying the path.
 
 --
 Puneet Kishor
 ___
 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

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

Re: mysql problem with socket

2012-04-29 Thread Jeff Greenberg

I'll edit $PATH. What is the proper way to start it?

Sent from my iPhone

On Apr 29, 2012, at 7:50 PM, Mr. Puneet Kishor punk.k...@gmail.com wrote:

 Yup, you are running the mysql version *not* installed by MacPorts. If you 
 look below, you are running `/usr/local/mysql/bin/mysqld` which either you 
 knowingly installed, or was installed by some other program without you 
 realizing.
 
 The reason `which mysqld` shows nothing is because /opt/local/lib/mysql5/bin 
 is not in your path.
 
 You should not start mysql via the Control Panel. That was not installed by 
 MacPorts, and starting that is causing the issues that you are facing.
 
 
 On Apr 29, 2012, at 6:40 PM, j...@ayendesigns.com wrote:
 
 'which' shows nothing for mysqld or mysql, but for mysql5 shows /opt/local...
 
 ps reveals 
 
 2025 ?? 0:00.24 /opt/local/bin/daemondo --label=mysql5 --start-cmd 
 /opt/local/etc/LaunchDaemons/org.macports.mysql5/mysql5.wrapper start ; 
 --stop-cmd /opt/local/etc/LaunchDaemons/org.macports.mysql5/mysql5.wrapper 
 stop ; --restart-cmd 
 /opt/local/etc/LaunchDaemons/org.macports.mysql5/mysql5.wrapper restart ; 
 --pid=none
 26834 ?? 0:00.02 /bin/sh /usr/local/mysql/bin/mysqld_safe 
 --datadir=/usr/local/mysql/data 
 --pid-file=/usr/local/mysql/data/MacBook-Pro.local.pid
 26906 ?? 0:01.38 /usr/local/mysql/bin/mysqld --basedir=/usr/local/mysql 
 --datadir=/usr/local/mysql/data --plugin-dir=/usr/local/mysql/lib/plugin 
 --user=mysql --log-error=/usr/local/mysql/data/MacBook-Pro.local.err 
 --pid-file=/usr/local/mysql/data/MacBook-Pro.local.pid
 28475 ttys000 0:00.00 grep mysql
 
 Are you sure the mysql that's being started is the one MacPorts installed, 
 and not the one you installed in /usr/local? How are you starting / 
 stopping mysql?
 
 
 The above is possibly the commonest mistake, and it is easy to check and 
 correct.
 
 One can easily determine which program is actually running by typing the 
 following
 
 $ ps -ax | grep mysql
 
 For example, if I run the above for postgres (I don't have mysql running to 
 demonstrate that), I get
 
 $ps -ax | grep postgres 
 61697 ?? 0:00.11 /opt/local/bin/daemondo --label=postgresql91-server 
 --start-cmd 
 /opt/local/etc/LaunchDaemons/org.macports.postgresql91-server/postgresql91-server.wrapper
  start ; --stop-cmd 
 /opt/local/etc/LaunchDaemons/org.macports.postgresql91-server/postgresql91-server.wrapper
  stop ; --restart-cmd 
 /opt/local/etc/LaunchDaemons/org.macports.postgresql91-server/postgresql91-server.wrapper
  restart ; --pid=none
 62940 ttys000 0:00.00 grep postgres
 
 
 As is visible, it is the postgres version installed by MacPorts that is 
 running. MacPorts installs *everything* under /opt/local and nothing 
 anywhere else.
 
 The next thing is to figure out which program will launch if you just type 
 it on the command line. The easiest way to determine that is to type
 
 $ which program name
 
 For example, with `pg_ctl` I get
 
 $which pg_ctl
 /opt/local/lib/postgresql91/bin/pg_ctl 
 
 Also, check your path by typing the following
 
 $echo $PATH
 
 
 That too will indicate which program will be launched if it were fired 
 without explicitly specifying the path.
 
 --
 Puneet Kishor
 ___
 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
 
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Re: mysql problem with socket


On Apr 29, 2012, at 7:47 PM, j...@ayendesigns.com wrote:

 There is no mysqld in that directory ... there are mysqld_multi and 
 mysqld_safe, but with that path added to $PATH 'which' still comes up empty
 


Ah... well, mysqld_safe is just a safe version of starting the mysql 
daemon. So, the only issue is that you somehow have mysql installed under 
/usr/local (dunno how it got there, but you must have installed it somehow 
without realizing), and also one installed under /opt/local (installed by 
macports).

So, you just want the one from macports to start up.

First, make sure the one under /usr/local is turned off. You can do so via 
System Preferences. Once you turn it off, make sure it is really off by looking 
in the Activity Monitor (you can filter by 'mysql') which is really just a gui 
front-end to ps.

Then, make sure /opt/local/lib/mysql5/bin is in your path. You can set the path 
variable in .bashrc or .bash_profile (which is usually called by .bashrc). Once 
you set that, you can either quit Terminal and start it again, or just type 
`source ~/.bash_profile` to make sure the new setting of path takes effect.

Then, start macport's mysql by typing `sudo port load name of the port` (I 
don't know the exact name of the mysql port installed by macport.

Check again that mysql is running. If it is not, then mysql didn't start 
because of some other reason. Check the logs to figure out why.

Yes, all this is frustrating and mysterious for us who are not so versed in all 
this, but the good thing is that you have to figure this out only once. Once 
you figure it out, one, you know how forever, and two, you never have to worry 
about it.



 
 The reason `which mysqld` shows nothing is because /opt/local/lib/mysql5/bin 
 is not in your path.
 
 ___
 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

R and R-framework

On my iMac I installed both ports successfully as a precursor to installing 
PL/R by hand (PL/R is not available in MacPorts).

$sudo port install R
$sudo port install R-framework


On my MBA (same operating system), the second command failed with the following 
message

$sudo port install R
..
---  Staging R into destroot
---  Installing R @2.15.0_0+gcc45+recommended
---  Activating R @2.15.0_0+gcc45+recommended
---  Cleaning R
$sudo port install R-framework
---  Computing dependencies for R-framework
Error: Unable to execute port: Can't install R-framework because 
conflicting ports are installed: R
To report a bug, see http://guide.macports.org/#project.tickets


Gak! How do I debug this?




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

Re: R and R-framework


On Apr 29, 2012, at 21:41, Mr. Puneet Kishor wrote:

 On my iMac I installed both ports successfully as a precursor to installing 
 PL/R by hand (PL/R is not available in MacPorts).
 
   $sudo port install R
   $sudo port install R-framework
 
 
 On my MBA (same operating system), the second command failed with the 
 following message
 
   $sudo port install R
   ..
   ---  Staging R into destroot
   ---  Installing R @2.15.0_0+gcc45+recommended
   ---  Activating R @2.15.0_0+gcc45+recommended
   ---  Cleaning R
   $sudo port install R-framework
   ---  Computing dependencies for R-framework
   Error: Unable to execute port: Can't install R-framework because 
 conflicting ports are installed: R
   To report a bug, see http://guide.macports.org/#project.tickets
 
 
 Gak! How do I debug this?

The ports conflict. You're not supposed to be able to install both at the same 
time. Pick one or the other.



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

Re: mysql problem with socket