Re: mysql5 and mysql51
On May 4, 2012, at 7:24 PM, Bradley Giesbrecht wrote:
On May 4, 2012, at 6:53 PM, Ryan Schmidt wrote:
On May 4, 2012, at 20:13, Terry Barnum wrote:
The mysql variants for postfix are mysql51 or mysql55. I installed postfix
+mysql51 which installed mysql5.1.62_1. Dovecot variants are mysql5 and
mysql55. Installing dovecot2 +mysql5 which is installing mysql5.1.62_0.
port installed shows:
mysql5 @5.1.62_0 (active)
mysql51 @5.1.62_1 (active)
What's the correct way to solve this?
We need to update all ports that use mysql to have mysql51 and mysql55
variants, and then deprecate the mysql5 port. This is an ongoing process.
Yes, it would be better to leave all the mysql5 variants in place until we
can make the change in mass.
Terry, what ports do you have installed that depend on mysql?
$ port dependents mysql5
dovecot depends on mysql5
dovecot2 depends on mysql5
p5-dbd-mysql depends on mysql5
p5.12-dbd-mysql depends on mysql5
postfix depends on mysql5
Switching to mysql51 for both dovecot2 and postfix should be a small change.
You might have to tell dovecot and postfix where to find the mysql51 socket
and you will probably need to tell mysql51 where your databases are.
The default location for datadir is /opt/local/var/db/{msyql5,mysql51}.
Personally I use a different directory which I set in
/opt/local/etc/{mysql5,mysql51}/my.cnf.
In my.cnf if you set the socket and datadir locations to the same as mysql5
everything should just work.
You can probably get away with installing mysql51 and coping your mysql5
my.cnf file over mysql55's my.cnf file.
$ sudo cp /opt/local/etc/{mysql5,mysql51}/my.cnf
And then look through the new my.cnf for any paths you may want to adjust.
Then stop mysql5 and start mysql55.
$ sudo port unload mysql5
$ sudo port load mysql51
Thank you Bradley, I'll give it a shot.
-Terry
Regards,
Bradley Giesbrecht (pixilla)
Terry Barnum
digital OutPost
http://www.dop.com
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: mysql5 and mysql51
On May 4, 2012, at 10:55 PM, Bjarne D Mathiesen wrote: Ryan Schmidt wrote: On May 4, 2012, at 20:13, Terry Barnum wrote: The mysql variants for postfix are mysql51 or mysql55. I installed postfix +mysql51 which installed mysql5.1.62_1. Dovecot variants are mysql5 and mysql55. Installing dovecot2 +mysql5 which is installing mysql5.1.62_0. port installed shows: mysql5 @5.1.62_0 (active) mysql51 @5.1.62_1 (active) What's the correct way to solve this? We need to update all ports that use mysql to have mysql51 and mysql55 variants, and then deprecate the mysql5 port. This is an ongoing process. I guess I'm partly to blame for that mess as I supplied the foundation patches for both dovecot2 postfix :-( The attached patch-Portfile.diff ought to bring dovecot2 postfix level in mysql versions ;-) No worries Bjarne. Thank you very much for helping to maintain these ports! -Terry 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 patch-Portfile.diff Terry Barnum digital OutPost http://www.dop.com ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: mysql5 and mysql51
Bjarne D Mathiesen wrote: The attached patch-Portfile.diff ought to bring dovecot2 postfix level in mysql versions ;-) I've noticed that the patch has been applied now :-) -- 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: mysql5 and mysql51
On May 7, 2012, at 9:52 AM, Terry Barnum wrote:
On May 4, 2012, at 7:24 PM, Bradley Giesbrecht wrote:
On May 4, 2012, at 6:53 PM, Ryan Schmidt wrote:
On May 4, 2012, at 20:13, Terry Barnum wrote:
The mysql variants for postfix are mysql51 or mysql55. I installed postfix
+mysql51 which installed mysql5.1.62_1. Dovecot variants are mysql5 and
mysql55. Installing dovecot2 +mysql5 which is installing mysql5.1.62_0.
port installed shows:
mysql5 @5.1.62_0 (active)
mysql51 @5.1.62_1 (active)
What's the correct way to solve this?
We need to update all ports that use mysql to have mysql51 and mysql55
variants, and then deprecate the mysql5 port. This is an ongoing process.
Yes, it would be better to leave all the mysql5 variants in place until we
can make the change in mass.
Terry, what ports do you have installed that depend on mysql?
$ port dependents mysql5
dovecot depends on mysql5
dovecot2 depends on mysql5
p5-dbd-mysql depends on mysql5
p5.12-dbd-mysql depends on mysql5
postfix depends on mysql5
Switching to mysql51 for both dovecot2 and postfix should be a small change.
You might have to tell dovecot and postfix where to find the mysql51 socket
and you will probably need to tell mysql51 where your databases are.
The default location for datadir is /opt/local/var/db/{msyql5,mysql51}.
Personally I use a different directory which I set in
/opt/local/etc/{mysql5,mysql51}/my.cnf.
In my.cnf if you set the socket and datadir locations to the same as mysql5
everything should just work.
You can probably get away with installing mysql51 and coping your mysql5
my.cnf file over mysql55's my.cnf file.
$ sudo cp /opt/local/etc/{mysql5,mysql51}/my.cnf
And then look through the new my.cnf for any paths you may want to adjust.
Then stop mysql5 and start mysql55.
$ sudo port unload mysql5
$ sudo port load mysql51
Thank you Bradley, I'll give it a shot.
Terrry, mysql5 has been added back as a variant and will remain until mysql5 is
replaced_by mysql51.
I would stick with mysql5 until we finish the ongoing updates to the mysql's;
hopefully soon.
Regards,
Bradley Giesbrecht (pixilla)
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)viewing messages/notes from installation
Greetings, Messages/notes often fly by unnoticed when printed during installation, especially for ports that are built as dependencies of others. The note about startupitem for dbus is a topical example. 8-) How do I (re)view any such messages? I *thought* that port notes port would do the trick. But I get: - port installed dbus The following ports are currently installed: dbus @1.4.18_0 (active) - port notes dbus dbus has no notes. even though I see such a note in Portfile. I'm missing something... Thanks, Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: mysql5 and mysql51
Terry Barnum wrote: On May 4, 2012, at 7:24 PM, Bradley Giesbrecht wrote: Terry, what ports do you have installed that depend on mysql? $ port dependents mysql5 dovecot depends on mysql5 dovecot2 depends on mysql5 p5-dbd-mysql depends on mysql5 p5.12-dbd-mysql depends on mysql5 postfix depends on mysql5 dovecot has been superseeded by dovecot2 ought to be retired dovecot2 mysql51 mysql55 inserted both mysql51 mysql55 builds mysql5 removed p5-dbd-mysql p5.12-dbd-mysql is a subport mysql51 mysql55 patch in trac https://trac.macports.org/ticket/34356 patch works on my system postfix mysql51 mysql55 inserted mysql51 builds mysql55 fails to build - under investigation mysql5 removed -- 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: (re)viewing messages/notes from installation
Running port notes dbus gives me this: dbus has the following notes: # Startup items have been generated that will aid in # starting dbus with launchd. They are disabled # by default. Execute the following command to start them, # and to cause them to launch at startup: # # sudo launchctl load -w /Library/LaunchDaemons/org.freedesktop.dbus-system.plist # launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist So I think your method is correct. Are you running it as su or as a regular user? On Mon, May 7, 2012 at 1:06 PM, Mark Perkins m...@sixshooterpeaks.netwrote: Greetings, Messages/notes often fly by unnoticed when printed during installation, especially for ports that are built as dependencies of others. The note about startupitem for dbus is a topical example. 8-) How do I (re)view any such messages? I *thought* that port notes port would do the trick. But I get: - port installed dbus The following ports are currently installed: dbus @1.4.18_0 (active) - port notes dbus dbus has no notes. even though I see such a note in Portfile. I'm missing something... Thanks, Mark ___ 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: mysql5 and mysql51
On May 7, 2012, at 11:38 AM, Bjarne D Mathiesen wrote: Terry Barnum wrote: On May 4, 2012, at 7:24 PM, Bradley Giesbrecht wrote: Terry, what ports do you have installed that depend on mysql? $ port dependents mysql5 dovecot depends on mysql5 dovecot2 depends on mysql5 p5-dbd-mysql depends on mysql5 p5.12-dbd-mysql depends on mysql5 postfix depends on mysql5 dovecot has been superseeded by dovecot2 ought to be retired dovecot2 mysql51 mysql55 inserted both mysql51 mysql55 builds mysql5 removed p5-dbd-mysql p5.12-dbd-mysql is a subport mysql51 mysql55 patch in trac https://trac.macports.org/ticket/34356 patch works on my system postfix mysql51 mysql55 inserted mysql51 builds mysql55 fails to build - under investigation mysql5 removed We need to keep the mysql5 variants until we have a path for someone to migrate ALL there mysql5 dependent ports to the new mysql's. Regards, Bradley Giesbrecht (pixilla) 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: (re)viewing messages/notes from installation
I ran it both ways. Same result, as I would expect. But I think I found the source of the problem, though I don't understand it * I have dbus @1.4.18_0 is installed * I recently did a 'port sync', so the port tree has - port info dbus dbus @1.4.20 (devel) snip * On another system where I have not sync'd the ports tree, I get the same as you, which is what I would expect. So now my question is why? Even though my tree is newer than what is installed, shouldn't I be able to see things relevant to my installation? Mark On 2012/05/07 12:42, Richard DeLaurell wrote: Running port notes dbus gives me this: dbus has the following notes: # Startup items have been generated that will aid in # starting dbus with launchd. They are disabled # by default. Execute the following command to start them, # and to cause them to launch at startup: # # sudo launchctl load -w /Library/LaunchDaemons/org.freedesktop.dbus-system.plist # launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist So I think your method is correct. Are you running it as su or as a regular user? On Mon, May 7, 2012 at 1:06 PM, Mark Perkins m...@sixshooterpeaks.netwrote: Greetings, Messages/notes often fly by unnoticed when printed during installation, especially for ports that are built as dependencies of others. The note about startupitem for dbus is a topical example. 8-) How do I (re)view any such messages? I *thought* that port notes port would do the trick. But I get: - port installed dbus The following ports are currently installed: dbus @1.4.18_0 (active) - port notes dbus dbus has no notes. even though I see such a note in Portfile. I'm missing something... Thanks, Mark ___ 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: (re)viewing messages/notes from installation
On Mon, May 7, 2012 at 2:07 PM, Mark Perkins m...@sixshooterpeaks.netwrote: So now my question is why? Even though my tree is newer than what is installed, shouldn't I be able to see things relevant to my installation? Those are the kind of insights only available from an oracular source (trans. I think Ryan will have to answer that question for you.) Mark On 2012/05/07 12:42, Richard DeLaurell wrote: Running port notes dbus gives me this: dbus has the following notes: # Startup items have been generated that will aid in # starting dbus with launchd. They are disabled # by default. Execute the following command to start them, # and to cause them to launch at startup: # # sudo launchctl load -w /Library/LaunchDaemons/org.freedesktop.dbus-system.plist # launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist So I think your method is correct. Are you running it as su or as a regular user? On Mon, May 7, 2012 at 1:06 PM, Mark Perkins m...@sixshooterpeaks.net wrote: Greetings, Messages/notes often fly by unnoticed when printed during installation, especially for ports that are built as dependencies of others. The note about startupitem for dbus is a topical example. 8-) How do I (re)view any such messages? I *thought* that port notes port would do the trick. But I get: - port installed dbus The following ports are currently installed: dbus @1.4.18_0 (active) - port notes dbus dbus has no notes. even though I see such a note in Portfile. I'm missing something... Thanks, Mark ___ 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: (re)viewing messages/notes from installation
On 2012-05-07 21:07 , Mark Perkins wrote: So now my question is why? Even though my tree is newer than what is installed, shouldn't I be able to see things relevant to my installation? The 'port notes' command is always evaluating the current Portfile in the ports tree. There is no way to get the notes of the installed port version explicitly. In this specific case, could it be that in one of the cases you are using a separate port installation without startupitems? The notes are only added if the variant +startupitem is selected. Some more details for the curious and developers: the implementation of notes predates registry2.0, with which we started to store the Portfile in the registry. It would now be possible to show the notes for the active version. However, such a change would have more implications for the interface. For example, a command such as 'port info' can be useful for both the current version in the tree, or the version currently installed/active. Also it's unclear what 'ports notes' should show if the port is not installed. Rainer PS: To keep things sorted, please take this topic to macports-dev follow-ups about possible implementations. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: (re)viewing messages/notes from installation
On 2012/05/07 15:09, Rainer Müller wrote: On 2012-05-07 21:07 , Mark Perkins wrote: So now my question is why? Even though my tree is newer than what is installed, shouldn't I be able to see things relevant to my installation? One small clarification. Everything about dbus appears to be working fine for me. I wanted to check the notes for what they said about launchctl commands to ensure that what I was seeing via 'launchctl list' was the full story (it is). When 'port notes dbus' showed 'no notes', I found the answer by sleuthing. The 'port notes' command is always evaluating the current Portfile in the ports tree. There is no way to get the notes of the installed port version explicitly. I can see (more or less) that that is what it is doing. It's unfortunate that I can't see the notes for the installed version, since that is what I want to know about. In the dbus case, if it showed me the notes for what's in-tree now, it would be the same. In this specific case, could it be that in one of the cases you are using a separate port installation without startupitems? No... at least I don't think so. dbus was installed (on both systems) as a dependency of something else and AFAICT has default variants. And the startup items *are* installed and properly loaded. The notes are only added if the variant +startupitem is selected. As I understand the current state of the dbus port, that's true for v1.4.20, but was not the case for 1.4.18 (what I have installed). With 1.4.18, the variant controlling startupitem was opposite sense. Some more details for the curious and developers: the implementation of notes predates registry2.0, with which we started to store the Portfile in the registry. It would now be possible to show the notes for the active version. However, such a change would have more implications for the interface. For example, a command such as 'port info' can be useful for both the current version in the tree, or the version currently installed/active. Also it's unclear what 'ports notes' should show if the port is not installed. I confess that I find it annoying that 'port info' doesn't tell me the story for my installed version. My last foray into tcl programming was in the previous century, else I might be inclined to dig into this. Rainer PS: To keep things sorted, please take this topic to macports-dev follow-ups about possible implementations. Thanks for the explanations. Education trumps ego. ;-) Mark ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
How do we know what each variant does?
Hello MacPorts community, I have never used them, probably because I don't have an answer yet to that question. What exactly are variants of a given port, and what are their description ? As an example, I don't understand what the X11, the GUI, the NO-GUI variants are for the PSPP port, since the standard installation (no variant) provides both non-GUI and GUI modes, the latter with X11. Thanks for insights, Pat ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: How do we know what each variant does?
I have never used them, probably because I don't have an answer yet to that question. What exactly are variants of a given port, and what are their description ? As an example, I don't understand what the X11, the GUI, the NO-GUI variants are for the PSPP port, since the standard installation (no variant) provides both non-GUI and GUI modes, the latter with X11. `port variants ...` will list out the variants and descriptions of them. For PSPP[-devel] they are: pspp has the variants: doc: Build documentation help: Provide in-application help via yelp * conflicts with no_gui ncurses: Enable terminal resizing no_graph: Disable graphing features no_gui: Disable PSPPIRE, the graphical interface * conflicts with help postgres: Enables reading of postgresql databases universal: Build for multiple architectures pspp-devel has the variants: doc: Build documentation [+]graph: Enable graphing features * conflicts with no_graph [+]gui: Build PSPPIRE, the graphical interface * conflicts with no_gui help: Provide in-application help via yelp * conflicts with no_gui * requires gui no_graph: Obsolete * conflicts with graph no_gui: Obsolete * conflicts with gui postgres: Enables reading of postgresql databases [+]quartz: Support for native Mac OS X graphics * conflicts with x11 universal: Build for multiple architectures x11: Enable X11 support * conflicts with quartz 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
MacPorts 2.1.0-rc1 now available for testing
Source code and pkg/dmgs for MacPorts 2.1.0-rc1 are now available [1]. Testing of either of these install methods is helpful. While there are no known regressions from 2.0.4 at this point, be prepared to encounter bugs. As always, having a recent backup would be wise. Please report any bugs that you find [2] (after first searching Trac [3], of course!) If no showstopping bugs are found in the next few days, this will become the 2.1.0 release. There are a large number of changes in this release. See the ChangeLog [4] for a list of most of them. You may like to focus your testing on the new features in that list, as well as your normal usage. Notable changes since beta1 are: * Fixed installing from archives on systems where tar is gnutar (i.e. Leopard and Tiger). (#34080) * Fixed incorrect behaviour of 'port deps' and 'port log' in the case where a subport is specified via a glob or pseudo-portname selector. Cheers, Josh [1] https://distfiles.macports.org/MacPorts/testing/ [2] https://trac.macports.org/newticket [3] https://trac.macports.org/search [4] https://trac.macports.org/browser/branches/release_2_1/base/ChangeLog ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
