Re: Can't connect to local MySQL server error

2012-08-05 Thread Ryan Schmidt

On Aug 5, 2012, at 02:05, Rodolfo Aramayo raram...@gmail.com wrote:

 I have followed the instructions outlined in the document:
 
 https://trac.macports.org/wiki/howto/MAMP
 
 And I can see my test web site and the output of phpinfo.php but I am
 consistently getting the following error:
 
 ERROR 2002 (HY000): Can't connect to local MySQL server through socket
 '/opt/local/var/run/mysql5/mysqld.sock' (2)
 
 which I have tried to correct unsuccessfully. Both mysql and php are
 pointing to the same directory: /opt/local/var/run/mysql5/

You are trying to start the MySQL server provided by the mysql5 / mysql5-server 
ports, yes?

Is the server running? that is, is the mysqld process running, as seen using 
ps or Activity Monitor?

If not, does the MySQL log file say anything about why that is?


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


Re: some port was nice enough to remove TeX w/o my permission

2012-08-05 Thread Ryan Schmidt
Let us keep this discussion on the mailing list so all can benefit from it. Use 
Reply All when you reply.


On Aug 4, 2012, at 17:13, Damon McDougall wrote:

 This happened to me too!
 
 I really don't think so… *installing* a port should not *uninstall* any 
 other ports. *Upgrading* a port *could* uninstall old versions of 
 dependencies, *if* you used the -u flag when upgrading to indicate that 
 you wanted that to happen.
 
 Is there a way to say, update this port and remove the previous version
 of it

sudo port -u upgrade whatever

It will remove the previously active version of this port, and its 
dependencies, if any of its dependencies were also in need of upgrade.

 but don't uninstall outdated dependencies, presumably because
 other ports might also use these dependencies?

If dependencies are outdated, they must be upgraded first.

If this breaks other ports, then probably those other ports need to be rebuilt 
as well. If those other ports don't already show up in the output of port 
outdated and you've already run sudo port selfupdate, then this is probably 
a bug that you should file a bug report about.



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


Re: some port was nice enough to remove TeX w/o my permission

2012-08-05 Thread Ryan Schmidt

On Aug 4, 2012, at 17:07, Jeremy Lavergne jer...@lavergne.gotdns.org wrote:

 I really don't think so… *installing* a port should not *uninstall* any 
 other ports. *Upgrading* a port *could* uninstall old versions of 
 dependencies, *if* you used the -u flag when upgrading to indicate that 
 you wanted that to happen.
 
 For most users, uninstall and deactivate are effectively the same thing. 

Sure, I wasn't trying to make a distinction about that. I was trying to say 
that installing a port should not uninstall (or deactivate) another port. But 
below you've found an exception to that:


 With that in mind, I know in some packages are deactivated during an install 
 because a given files may be installed by a different package in separate 
 versions of the package. If you don't remove the other package first, you'll 
 run into an error where a file is already installed by another package.
 
 This happens in various category:textproc and category:kde4 packages (pdfjam 
 comes to mind as one that uninstalls texlive-bin-extra).

Ah yes. pdfjam does use the so-called deactivate hack, an unusual situation 
which does leave another port deactivated. As the comment in the port explains:

# texlive-bin-extra used to contain pdfjam, but doesn't
# anymore. If the old version is installed, deactivate it to avoid
# a conflict.

So, if you had an old version of texlive-bin-extra installed (one that provided 
pdfjam), and then you try to install the standalone pdfjam port, it will 
deactivate your old texlive-bin-extra for you to avoid a conflict that you 
would then manually have to resolve. You will also have to upgrade 
texlive-bin-extra to the newer version that does not provide its own copy of 
pdfjam anymore. Often, people run sudo port upgrade outdated, to upgrade all 
outdated ports at once, which should avoid any problems. 

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


Re: Can't connect to local MySQL server error

2012-08-05 Thread Rodolfo Aramayo
Answers below...

On Sun, Aug 5, 2012 at 3:17 AM, Ryan Schmidt ryandes...@macports.org wrote:

 On Aug 5, 2012, at 02:05, Rodolfo Aramayo raram...@gmail.com wrote:

 I have followed the instructions outlined in the document:

 https://trac.macports.org/wiki/howto/MAMP

 And I can see my test web site and the output of phpinfo.php but I am
 consistently getting the following error:

 ERROR 2002 (HY000): Can't connect to local MySQL server through socket
 '/opt/local/var/run/mysql5/mysqld.sock' (2)

 which I have tried to correct unsuccessfully. Both mysql and php are
 pointing to the same directory: /opt/local/var/run/mysql5/

 You are trying to start the MySQL server provided by the mysql5 / 
 mysql5-server ports, yes?

Yes


 Is the server running? that is, is the mysqld process running, as seen using 
 ps or Activity Monitor?

Yes

 If not, does the MySQL log file say anything about why that is?

No socket was being created.

Now I had a weird experience:

I had installed:
mysql55
mysql55-server
mysql_select

In addition to the
mysql5 and
mysql55-server

I wasn't detecting this because the way port search was acting

For example if I now search, I get:

port installed *mysql*
None of the specified ports are installed.

port installed *mysql
The following ports are currently installed:
  p5.12-class-dbi-mysql @1.0.0_3 (active)
  p5.12-datetime-format-mysql @0.40.0_3 (active)
  p5.12-dbd-mysql @4.20.0_1+mysql5 (active)
  php5-mysql @5.3.15_0+mysqlnd (active)

port installed mysql*
None of the specified ports are installed.

port installed mysql
None of the specified ports are installed.

 port installed | grep mysql
  mysql5 @5.1.63_0 (active)
  mysql5-server @5.1.63_0 (active)
  p5.12-class-dbi-mysql @1.0.0_3 (active)
  p5.12-datetime-format-mysql @0.40.0_3 (active)
  p5.12-dbd-mysql @4.20.0_1+mysql5 (active)
  php5-mysql @5.3.15_0+mysqlnd (active)

Note how this last one search is more complete
I was using the command port installed *mysql* before thus failing
to detect that I had installed extra mysql ports

I uninstalled mysql55, mysql55-server, mysql_ select AND uninstalled
mysql5-server
I then re-installed mysql5-server, re-booted and got the socket live

But for a while I was under the impression the presence of the other
mysql ports was interfering with the generation of the socket??

So things are working now

I need to learn where to place my wordpress (which is not up-to-date
in MacPorts) and mantis installations now and learn where the mysql
databases live inside the ports system which is something I was very
familiar using the Apple standard system. Importantly I need to learn
how not to kill the databases during upgrades

THANKS

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


Re: Can't connect to local MySQL server error

2012-08-05 Thread Robson Roberto Souza Peixoto
On Sun, Aug 5, 2012 at 5:49 AM, Rodolfo Aramayo raram...@gmail.com wrote:
 Answers below...

 On Sun, Aug 5, 2012 at 3:17 AM, Ryan Schmidt ryandes...@macports.org wrote:

 On Aug 5, 2012, at 02:05, Rodolfo Aramayo raram...@gmail.com wrote:

 I have followed the instructions outlined in the document:

 https://trac.macports.org/wiki/howto/MAMP

 And I can see my test web site and the output of phpinfo.php but I am
 consistently getting the following error:

 ERROR 2002 (HY000): Can't connect to local MySQL server through socket
 '/opt/local/var/run/mysql5/mysqld.sock' (2)

 which I have tried to correct unsuccessfully. Both mysql and php are
 pointing to the same directory: /opt/local/var/run/mysql5/

 You are trying to start the MySQL server provided by the mysql5 / 
 mysql5-server ports, yes?

 Yes


 Is the server running? that is, is the mysqld process running, as seen using 
 ps or Activity Monitor?

 Yes

 If not, does the MySQL log file say anything about why that is?

 No socket was being created.

Check if the /tmp/mysql.sock was being created.


 Now I had a weird experience:

 I had installed:
 mysql55
 mysql55-server
 mysql_select

 In addition to the
 mysql5 and
 mysql55-server

 I wasn't detecting this because the way port search was acting

 For example if I now search, I get:

port installed *mysql*
 None of the specified ports are installed.

port installed *mysql
 The following ports are currently installed:
   p5.12-class-dbi-mysql @1.0.0_3 (active)
   p5.12-datetime-format-mysql @0.40.0_3 (active)
   p5.12-dbd-mysql @4.20.0_1+mysql5 (active)
   php5-mysql @5.3.15_0+mysqlnd (active)

port installed mysql*
 None of the specified ports are installed.

port installed mysql
 None of the specified ports are installed.

 port installed | grep mysql
   mysql5 @5.1.63_0 (active)
   mysql5-server @5.1.63_0 (active)
   p5.12-class-dbi-mysql @1.0.0_3 (active)
   p5.12-datetime-format-mysql @0.40.0_3 (active)
   p5.12-dbd-mysql @4.20.0_1+mysql5 (active)
   php5-mysql @5.3.15_0+mysqlnd (active)

 Note how this last one search is more complete
 I was using the command port installed *mysql* before thus failing
 to detect that I had installed extra mysql ports

 I uninstalled mysql55, mysql55-server, mysql_ select AND uninstalled
 mysql5-server
 I then re-installed mysql5-server, re-booted and got the socket live

 But for a while I was under the impression the presence of the other
 mysql ports was interfering with the generation of the socket??

 So things are working now

 I need to learn where to place my wordpress (which is not up-to-date
 in MacPorts) and mantis installations now and learn where the mysql
 databases live inside the ports system which is something I was very
 familiar using the Apple standard system. Importantly I need to learn
 how not to kill the databases during upgrades

 THANKS

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



-- 
Robson Roberto Souza Peixoto
Robinho
Master in Computer Science, University of Campinas
Linux Counter #395633
IRC: robsonpeixoto
Twitter: http://twitter.com/rrspba
github: https://github.com/robsonpeixoto
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users


Re: Can't connect to local MySQL server error

2012-08-05 Thread Ryan Schmidt

On Aug 5, 2012, at 03:49, Rodolfo Aramayo wrote:

 On Sun, Aug 5, 2012 at 3:17 AM, Ryan Schmidt wrote:
 
 Is the server running? that is, is the mysqld process running, as seen using 
 ps or Activity Monitor?
 
 Yes
 
 If not, does the MySQL log file say anything about why that is?
 
 No socket was being created.

I gathered that… did it say why no socket was being created?


 Now I had a weird experience:
 
 I had installed:
 mysql55
 mysql55-server
 mysql_select
 
 In addition to the
 mysql5 and
 mysql55-server
 
 I wasn't detecting this because the way port search was acting
 
 For example if I now search, I get:
 
 port installed *mysql*
 None of the specified ports are installed.
 
 port installed *mysql
 The following ports are currently installed:
  p5.12-class-dbi-mysql @1.0.0_3 (active)
  p5.12-datetime-format-mysql @0.40.0_3 (active)
  p5.12-dbd-mysql @4.20.0_1+mysql5 (active)
  php5-mysql @5.3.15_0+mysqlnd (active)
 
 port installed mysql*
 None of the specified ports are installed.

Understand that the *shell* will expand these glob patterns if possible, before 
running MacPorts. So if you have an item named, say, mysqlstuff in the 
current directory, then port installed mysql* will be expanded by the shell 
to port installed mysqlstuff before MacPorts ever has a chance to see the 
command. Only if the glob doesn't match something in the current directory 
would the shell pass port installed mysql*' to MacPorts. If you do not want 
the shell to expand the glob, quote the argument, as in port installed 
'mysql*'. Alternately you can use port installed name:mysql which is similar 
to port installed '*mysql*'. The port installed '*mysql*' syntax uses 
globs, whereas the port installed name:mysql syntax uses Perl-compatible 
regular expressions.


 port installed mysql
 None of the specified ports are installed.

This is not unexpected; there is no port called mysql so it cannot be 
installed. Globs are by default anchored on both ends so you must add asterisks 
where you want arbitrary characters to be matched. PCREs on the other hand are 
unanchored by default and you must anchor them if desired.

By example:

# Installed port whose name is mysql:
port installed name:^mysql$
port installed mysql

# Installed ports whose names begin with mysql:
port installed name:^mysql
port installed 'mysql*'

# Installed ports whose names end with mysql:
port installed name:mysql$
port installed '*mysql'

# Installed ports whose names contain mysql:
port installed name:mysql
port installed '*mysql*'
port installed | grep mysql


 port installed | grep mysql
  mysql5 @5.1.63_0 (active)
  mysql5-server @5.1.63_0 (active)
  p5.12-class-dbi-mysql @1.0.0_3 (active)
  p5.12-datetime-format-mysql @0.40.0_3 (active)
  p5.12-dbd-mysql @4.20.0_1+mysql5 (active)
  php5-mysql @5.3.15_0+mysqlnd (active)
 
 Note how this last one search is more complete
 I was using the command port installed *mysql* before thus failing
 to detect that I had installed extra mysql ports

Using grep is also reasonable, if you're more comfortable with that. grep by 
default uses old-style regular expressions, and can be made to use PCREs with 
the -E flag.


 I uninstalled mysql55, mysql55-server, mysql_ select AND uninstalled
 mysql5-server
 I then re-installed mysql5-server, re-booted and got the socket live
 
 But for a while I was under the impression the presence of the other
 mysql ports was interfering with the generation of the socket??

My understanding is that the new mysql55 and mysql51 families of ports should 
not interfere with one another nor with the old mysql5 family of ports.


 So things are working now

I'm glad you got it working, though I can't explain why it didn't work for you 
before.


 I need to learn where to place my wordpress (which is not up-to-date
 in MacPorts)

Feel free to attach a patch to this ticket to update the port:

https://trac.macports.org/ticket/32778

The port's current maintainer appears to have left us (has not responded to 
multiple tickets and has not committed in 11 months) so if you're interested 
perhaps you could take over the wordpress port.


 and mantis installations now

I used to use Mantis but haven't in many years and we don't seem to have a port 
for it. If you'd like to contribute one please do.


 and learn where the mysql
 databases live inside the ports system

/opt/local/var/db/$MYSQL

where $MYSQL is mysql5, mysql51, mysql55, percona or mariadb depending on which 
MySQL port you're using. Or you can change the data directory as desired by 
editing your my.cnf. I may be weird but on my development machine I keep my 
databases in $HOME/mysql/data.


 which is something I was very
 familiar using the Apple standard system. Importantly I need to learn
 how not to kill the databases during upgrades

The databases are not registered to any port so MacPorts will not touch them 
when you upgrade ports nor ever uninstall them.

When you upgrade MySQL, you may manually need to manually 

Re: Can't connect to local MySQL server error

2012-08-05 Thread Brandon Allbery
On Sun, Aug 5, 2012 at 4:49 AM, Rodolfo Aramayo raram...@gmail.com wrote:

 port installed *mysql*
 None of the specified ports are installed.


If you have any filenames in the current directory containing the string
mysql (probably starting with, from your examples) then those filenames
will be passed to the port command.  *The port command has no control
whatsoever over this; it is basic shell behavior that cannot be overridden.*

You should get into the habit of always quoting any metacharacters you
don't want the shell to expand.  These are:  $ * ? [ { '  \ and leading ~.
 SIngle quotes prevent all expansion including the quoting behavior of \ ;
\ quotes any single character, except when in a single-quoted string.

-- 
brandon s allbery  allber...@gmail.com
wandering unix systems administrator (available) (412) 475-9364 vm/sms
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users


compiled ports in german

2012-08-05 Thread Leon Rosenberg
Hello,

after I reinstalled macports under mountain lion and reinstalled first
ports (subversion) I saw that they are in german :-(
I do live in germany, but by macosx runs in english as any other
program i have on my mac.
A short search in google and macports tickets didn't offer any help,
how can I switch the language of ports to something normal aka
english?

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


Re: compiled ports in german

2012-08-05 Thread Lawrence Velázquez
On Aug 5, 2012, at 11:10 a.m., Leon Rosenberg wrote:

 after I reinstalled macports under mountain lion and reinstalled first
 ports (subversion) I saw that they are in german :-(
 I do live in germany, but by macosx runs in english as any other
 program i have on my mac.
 A short search in google and macports tickets didn't offer any help,
 how can I switch the language of ports to something normal aka
 english?

Do you set LANG or any of the LC_* environment variables to a German locale? 
Try setting LANG to en_US.UTF-8 or something similar.

http://lists.macosforge.org/pipermail/macports-users/2012-July/029944.html


vq

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


Re: compiled ports in german

2012-08-05 Thread Leon Rosenberg
Thank you,
export LANG=en_US.UTF-8
did the trick.

Leon

On Sun, Aug 5, 2012 at 5:47 PM, Lawrence Velázquez
larry.velazq...@gmail.com wrote:
 On Aug 5, 2012, at 11:10 a.m., Leon Rosenberg wrote:

 after I reinstalled macports under mountain lion and reinstalled first
 ports (subversion) I saw that they are in german :-(
 I do live in germany, but by macosx runs in english as any other
 program i have on my mac.
 A short search in google and macports tickets didn't offer any help,
 how can I switch the language of ports to something normal aka
 english?

 Do you set LANG or any of the LC_* environment variables to a German locale? 
 Try setting LANG to en_US.UTF-8 or something similar.

 http://lists.macosforge.org/pipermail/macports-users/2012-July/029944.html


 vq

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


Re: Can't connect to local MySQL server error

2012-08-05 Thread Rodolfo Aramayo
On Sun, Aug 5, 2012 at 5:53 AM, Ryan Schmidt ryandes...@macports.org wrote:

 On Aug 5, 2012, at 03:49, Rodolfo Aramayo wrote:

 On Sun, Aug 5, 2012 at 3:17 AM, Ryan Schmidt wrote:

 Is the server running? that is, is the mysqld process running, as seen 
 using ps or Activity Monitor?

 Yes

 If not, does the MySQL log file say anything about why that is?

 No socket was being created.

 I gathered that… did it say why no socket was being created?


 Now I had a weird experience:

 I had installed:
 mysql55
 mysql55-server
 mysql_select

 In addition to the
 mysql5 and
 mysql55-server

 I wasn't detecting this because the way port search was acting

 For example if I now search, I get:

 port installed *mysql*
 None of the specified ports are installed.

 port installed *mysql
 The following ports are currently installed:
  p5.12-class-dbi-mysql @1.0.0_3 (active)
  p5.12-datetime-format-mysql @0.40.0_3 (active)
  p5.12-dbd-mysql @4.20.0_1+mysql5 (active)
  php5-mysql @5.3.15_0+mysqlnd (active)

 port installed mysql*
 None of the specified ports are installed.

 Understand that the *shell* will expand these glob patterns if possible, 
 before running MacPorts. So if you have an item named, say, mysqlstuff in 
 the current directory, then port installed mysql* will be expanded by the 
 shell to port installed mysqlstuff before MacPorts ever has a chance to see 
 the command. Only if the glob doesn't match something in the current 
 directory would the shell pass port installed mysql*' to MacPorts. If you do 
 not want the shell to expand the glob, quote the argument, as in port 
 installed 'mysql*'. Alternately you can use port installed name:mysql which 
 is similar to port installed '*mysql*'. The port installed '*mysql*' 
 syntax uses globs, whereas the port installed name:mysql syntax uses 
 Perl-compatible regular expressions.


 port installed mysql
 None of the specified ports are installed.

 This is not unexpected; there is no port called mysql so it cannot be 
 installed. Globs are by default anchored on both ends so you must add 
 asterisks where you want arbitrary characters to be matched. PCREs on the 
 other hand are unanchored by default and you must anchor them if desired.

 By example:

 # Installed port whose name is mysql:
 port installed name:^mysql$
 port installed mysql

 # Installed ports whose names begin with mysql:
 port installed name:^mysql
 port installed 'mysql*'

 # Installed ports whose names end with mysql:
 port installed name:mysql$
 port installed '*mysql'

 # Installed ports whose names contain mysql:
 port installed name:mysql
 port installed '*mysql*'
 port installed | grep mysql


 port installed | grep mysql
  mysql5 @5.1.63_0 (active)
  mysql5-server @5.1.63_0 (active)
  p5.12-class-dbi-mysql @1.0.0_3 (active)
  p5.12-datetime-format-mysql @0.40.0_3 (active)
  p5.12-dbd-mysql @4.20.0_1+mysql5 (active)
  php5-mysql @5.3.15_0+mysqlnd (active)

 Note how this last one search is more complete
 I was using the command port installed *mysql* before thus failing
 to detect that I had installed extra mysql ports

 Using grep is also reasonable, if you're more comfortable with that. grep by 
 default uses old-style regular expressions, and can be made to use PCREs with 
 the -E flag.

Thanks Ryan, this explanation make things very clear in my mind now.
I  learned a lot...



 I uninstalled mysql55, mysql55-server, mysql_ select AND uninstalled
 mysql5-server
 I then re-installed mysql5-server, re-booted and got the socket live

 But for a while I was under the impression the presence of the other
 mysql ports was interfering with the generation of the socket??

 My understanding is that the new mysql55 and mysql51 families of ports should 
 not interfere with one another nor with the old mysql5 family of ports.

That was my original thought as well...
If Iwanted to get mysql55 working, replacing mysql5, and talking to
apache2 and php5, how should I proceed?
Also, what is the procedure to use php54 instead of php53?
Can more than one mysql be talking to php and to phpmyadmin at the same time?



 So things are working now

 I'm glad you got it working, though I can't explain why it didn't work for 
 you before.

What can I say...the ghost in the machine??



 I need to learn where to place my wordpress (which is not up-to-date
 in MacPorts)

 Feel free to attach a patch to this ticket to update the port:

 https://trac.macports.org/ticket/32778

 The port's current maintainer appears to have left us (has not responded to 
 multiple tickets and has not committed in 11 months) so if you're interested 
 perhaps you could take over the wordpress port.

I would be more than glad to do that but I would need some initial
coaching on how to create a port first...



 and mantis installations now

 I used to use Mantis but haven't in many years and we don't seem to have a 
 port for it. If you'd like to contribute one please do.

Same here...I really would need to understand how to  

Avidemux -- What is happening

2012-08-05 Thread Michael_google gmail_Gersten
What is the status of Avidemux?

There are a number of people complaining that it won't build; I did
not add to that.

There is a ticket calling for it to be updated, but it is not.

There is a binary for an older version available from download at
http://avidemux.sourceforge.net/download.html, but that is an out of
date version. It talks about how to use a different package manager to
compile, but that one uses /usr/local (which is a disaster waiting for
MacPorts).

There's info on the web saying that you can get a working binary of
Avidemux on 10.7 by taking avidemux2.app, removing the included
libraries that do not work on 10.7, and letting the system's version
of those libraries be used -- but I can't find an up to date version
of avidemux2.app to do that trick with.

Halp! Pwease! I'm ... past frustrated and giving up.

-- 
Political and economic blog of a strict constitutionalist
http://StrictConstitution.BlogSpot.com

This message may have been spell checked by a laptop kitten.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users