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, kde-l10n-es
On Aug 17, 2011, at 17:04, David Perlman wrote:
>
> On Aug 17, 2011, at 3:42 PM, Ryan Schmidt wrote:
>
>>> Error: port uninstall failed: error deleting
>>> "/opt/local/var/macports/software/1Dmean/1.0_0": directory not empty
>>
>> Delete the directory and try again.
>
> I sudo rm -Rf'd the d
On Aug 17, 2011, at 15:43, Jeremy Lavergne wrote:
> 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).
Well, it looks like old installed ports from an older OS, thus built for a
different architecture, fo
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
http://lists.macosforge.org/mailman/listinfo.c
On Aug 17, 2011, at 15:37, David Perlman wrote:
> :info:configure dyld: Library not loaded: /opt/local/lib/libintl.8.dylib
> :info:configure Referenced from: /opt/local/bin/gawk
> :info:configure Reason: no suitable image found. Did find:
> :info:configure /opt/local/lib/libintl.8.dylib
I am pretty deep down a rabbit hole which started with just trying to install
ffmpeg. Getting along a little bit at a time... but now having these errors:
Trinley:macports omgoleus$ sudo port selfupdate
---> Updating the ports tree
---> Updating MacPorts base sources using rsync
MacPorts base
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. T
On 16 Aug 2011, at 22:24, Andrew Long wrote:
>>
>
> The problem that I now have is to find out which application that, probably
> several years and several machines ago, caused me to need to install mono
> framework. But that isn't a problem for this list.
The application was usenext (the hig
On Aug 16, 2011, at 5:01 PM, Eric Cronin wrote:
>
>> As far as I know, we don't link with Mono, so it shouldn't interfere
>> with selfupdate (it may interfere with building your own mono). I
>> wasn't sure which was failing for you...
>
> We don't. But, the 3rd party Mono package installs in a l
The same problem like #30072
(http://lists.macosforge.org/pipermail/macports-tickets/2011-July/085635.html)
The comment in #30073 said it was fixed, but now it does not work still!
Can't start terminator!!
bash-3.2$ terminator
You need to install the python bindings for gobject, gtk and pang
On 17 Aug 2011, at 11:25, Ryan Schmidt wrote:
>> As I wiped my disk and installed Lion from a bootable USB key I made with my
>> copy of Lion (I did this to maximise performance), I had nothing in the way
>> of MacPorts
>
> Ok.
>
>
>> All I am saying is, on the same machine the selfupdate ste
On Aug 17, 2011, at 05:23, Federico Calboli wrote:
> On 17 Aug 2011, at 11:19, Ryan Schmidt wrote:
>
>> Correct, MacPorts 1.x was not compatible with Lion, if that's what you mean.
>>
>>> so all I see now is post fresh install of MP 2.0.1 from disk image.
>>
>> FYI, installing a MacPorts disk i
On 17 Aug 2011, at 11:19, Ryan Schmidt wrote:
>
> Correct, MacPorts 1.x was not compatible with Lion, if that's what you mean.
>
>> so all I see now is post fresh install of MP 2.0.1 from disk image.
>
> FYI, installing a MacPorts disk image over an existing MacPorts install would
> not uninst
On Aug 17, 2011, at 04:59, Federico Calboli wrote:
>> If you're upgrading from MacPorts 1.x to MacPorts 2.x, then all existing
>> installed ports must be converted. This can take hours depending on how many
>> ports you have installed, but again should be bound by disk speed and not be
>> CPU
> If you're upgrading from MacPorts 1.x to MacPorts 2.x, then all existing
> installed ports must be converted. This can take hours depending on how many
> ports you have installed, but again should be bound by disk speed and not be
> CPU intensive
I should have mentioned, when I installed Lion
On Aug 16, 2011, at 09:24, Mark Hattam wrote:
> Error: Target org.macports.deactivate returned: Active version of
> p5-locale-gettext is not 1.50.0_5 but 1.05_5.
Looks like what I filed here:
https://trac.macports.org/ticket/30833
I'm hoping someone who better understands base and the changes
16 matches
Mail list logo
