macports-users Digest, Vol 62, Issue 2

[Fabrizio Bartolomucci]

Does anyone know if there is a gimp distribution for OSX Lion?

Sent by a mobile Fabrizio Bartolomucci from an iPhone:
mailto:fbartolom at gmail.com
facetime://3474013121

On 02/ott/2011, at 16:00, macports-users-request at lists.macosforge.org wrote:

> Send macports-users mailing list submissions to
>    macports-users at lists.macosforge.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>    http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
> or, via email, send a message with subject or body 'help' to
>    macports-users-request at lists.macosforge.org
> 
> You can reach the person managing the list at
>    macports-users-owner at lists.macosforge.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of macports-users digest..."
> 
> 
> Today's Topics:
> 
>   1. Re: MacPorts selfupdate fails? cannot write to location
>      (William H. Magill)
>   2. Lion/MacPorts2.x migration: Fetchmail looking for Kerberos
>      (Bill Christensen)
>   3. Re: Lion/MacPorts2.x migration: Fetchmail looking for
>      Kerberos (Brandon Allbery)
>   4. Re: MacTex vs MacPorts (Ryan Schmidt)
>   5. Re: autoexpect : can't find package Expect (Ryan Schmidt)
>   6. Re: Re: MacPorts selfupdate fails& cannot write to location
>      (Joshua Root)
>   7. Re: Re: MacPorts selfupdate fails& cannot write to location
>      (Joshua Root)
>   8. Re: i383-elf-gdb build help (Dongsheng Wang)
>   9. Re: i383-elf-gdb build help (Ryan Schmidt)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Sat, 01 Oct 2011 15:07:01 -0400
> From: "William H. Magill" <magill at me.com>
> To: macports-users <macports-users at lists.macosforge.org>
> Subject: Re: MacPorts selfupdate fails? cannot write to location
> Message-ID: <9E8560A8-A1BE-48A5-9607-A9BCDB412112 at me.com>
> Content-Type: text/plain; charset=windows-1252
> 
> 
> On Sep 14, 2011, at 12:38 PM, Ryan Schmidt wrote:
> 
>> On Sep 13, 2011, at 21:49, William H. Magill wrote:
>>> This is very weird? True? registry.db does not exist? no idea why unless the previous "selfupdate" attempt deleted it.
>>>                                 False? both my userid and root (sudo) can write to the directory.
>>> -----------------------------<cut here>--------------------------
>>> outpost> sudo port -v selfupdate
>>> Password:
>>> port registry doesn't exist at "/opt/local/var/macports/registry/registry.db" and couldn't write to this location
>> 
>> [snip]
>> 
>>> Note: last activity had been 8 July when I successfully installed iStumbler.
>> 
>> July 8 predates MacPorts 2, unless you were running a beta version of it.
>> 
>> MacPorts 1 by default used a flat registry, not the new SQLite registry mandated by MacPorts 2.
>> 
>> When upgrading to MacPorts 2, it's supposed to detect if you're using the flat registry, and convert it to the new SQLite registry.
>> 
>> It looks like that conversion didn't happen in your case, or at least, didn't happen completely. Or maybe you thought selfupdate was taking too long and you interrupted it? The conversion can take hours depending on how many ports you have installed and how fast your computer is.
>> 
>> In that case, hopefully MacPorts hasn't removed the previous flat registry information, and it should be possible to "reset" MacPorts so that it tries the conversion again. But I forget how to make it do that.
> 
> Returning to a problem I was having earlier before "life" interrupted ?.and am still having.
> 
> I realize that the registry.db file does not exist. What I don't understand is the "couldn't write to this location" part of the error.
> 
> I have no problem simply wiping Mac Ports and sting over but upgrading from Snow Leopard (where I had last run Mac Ports 1.9) to Lion and attempting to upgrade to MacPorts 2.x "should work."
> I also realize that the flat registry is/was gone because of a previous failed "self update"? but why can't it write?
> 
> =================<cut here>===================
> outpost> sudo port -vd selfupdate
> port registry doesn't exist at "/opt/local/var/macports/registry/registry.db" and couldn't write to this location
>    while executing
> "registry::open $db_path"
>    (procedure "mportinit" line 551)
>    invoked from within
> "mportinit ui_options global_options global_variations"
> Error: /opt/local/bin/port: Failed to initialize MacPorts, port registry doesn't exist at "/opt/local/var/macports/registry/registry.db" and couldn't write to this location
> =================<cut here>===================
> 
> outpost> ls -alse /opt
> total 0
> 0 drwxr-xr-x@  3 magill  admin   102 Aug 27  2009 .
> 0 drwxr-xr-x@ 32 root    wheel  1156 Aug 17 21:49 ..
> 0 drwxr-xr-x  13 magill  admin   442 Sep 12 13:45 local
> [/Users/magill] magill 
> outpost> ls -alse /opt/local
> total 4
> 0 drwxr-xr-x  13 magill  admin   442 Sep 12 13:45 .
> 0 drwxr-xr-x@  3 magill  admin   102 Aug 27  2009 ..
> 0 drwxr-xr-x  28 magill  admin   952 Sep 12 13:45 bin
> 0 drwxr-xr-x   3 magill  admin   102 Aug 27  2009 etc
> 0 drwxr-xr-x  23 magill  admin   782 Jun 15 01:37 include
> 0 drwxr-xr-x  31 magill  admin  1054 Sep 12 13:45 lib
> 0 drwxr-xr-x   3 magill  admin   102 Nov  7  2010 libexec
> 4 lrwxr-xr-x   1 root    admin     9 Sep 12 13:45 man -> share/man
> 0 drwxr-xr-x   3 magill  admin   102 Nov  7  2010 sbin
> 0 drwxr-xr-x   7 magill  admin   238 Sep 12 13:45 share
> 0 drwxr-xr-x   2 magill  admin    68 Sep 12 13:45 src
> 0 drwxr-xr-x   3 magill  admin   102 Nov  7  2010 var
> 0 drwxr-xr-x   2 magill  admin    68 Sep 12 13:45 www
> [/Users/magill] magill 
> outpost> ls -alse /opt/local/var
> total 0
> 0 drwxr-xr-x   3 magill  admin  102 Nov  7  2010 .
> 0 drwxr-xr-x  13 magill  admin  442 Sep 12 13:45 ..
> 0 drwxr-xr-x  12 magill  admin  408 Sep 12 13:45 macports
> [/Users/magill] magill 
> outpost> ls -alse /opt/local/var/macports
> total 16
> 0 drwxr-xr-x  12 magill  admin   408 Sep 12 13:45 .
> 0 drwxr-xr-x   3 magill  admin   102 Nov  7  2010 ..
> 4 -rw-r--r--   1 root    admin    13 Sep 12 13:45 .tclpackage
> 0 drwxr-xr-x   3 magill  admin   102 Jul  8 14:03 build
> 0 drwxr-xr-x   4 magill  admin   136 Jul  8 14:03 distfiles
> 0 drwxr-xr-x   2 magill  admin    68 Jul  8 14:03 logs
> 0 drwxr-xr-x   3 root    admin   102 Nov  7  2010 packages
> 12 -r--r--r--   1 magill  admin  9851 Sep 12 13:45 port-help.tcl
> 0 drwxr-xr-x   6 root    admin   204 Jul  8 14:03 receipts
> 0 drwxr-xr-x   4 magill  admin   136 Sep 13 22:39 registry
> 0 drwxr-xr-x   3 magill  admin   102 Jul  8 14:03 software
> 0 drwxr-xr-x   3 root    admin   102 Jun 15 01:37 sources
> [/Users/magill] magill 
> outpost> ls -alse /opt/local/var/macports/registry
> total 0
> 0 drwxr-xr-x   4 magill  admin  136 Sep 13 22:39 .
> 0 drwxr-xr-x  12 magill  admin  408 Sep 12 13:45 ..
> 0 -rw-r--r--   1 root    admin    0 Jul  8 14:03 .registry.lock
> 0 -rw-rw-r--   1 root    admin    0 Nov  7  2010 .turd_MacPorts
> [/Users/magill] magill 
> 
> 
> 
> T.T.F.N.
> William H. Magill
> # iMac11,3 Core i7 [2.936GHz - 4 GB 1333] OS X 10.7.1
> # iMac6,1 Core 2 Duo [2.16GHz - 3 GB 667] OS X 10.6.8
> # MacBook Pro4.1 Core 2 Duo [2.5GHz - 4GB 667] OS X 10.6.8
> # Mac mini Core Duo [1.66 Ghz - 2 GB 667] OS X 10.6.8
> # Flat-panel iMac (2.1) [800MHz - Super Drive - 768 Meg] OS X 10.4.11 
> # PWS433a [Alpha 21164 Rev 7.2 (EV56)- 64 Meg] Tru64 5.1a 
> # XP1000 [Alpha 21264-3 (EV6) - 256 meg] FreeBSD 5.3
> # XP1000 [Alpha 21264-A (EV6-7) - 256 meg] FreeBSD 5.3
> magill at mcgillsociety.org
> magill at me.com
> whmagill at gmail.com
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Sat, 01 Oct 2011 15:56:23 -0500
> From: Bill Christensen <billc_lists at greenbuilder.com>
> To: macports-users <macports-users at lists.macosforge.org>
> Subject: Lion/MacPorts2.x migration: Fetchmail looking for Kerberos
> Message-ID: <4E877E77.6020100 at greenbuilder.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> Hi folks,
> 
> I'm doing a test migration of a server from SnowLeopard/MacPorts 1.9.x 
> to Lion/MacPorts2.x.   Most of it appears to be going fairly smoothly 
> (though uninstalling/reinstalling all the ports is a bit tedious), but 
> i've run into a problem installing Fetchmail.  It's looking for Kerberos 
> V... apparently found in /usr, but then gives the error "Kerberos 5 DES 
> libraries not found" in the log, and quits.
> 
> Any suggestions?
> 
> Thanks!
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Sat, 1 Oct 2011 18:01:13 -0400
> From: Brandon Allbery <allbery.b at gmail.com>
> To: Bill Christensen <billc_lists at greenbuilder.com>
> Cc: macports-users <macports-users at lists.macosforge.org>
> Subject: Re: Lion/MacPorts2.x migration: Fetchmail looking for
>    Kerberos
> Message-ID:
>    <CAKFCL4U=nAFz60Mf9Q5m8oQrNXBsb+cjw0CHERBb7Z5j6zEh0Q at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> On Sat, Oct 1, 2011 at 16:56, Bill Christensen <billc_lists at greenbuilder.com
>> wrote:
> 
>> I'm doing a test migration of a server from SnowLeopard/MacPorts 1.9.x to
>> Lion/MacPorts2.x.   Most of it appears to be going fairly smoothly (though
>> uninstalling/reinstalling all the ports is a bit tedious), but i've run into
>> a problem installing Fetchmail.  It's looking for Kerberos V... apparently
>> found in /usr, but then gives the error "Kerberos 5 DES libraries not found"
>> in the log, and quits.
>> 
> 
> That's a Lion compatibility issue... Apple decided to change the whole
> Kerberos subsystem in frustrating ways, so on Lion a lot of stuff that could
> use system Kerberos now needs to use one from MacPorts, and not all ports
> have been updated to reflect this yet.  Install heimdal or kerberos5 from
> ports and you should be fine; also file a ticket against the fetchmail port
> about the Lion incompatibility.
> 
> (Specifically:  they switched from MIT to Heimdal, then left out most of the
> API.  As such, the heimdal port might work better with Lion's Kerberos.)
> 
> -- 
> brandon s allbery                                      allbery.b at gmail.com
> wandering unix systems administrator (available)     (412) 475-9364 vm/sms
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20111001/96efe4f8/attachment-0001.html>
> 
> ------------------------------
> 
> Message: 4
> Date: Sat, 1 Oct 2011 17:47:28 -0500
> From: Ryan Schmidt <ryandesign at macports.org>
> To: Sam Kuper <sam.kuper at uclmail.net>
> Cc: "macports-users at lists.macosforge.org Mailing List"
>    <macports-users at lists.macosforge.org>
> Subject: Re: MacTex vs MacPorts
> Message-ID: <31B71A0B-D0B6-4347-A2EF-4D9C553790B6 at macports.org>
> Content-Type: text/plain; charset=us-ascii
> 
> 
> On Oct 1, 2011, at 07:53, Sam Kuper wrote:
> 
>> On 1 October 2011 10:04, Keith J. Schultz <keithjschultz at web.de> wrote:
>>> (Snip)
>>> MacTeX does work well with Macports. You have to change the config-file
>>> of MacPorts to look for the existence of the MacTeX binaries. Sorry, I can not
>>> remember which. Of course It may not work anymore.
>>> 
>>> At least I am happy with MacTeX.
>> 
>> Thanks Keith. Is the change you referred to described here:
>> http://www.tug.org/mactex/multipletexdistributions.html ? Or did you
>> find that a different change worked better?
> 
> If you want MacTex software to be able to satisfy MacPorts TeX dependencies, you can add /usr/texbin to binpath in macports.conf. Otherwise if you install ports that require TeX, they'll install the requisite MacPorts TeX ports.
> 
> 
> 
> 
> 
> ------------------------------
> 
> Message: 5
> Date: Sat, 1 Oct 2011 18:14:01 -0500
> From: Ryan Schmidt <ryandesign at macports.org>
> To: Yvon Thoraval <yvon.thoraval at gmail.com>
> Cc: Mark Duling <markd at macports.org>,    MacPorts Users
>    <macports-users at lists.macosforge.org>
> Subject: Re: autoexpect : can't find package Expect
> Message-ID: <492B30FD-FAB4-47EF-B72D-BB7E7A6A4BCE at macports.org>
> Content-Type: text/plain; charset=us-ascii
> 
> On Oct 1, 2011, at 01:10, Yvon Thoraval wrote:
> 
>> after :
>> $ sudo port uninstall expect
>> $ sudo port selfupdate
>> $ sudo port install expect
>> giving :
>> --->  Computing dependencies for expect
>> --->  Fetching archive for expect
>> --->  Attempting to fetch expect-5.45_1.darwin_11.x86_64.tgz from http://packages.macports.org/expect
>> --->  Fetching expect
>> --->  Verifying checksum(s) for expect
>> --->  Extracting expect
>> --->  Configuring expect
>> --->  Building expect
>> --->  Staging expect into destroot
>> --->  Installing expect @5.45_1
>> --->  Activating expect @5.45_1
>> --->  Cleaning expect
>> 
>> i ran autoexpect, having same prob :
>> $  autoexpect
>> can't find package Expect
>>    while executing
>> "package require Expect"
>>    (file "/opt/local/bin/autoexpect" line 6)
>> 
>> 
>> ???
> 
> You know, I see the same problem. We also already have this bug report about it:
> 
> https://trac.macports.org/ticket/31225
> 
> So now someone just needs to figure out how to resolve it.
> 
> 
> 
> 
> ------------------------------
> 
> Message: 6
> Date: Sun, 02 Oct 2011 10:45:30 +1100
> From: Joshua Root <jmr at macports.org>
> To: "William H. Magill" <magill at me.com>
> Cc: MacPorts Users <macports-users at lists.macosforge.org>
> Subject: Re: Re: MacPorts selfupdate fails& cannot write to location
> Message-ID: <4E87A61A.4090708 at macports.org>
> Content-Type: text/plain; charset=UTF-8
> 
> On 28164-7-23 05:59 , William H. Magill wrote:
>> Returning to a problem I was having earlier before "life" interrupted ?.and am still having.
>> 
>> I realize that the registry.db file does not exist. What I don't understand is the "couldn't write to this location" part of the error.
> 
> It's a bug (fixed in svn). It's looking at the permissions on the
> registry dir, sees that it is not the owner, and the group and world
> writable bits are not set, so it concludes that it cannot write to that
> directory.
> 
>> I have no problem simply wiping Mac Ports and sting over but upgrading from Snow Leopard (where I had last run Mac Ports 1.9) to Lion and attempting to upgrade to MacPorts 2.x "should work."
>> I also realize that the flat registry is/was gone because of a previous failed "self update"? but why can't it write?
> 
> What makes you say the flat registry is gone? Is there nothing in
> /opt/local/var/macports/receipts?
> 
> - Josh
> 
> 
> ------------------------------
> 
> Message: 7
> Date: Sun, 02 Oct 2011 11:00:02 +1100
> From: Joshua Root <jmr at macports.org>
> To: "William H. Magill" <magill at me.com>
> Cc: MacPorts Users <macports-users at lists.macosforge.org>
> Subject: Re: Re: MacPorts selfupdate fails& cannot write to location
> Message-ID: <4E87A982.3020904 at macports.org>
> Content-Type: text/plain; charset=UTF-8
> 
> On 28164-7-23 05:59 , William H. Magill wrote:
>> I have no problem simply wiping Mac Ports and sting over but upgrading from Snow Leopard (where I had last run Mac Ports 1.9) to Lion and attempting to upgrade to MacPorts 2.x "should work."
> 
> Another thing: Note that the Migration instructions actually say to use
> the installer, not to selfupdate. If you go from 10.5 to 10.6 for
> example, the existing version will most likely not be able to run
> because an i386/ppc MacPorts.dylib cannot be loaded into an x86_64 tclsh.
> 
> Selfupdate probably does work OK going from 10.6 to 10.7, and I'm not
> sure if installing the .pkg resets the ownership on the directories
> (which would solve your problem if it does). But anyway, that's what the
> Migration wiki page says, and there are good reasons for it.
> 
> - Josh
> 
> 
> ------------------------------
> 
> Message: 8
> Date: Sun, 2 Oct 2011 08:02:52 -0400
> From: Dongsheng Wang <dongsheng at gmail.com>
> To: Ryan Schmidt <ryandesign at macports.org>
> Cc: macports-users at lists.macosforge.org
> Subject: Re: i383-elf-gdb build help
> Message-ID:
>    <CAO2WUH6OJ6FybAKr_z2-XSNitpXW1VCOz2ySyvA_9AHcomiQ6Q at mail.gmail.com>
> Content-Type: text/plain; charset="windows-1252"
> 
> I copied the Portfile from corss/arm-elf-gdb to start. After replaced all
> "arm" with "i386", it actually worked all the way to activation. And, it
> gave the following error during activation phrase. (I hade arm-elf-gdb
> installed already BTW) After I deactivate arm-elf-gdb and try again.
> Everything is fine.
> 
> What is the right way to fix the problem?
> 
> :error:activate Target org.macports.activate returned: Image error:
> /opt/local/share/gdb/syscalls/amd64-linux.xml is being used by the active
> arm-elf-gdb port.  Please deactivate this port first, or use 'port -f
> activate i386-elf-gdb' to force the activation.
> :debug:activate Backtrace: Image error:
> /opt/local/share/gdb/syscalls/amd64-linux.xml is being used by the active
> arm-elf-gdb port.  Please deactivate this port first, or use 'port -f
> activate i386-elf-gdb' to force the