Re: Macports selfupdate failed

It appears the problem is MacPorts is grabbig SQLite from /Library/Frameworks/Mono.framework/Versions/2.10.3/include/sqlite3.h Obviously, part of the problem is that the version of SQlite being found/used is from the Mono SDK (installed from go-mono.com), installed at

Re: Why was the macports user implemented

Please explain to me like if I were a four-year old, why was the user 'macports' implemented? The user was created to address this problem: Portfiles and the packages they install can contain arbitrary code, and should not be trusted unless they are signed and that packager is trusted. The

Re: Why was the macports user implemented

On Wed, August 31, 2011 3:26 pm, Rodolfo Aramayo wrote: Great. Good explanation. Thanks, but then that begs the question as to why the files in '/opt/local/' are not owned by macports:macports and instead by 'root:admin and/or root:wheel'? Am I missing something in here?? Once things are

Re: Updating Mac OS X Server 10.6.8 amavisd-new

The question I pose to the port-community, If I use the macports installer, will it update the current version of amavisd-new on 10.6.8 or just install a new version? As well, if it does install a new version what should I need to change to make use of 2.6.6 rather than the old version. At

Re: disk I/O error (10) while executing query: ATTACH DATABASE '/opt/local/var/macports/registry/registry.db' AS registry

I do not believe I have any disk problem. Disk Utility shows no problem. I am able to copy the registry file just fine without any I/O errors. That is an SQLite-specific error message, and not the foreboding of the kernel. ___ macports-users mailing

KDE4 Documentation

tl;dr documentation changes will cause a revbump [1], you can safely ignore the update if rebuilds are painful. In some situations building documentation for KDE ports has not worked for a while. This is due to libxml continuing to segfault meinproc when documentation is built by macportsuser.

Re: Port upgrade problems

I'm not seeing it, but have you tried `sudo port clean` on those ports? It looks like old build folders from prior OS (wrong architecture). ___ macports-users mailing list macports-users@lists.macosforge.org

KDE4 Documentation

Here's the list of KDE ports that had been building their documentation when they ought not to have been, fixed in r82682: blinken, cantor, digikam, gwenview, kalgebra, kalzium, kamera, kanagram, kbruch, kde-l10n-ca, kde-l10n-cs, kde-l10n-da, kde-l10n-de, kde-l10n-el, kde-l10n-en_GB,

<    2   3   4   5   6   7