Was adding the usual mamp stuff to a new machine
port install mysql5 +server
- or -
port install mysql5-devel +server
Does the only thing the +server variant adds is a launchd/startup
item? From looking at the port, that appears to be the case.
If that is the case, looking at
port info
Thanks Jeremy,
I did
sudo port upgrade pango
and it installed glib2. But when I run coqide,
the pango error messages are still there.
I do not know how to isolate the font that is
causing the problem, and also am unable to figure
that out from your bug report (probably due to
ignorance on
On Apr 22, 2009, at 04:08, Dimitri Hendriks wrote:
I did
sudo port upgrade pango
and it installed glib2.
pango has always required glib2 so glib2 must already have been on
your system. Though it may have been upgraded.
You should now have pango 1.24.1, yes?
But when I run coqide,
On Apr 22, 2009, at 04:00, Scott Haneda wrote:
Was adding the usual mamp stuff to a new machine
port install mysql5 +server
- or -
port install mysql5-devel +server
Does the only thing the +server variant adds is a launchd/startup
item? From looking at the port, that appears to be the
Ryan Schmidt wrote:
On Apr 21, 2009, at 23:27, Victor Eijkhout wrote:
On 2009/04/21, at 6:49 PM, Ryan Schmidt wrote:
Do you have libiconv installed with the universal variant? If so,
what architectures did you request in your macports.conf? If you
requested any 64-bit architectures, it
Hi Ryan,
You should now have pango 1.24.1, yes?
No, I have 1.24.0. If sudo port upgrade pango
is not the right way to upgrade, then what is?
Thanks again,
Dimitri
___
macports-users mailing list
macports-users@lists.macosforge.org
Dimitri Hendriks wrote:
Hi Ryan,
You should now have pango 1.24.1, yes?
No, I have 1.24.0. If sudo port upgrade pango
is not the right way to upgrade, then what is?
Probably you need to selfupdate first.
- Josh
___
macports-users mailing list
On Apr 22, 2009, at 07:41, Joshua Root wrote:
port installed gives
libiconv @1.12_0+darwin_8 (active)
Ok, so libiconv is installed, and is not universal.
But you don't have the current version. You have 1.12_0, and the
bug was
fixed in 1.12_2. Update your MacPorts and your port
I'm not sure either what's going on but I don't have time to look at
it at the moment so I'm sending your message back to the mailing list
in the hopes that someone else can help. Remember to use Reply All so
your reply goes to the list too, not just to me.
On Apr 22, 2009, at 11:47, MKG
I've got a corrupted registry (receipts).
Will reinstalling macports correct a corrupted registry?
Is it possible to re-install macports from the .dmg while keeping all the
ports that are installed (and registered)?
How can I correct a corrupted registry, without re-installation?
Thanks in
Darren Weber wrote:
I've got a corrupted registry (receipts).
Do you know which receipt it is?
I assume this the issue with using \n in the
description/long_description as you did in your gdb port. In this case,
you could fix it by editing the receipt by hand. A valid receipt should
have only
This should tell you which one is problematic:
for f in /opt/local/var/macports/receipts/*/*/receipt.bz2; do echo -n
$f bzcat $f | wc -l; done | grep -v ' 2$'
On Apr 22, 2009, at 14:09, Rainer Müller wrote:
Darren Weber wrote:
I've got a corrupted registry (receipts).
Do you know
Nice command line, Jeremy!
I did find my own custom port had some \n chars in long_description that
screwed up the registry. It's all working correctly now.
Phew!
Thanks!
On Wed, Apr 22, 2009 at 4:01 PM, Jeremy Huddleston jerem...@macports.orgwrote:
This should tell you which one is
Hello, I have been trying for a few weeks on and off, and solid a few
days to get a working postfix, dovecot system with macports, using
mysql for auth.
Has anyone gotten this up and running? I believe I am stuck on the
fact that I need sasl support in postfix and dovecot. I believe the
14 matches
Mail list logo
