BTW, for the record here, the problem with the upgrade turned out to be
macports found the old bzip2 and was trying to use it to extract the
tarball. It was the old tiger binary, and failing, but the ports code
wasn't detecting the failure. When it went to process the extracted
files, they we
On Jun 13, 2008, at 18:29, Brian Flaherty wrote:
> Hello,
>
> I have Emacs.app installed, and I'd like to install emacs +carbon
> too. When I did that, everything was fine until activation:
>
> ---> Activating emacs 22.2_0+carbon
> Error: Target org.macports.activate returned: Image error:
> /A
Hello,
I have Emacs.app installed, and I'd like to install emacs +carbon
too. When I did that, everything was fine until activation:
---> Activating emacs 22.2_0+carbon
Error: Target org.macports.activate returned: Image error:
/Applications/MacPorts/Emacs.app/Contents/Info.plist is being used
On Jun 13, 2008, at 16:27, Alan Batie wrote:
> Ryan Schmidt wrote:
>
>> MacPorts just has no way to know. That's why it's an excellent
>> suggestion to add the OS version, Xcode version and processor
>> architecture to the unique identifier to try to make it truly unique.
>
> We're in violent
Ryan Schmidt wrote:
MacPorts just has no way to know. That's why it's an
excellent suggestion to add the OS version, Xcode version and processor
architecture to the unique identifier to try to make it truly unique.
We're in violent agreement ;-) I was thinking of this future, sorry
about th
On Jun 13, 2008, at 02:35, Alan Batie wrote:
> Ryan Schmidt wrote:
>
if there's a change from what's installed, replace what's
installed
with the new version
>>
>> MacPorts has no way to know "if there's a change from what's
>> installed"
>
> Given that you can say "port ins
Alan Batie wrote:
> The error I'm seeing (I did a "port -f uninstall glib2" before to try to
> start fresh):
>
> # port install glib2
> ---> Applying patches to glib2
> Error: Target org.macports.patch returned: couldn't change working
> directory to
> "/opt/local/var/macports/build/_opt_local
On Jun 13, 2008, at 5:11 AM, Joerg van den Hoff wrote:
> hi,
>
> under 10.4.11 I did a `port upgrade mercurial'.
>
...
> /usr/bin/libtool -o libpython2.5.dylib -dynamic \
>-all_load libpython2.5.a -single_module \
>-install_name /opt/local/lib/libpython2.5.dylib \
>-compat
On Jun 13, 2008, at 13:48, Yvon Thoraval wrote:
>> No port should claim ownership of perllocal.pod. Any port that
>> does needs to be fixed.
>>
>> git-core stopped claiming ownership of perllocal.pod in r34462
>> (2008-02-25) so you should update your ports ("sudo port
>> selfupdate"), clean
hi,
under 10.4.11 I did a `port upgrade mercurial'.
which depends on python2.5 and `port' tries to install this (only
python2.4 installed up to now). now I see the following:
==CUT
---> Fetching python25
--->
Ryan Schmidt wrote:
if there's a change from what's installed, replace what's installed
with the new version
MacPorts has no way to know "if there's a change from what's
installed"
Given that you can say "port installed" to list what's installed, there
must be some sort of registration
11 matches
Mail list logo
