From tabithamc at gmail.com Tue Jan 1 02:04:51 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Tue Jan 1 02:03:04 2008 Subject: Ok to switch from Crypt to Shadow Password? Message-ID: <7fccb3000801010204h5ae2eafdh59a27ef74e07d24f@mail.gmail.com> Hello all -- I am happily running Leopard Server and installing MacPorts 1.6.0. Some of the ports install users in the local directory domain (with Leopard Apple has officially done away with NetInfo by the way). There is an option using Workgroup Manager -- a GUI tool only bundled by Apple with Mac OS X Server, to change the password type of local directory domain users (for example, the user "ldap" installed by MacPorts as part of the openldap port) from crypt to Shadow Password. Has anyone ever tried this and if so are there any reasons not to switch from crypt to Shadow Password? Thank, -T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080101/f0e7959d/attachment.html From tabithamc at gmail.com Tue Jan 1 05:35:01 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Tue Jan 1 05:33:20 2008 Subject: Some confusion about XFree86 Message-ID: <7fccb3000801010535q293e1c56pf41e1f80ce19eff3@mail.gmail.com> Hello all -- Its been a while since I've made a bunch of MacPorts, but I have an Xserve running Leopard Server 10.5.1 and wanted to give it a try with MacPorts 1.6.0. I had problems building XFree86 (I tried to install with the -d debug option and have saved the output in case it might be useful to submit to the Trac bug reporting system). Before submitting anything, I started poking around a bit, looking at some of the more recent posts about Leopard and XFree86 on the MacPorts mailing list and also noticing that Apple's X11 app is now based on X.org. I noticed that there are also some new (well, new since I last tried MacPorts 1.5.0 on a Tiger Server system in August of 2007), ports that seem to be related to X, such as xorg-util-macros and xorg-xproto (but even these newish ports still depend on XFree86). I'm wondering if anyone can provide a little clearer lay of the land / big picture to help me fill in the missing pieces (with apologies if there is a lot more details interwoven into these mail threads). Are there any recommended paths to take with regard to X11 app or building XFree86 port? Has anyone else had failure building XFree86 on Leopard Server 10.5.1 or Leopard 10.5.1? Thank you for any suggestions. Best regards, T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080101/c435d474/attachment.html From someguyonearth at gmail.com Tue Jan 1 05:40:09 2008 From: someguyonearth at gmail.com (Some Guy) Date: Tue Jan 1 05:38:23 2008 Subject: problem using port to install gnucash on mac 10.5 Message-ID: <9153cb050801010540y6a8f53cdw501b27bcb636174f@mail.gmail.com> could anyone please help, i have been trying to install gnucash on my mac but i get this; "---> Building aqbanking with target all Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_aqbanking/work/aqbanking- 2.3.3" && make all " returned error 2 Command output: make[6]: Nothing to be done for `all'. Making all in dialogs make[6]: Nothing to be done for `all'. Making all in views make[6]: Nothing to be done for `all'. make[6]: Nothing to be done for `all-am'. Making all in qbanking Making all in lib make all-recursive Making all in widgets make all-am make[8]: Nothing to be done for `all-am'. Making all in dialogs make all-am make[8]: Nothing to be done for `all-am'. Making all in views make all-am make[8]: Nothing to be done for `all-am'. /bin/sh ../../../../libtool --tag=CXX --mode=link /usr/bin/g++-4.0 -O2 -g -Wall -L/opt/local/lib -g -o testlib testlib.o libqbanking.la/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_aqbanking/work/aqbanking- 2.3.3/src/libs/aqbanking/libaqbanking.la -lintl /usr/bin/g++-4.0 -O2 -g -Wall -g -o .libs/testlib testlib.o-Wl,-bind_at_load -L/opt/local/lib ./.libs/libqbanking.dylib -L/usr/lib -L/sw/lib -L/opt/local/lib/qt3/lib /opt/local/lib/qt3/lib/libqt- mt.dylib-L/usr/X11R6/lib -lresolv -lz -lGL /usr/X11/lib/libXmu.6.2.0.dylib /opt/local/lib/libXrender.dylib /usr/X11/lib/libXrandr.2.0.0.dylib /usr/X11/lib/libXcursor.1.0.2.dylib /usr/X11/lib/libXinerama.1.0.0.dylib /opt/local/lib/libXft.dylib /opt/local/lib/libfreetype.dylib /opt/local/lib/libfontconfig.dylib /usr/X11/lib/libXext.6.4.0.dylib /usr/X11/lib/libX11.6.2.0.dylib -lm /usr/X11/lib/libSM.6.0.0.dylib /usr/X11/lib/libICE.6.3.0.dylib -ldl /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_aqbanking/work/aqbanking- 2.3.3/src/libs/aqbanking/.libs/libaqbanking.dylib /opt/local/lib/libgwenhywfar.dylib -lssl -lcrypto /opt/local/lib/libintl.dylib /opt/local/lib/libiconv.dylib -lc ld: cycle in dylib re-exports with /usr/X11R6/lib/libGL.dylib collect2: ld returned 1 exit status make[7]: *** [testlib] Error 1 make[6]: *** [all-recursive] Error 1 make[5]: *** [all] Error 2 make[4]: *** [all-recursive] Error 1 make[3]: *** [all-recursive] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Error: The following dependencies failed to build: aqbanking evince avahi esound gconf intltool orbit2 libidl gnome-doc-utils iso-codes py25-hashlib openssl py25-libxml2 gnome-icon-theme icon-naming-utils p5-getopt-long p5-pathtools p5-xml-simple p5-test-simple p5-test-harness p5-xml-namespacesupport p5-xml-sax gnome-keyring libgcrypt libgpg-error gnome-vfs gnome-mime-data howl neon libart_lgpl libgnome libbonobo popt libgnomecanvas gail libgnomeui libbonoboui m4 nautilus eel gnome-desktop fribidi startup-notification gnome-menus libexif librsvg libcroco libgsf shared-mime-info poppler poppler-data gnucash-docs yelp firefox-x11 zip libgtkhtml goffice03 libgnomeprintui libgnomeprint bison libgnomecups pcre guile16 readline ncurses ncursesw gawk libgtkhtml3 p5-finance-quote p5-crypt-ssleay p5-libwww-perl p5-compress-zlib p5-compress-raw-zlib p5-io-compress-base p5-scalar-list-utils p5-io-compress-zlib p5-html-parser p5-html-tagset p5-uri p5-datemanip p5-html-tableextract slib slib-guile16 Error: Status 1 encountered during processing." -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080101/7fc1336a/attachment-0001.html From james.sumners at gmail.com Tue Jan 1 10:03:48 2008 From: james.sumners at gmail.com (James Sumners) Date: Tue Jan 1 10:01:59 2008 Subject: problem using port to install gnucash on mac 10.5 In-Reply-To: <9153cb050801010540y6a8f53cdw501b27bcb636174f@mail.gmail.com> References: <9153cb050801010540y6a8f53cdw501b27bcb636174f@mail.gmail.com> Message-ID: I have the best luck installing gnucash when enabling the following variants: without_quotes, without_hbci, without_ofx, and without_docs. On Jan 1, 2008 8:40 AM, Some Guy wrote: > could anyone please help, i have been trying to install gnucash on my mac > but i get this; -- James Sumners http://james.roomfullofmirrors.com/ "All governments suffer a recurring problem: Power attracts pathological personalities. It is not that power corrupts but that it is magnetic to the corruptible. Such people have a tendency to become drunk on violence, a condition to which they are quickly addicted." Missionaria Protectiva, Text QIV (decto) CH:D 59 From rsync at reifferscheid.org Tue Jan 1 11:58:01 2008 From: rsync at reifferscheid.org (Thomas Reifferscheid) Date: Tue Jan 1 11:56:13 2008 Subject: Pidgin with OTR? In-Reply-To: <4779E0A3.3090106@gmail.com> References: <4776C0FE.1010604@gmail.com> <4776F44C.8030804@reifferscheid.org> <47779628.3090005@reifferscheid.org> <4779E0A3.3090106@gmail.com> Message-ID: <477A9B49.7070701@reifferscheid.org> pigdin-encryption is http://pidgin-encrypt.sourceforge.net/ it has nothing to do with pidgin-otr. pidgin-otr is not available yet in macports. You find details here: http://trac.macosforge.org/projects/macports/ticket/13759 Kind regards Thomas Matrix Mole wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Thomas Reifferscheid wrote: > >> Success. The new portfile got already posted to the >> macports devel mailinglist, so it should be available shortly. >> >> The port is called pidgin-otr. >> > > I've re-sync'd my ports tree and I saw a port called pidgin-encryption > but not one labeled pidgin-otr. I'm guessing that the pidgin-encryption > is the correct port. Otherwise it might be that it hasn't been put into > the port tree for non-devel users yet. I do notice that > pidgin-encryption does not have libotr port as a dependent. I haven't > had a chance to test out the encryption with the encrypted pidgin as of > yet to confirm that it works in concert with the OTR encryption. > > Matrix Mole > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (Darwin) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFHeeCjNtosHRPp48MRAmQkAKCiPNXuo7MHon2DmDdsZrp6IKIBdwCgjykM > YkDPdhafKV7YvX2iE05rgXk= > =eQkw > -----END PGP SIGNATURE----- > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users > From jkh at apple.com Tue Jan 1 12:16:34 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Tue Jan 1 12:16:15 2008 Subject: Emacs and Leopard problems continue In-Reply-To: <887865AB-59C2-436B-99CC-15C7CCE06CF4@cvrti.utah.edu> References: <887865AB-59C2-436B-99CC-15C7CCE06CF4@cvrti.utah.edu> Message-ID: <88E9028D-D470-43E5-BD51-0EE50D328E3F@apple.com> OK, I'll bite. What specifically is wrong with the system emacs that requires folks to struggle so hard to build another copy? It even supports carbon if you add an app wrapper (like the one I just attached - a mere 55k, and most of that is the icon), so I'm not sure what would lead one to struggle so hard to build emacs again. Yes, the macports version should certainly work just on general principle, but that's not the question I'm asking. - Jordan -------------- next part -------------- A non-text attachment was scrubbed... Name: Emacs.app.zip Type: application/zip Size: 24960 bytes Desc: not available Url : http://lists.macosforge.org/pipermail/macports-users/attachments/20080101/4f32ccb6/Emacs.app-0001.zip -------------- next part -------------- p On Dec 31, 2007, at 2:58 PM, Rob MacLeod wrote: > Hi folks, > > I am still struggling with Leopard woes with emacs. > > I was able to get emacs, emacs-devel, and emacs-app all made by > manually applying the patch provided in ticket #13294. emacs made > in the wrong directory while emacs-devel did better and ended up > properly placed. > > However, neither emacs nor emacs-devel launch a new X window when I > start them. I vaguely recall that this was a problem in the past > but I was able with Tiger to get at least one of them (no longer > sure which) to work in the proper X window mode. > > Does anyone know if there are some other settings I need to get a > full functioning X11 based emacs to work? > > In the meantime, I will experiment with emacs-app to see if I can > get it to work the way I am used to... > > Good thing this is the break and I have time to deal with all the > frustrations of Leopard.... > > Happy New Year, > > Rob > > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users From jkh at apple.com Tue Jan 1 12:18:27 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Tue Jan 1 12:18:06 2008 Subject: Ok to switch from Crypt to Shadow Password? In-Reply-To: <7fccb3000801010204h5ae2eafdh59a27ef74e07d24f@mail.gmail.com> References: <7fccb3000801010204h5ae2eafdh59a27ef74e07d24f@mail.gmail.com> Message-ID: <3B72B247-8516-4405-BDB2-21164DE4134F@apple.com> Let's ask a different question: What are you trying to achieve? - Jordan On Jan 1, 2008, at 2:04 AM, Tabitha McNerney wrote: > Hello all -- > > I am happily running Leopard Server and installing MacPorts 1.6.0. > Some of the ports install users in the local directory domain (with > Leopard Apple has officially done away with NetInfo by the way). > There is an option using Workgroup Manager -- a GUI tool only > bundled by Apple with Mac OS X Server, to change the password type > of local directory domain users (for example, the user "ldap" > installed by MacPorts as part of the openldap port) from crypt to > Shadow Password. Has anyone ever tried this and if so are there any > reasons not to switch from crypt to Shadow Password? > > Thank, > > -T.M. > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users From ryandesign at macports.org Tue Jan 1 13:16:11 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Jan 1 13:14:47 2008 Subject: Some confusion about XFree86 In-Reply-To: <7fccb3000801010535q293e1c56pf41e1f80ce19eff3@mail.gmail.com> References: <7fccb3000801010535q293e1c56pf41e1f80ce19eff3@mail.gmail.com> Message-ID: On Jan 1, 2008, at 07:35, Tabitha McNerney wrote: > Its been a while since I've made a bunch of MacPorts, but I have an > Xserve running Leopard Server 10.5.1 and wanted to give it a try > with MacPorts 1.6.0. > > I had problems building XFree86 (I tried to install with the -d > debug option and have saved the output in case it might be useful > to submit to the Trac bug reporting system). Before submitting > anything, I started poking around a bit, looking at some of the > more recent posts about Leopard and XFree86 on the MacPorts mailing > list and also noticing that Apple's X11 app is now based on X.org. > > I noticed that there are also some new (well, new since I last > tried MacPorts 1.5.0 on a Tiger Server system in August of 2007), > ports that seem to be related to X, such as xorg-util-macros and > xorg-xproto (but even these newish ports still depend on XFree86). > > I'm wondering if anyone can provide a little clearer lay of the > land / big picture to help me fill in the missing pieces (with > apologies if there is a lot more details interwoven into these mail > threads). Are there any recommended paths to take with regard to > X11 app or building XFree86 port? Has anyone else had failure > building XFree86 on Leopard Server 10.5.1 or Leopard 10.5.1? I guess the first question is: why do you want to build XFree86? Ports that depend on XFree86 only do so in the event that you have not installed Apple X11. MacPorts installation documents state that you must install Apple X11. Therefore, nobody should need to install the XFree86 port, and in fact, you cannot do so if Apple X11 is already installed, which it is now by default on Leopard. From ryandesign at macports.org Tue Jan 1 13:17:28 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Jan 1 13:16:03 2008 Subject: problem using port to install gnucash on mac 10.5 In-Reply-To: <9153cb050801010540y6a8f53cdw501b27bcb636174f@mail.gmail.com> References: <9153cb050801010540y6a8f53cdw501b27bcb636174f@mail.gmail.com> Message-ID: <38E322B1-12C0-4F25-B921-6010027D3CCE@macports.org> On Jan 1, 2008, at 07:40, Some Guy wrote: > could anyone please help, i have been trying to install gnucash on > my mac but i get this; > > > "---> Building aqbanking with target all [snip] > ld: cycle in dylib re-exports with /usr/X11R6/lib/libGL.dylib You are experiencing this bug: http://trac.macosforge.org/projects/macports/ticket/13173 From ryandesign at macports.org Tue Jan 1 13:18:28 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Jan 1 13:17:00 2008 Subject: Rebuild after Xcode update? In-Reply-To: References: Message-ID: <6D1FBB42-3EBB-4152-BE2B-1635B5686522@macports.org> On Dec 31, 2007, at 23:19, Skip Montanaro wrote: > I'm currently using Xcode 2.2.1 and am having trouble building the > Python > 2.5 port. A little searching suggested I should update my Xcode, > so I'm > downloading the Xcode 2.5 image as I write this. > > Once I've updated my Xcode installation, what should I do on the > MacPorts > side of things? Is there some way to say "rebuild all" or do I > just plow > ahead with the Python 2.5 install and ignore the fact that > everything else > was built up to that point with Xcode 2.2.1? There isn't a way to say "rebuild all" that I know of. I'm not sure if it's necessary. I would begin with the assumption that it is not necessary. Just upgrade to Xcode 2.5 and then install whatever ports you wanted to install. From harrylparker at gmail.com Tue Jan 1 13:49:57 2008 From: harrylparker at gmail.com (Harry Parker) Date: Tue Jan 1 13:48:07 2008 Subject: unable to upgrade port py25-scipy Message-ID: <2a77b9140801011349tf3fe815ne7899ce218c12748@mail.gmail.com> I have been having trouble for several weeks upgrading port py25-scipy. Today I did a port selfupdate and successfully upgraded g95 and tried to upgrade py25-scipy from from version 0.6.0_0. The attempted upgrade ends with: ------- building 'scipy.interpolate.dfitpack' extension error: extension 'scipy.interpolate.dfitpack' has Fortran sources but no Fortran compiler found Warning: the following items did not execute (for py25-scipy): org.macports.destroot org.macports.build Error: Unable to upgrade port: 1 ------- I tried this with the default variant and with the +g95 variant set explicitly. This is on a PowerPC G4 recently upgraded to Mac OS X 10.4.11. Any ideas? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080101/dfbed239/attachment.html From tabithamc at gmail.com Tue Jan 1 15:09:10 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Tue Jan 1 15:07:21 2008 Subject: Ok to switch from Crypt to Shadow Password? In-Reply-To: <3B72B247-8516-4405-BDB2-21164DE4134F@apple.com> References: <7fccb3000801010204h5ae2eafdh59a27ef74e07d24f@mail.gmail.com> <3B72B247-8516-4405-BDB2-21164DE4134F@apple.com> Message-ID: <7fccb3000801011509p6b2af9fdtcf7c43ea37d4bf27@mail.gmail.com> On 1/1/08, Jordan K. Hubbard wrote: > > Let's ask a different question: What are you trying to achieve? > > - Jordan Hi Jordan, You raise a good question, about what I am trying to achieve. My concern is that, after reading Apple's Mac OS X Server Leopard documentation, it strikes me that crypt passwords are less secure compared to other options such as Shadow Passwords, as I quote the Leopard Server OpenDirectory documentation (PDF): User accounts not used on computers that require a crypt password should > have an > Open Directory password or a shadow password. A crypt password is required > only for > logging in to a computer with Mac OS X v10.1 or earlier and on computers > with some > types of UNIX. > > A crypt password is stored as an encrypted value, or hash, in the user > account record in > the directory domain. Because the crypt password can be recovered from the > directory > domain, it is subject to offline attack and is less secure than other > password types. > Maybe I am misinterpreting, but it strikes me that Apple is recommending that, if possible, a crypt password should be last on the list of password type choices. Thanks, T.M. On Jan 1, 2008, at 2:04 AM, Tabitha McNerney wrote: > > > Hello all -- > > > > I am happily running Leopard Server and installing MacPorts 1.6.0. > > Some of the ports install users in the local directory domain (with > > Leopard Apple has officially done away with NetInfo by the way). > > There is an option using Workgroup Manager -- a GUI tool only > > bundled by Apple with Mac OS X Server, to change the password type > > of local directory domain users (for example, the user "ldap" > > installed by MacPorts as part of the openldap port) from crypt to > > Shadow Password. Has anyone ever tried this and if so are there any > > reasons not to switch from crypt to Shadow Password? > > > > Thank, > > > > -T.M. > > _______________________________________________ > > macports-users mailing list > > macports-users@lists.macosforge.org > > http://lists.macosforge.org/mailman/listinfo/macports-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080101/6c286d27/attachment.html From skip at pobox.com Tue Jan 1 15:11:35 2008 From: skip at pobox.com (skip@pobox.com) Date: Tue Jan 1 15:09:53 2008 Subject: gcc42 target bootstrap runs forever? Message-ID: <18298.51367.714305.630046@montanaro.dyndns.org> I executed sudo port upgrade active this morning. It made it through several different port upgrades, but when it got to gcc42 it just seemed to run forever. I don't know how long I let it run before killing it, but it had to be at least two-three hours. I'm going to try installing gcc43 instead. Should the gcc42 upgrade have worked? I've got MacPorts 1.6.0 and Xcode 2.5 installed on a Powerbook G4 running OSX 10.4.11. Thx, -- Skip Montanaro - skip@pobox.com - http://www.webfast.com/~skip/ From ryandesign at macports.org Tue Jan 1 15:36:19 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Jan 1 15:34:53 2008 Subject: gcc42 target bootstrap runs forever? In-Reply-To: <18298.51367.714305.630046@montanaro.dyndns.org> References: <18298.51367.714305.630046@montanaro.dyndns.org> Message-ID: <6977BAF9-F1F3-4AA4-99EC-718276B521DF@macports.org> On Jan 1, 2008, at 17:11, skip@pobox.com wrote: > I executed sudo port upgrade active this morning. It made it through > several different port upgrades, but when it got to gcc42 it just > seemed to > run forever. I don't know how long I let it run before killing it, > but it > had to be at least two-three hours. > > I'm going to try installing gcc43 instead. Should the gcc42 > upgrade have > worked? I've got MacPorts 1.6.0 and Xcode 2.5 installed on a > Powerbook G4 > running OSX 10.4.11. gcc42 took about 6 hours to build and install on my 1.5-GHz PowerBook G4 back when I had it. If your PowerBook is slower, it'll take even longer. You can install with the -v flag to see what's going on, to show that it's still working, and not frozen. sudo port -v upgrade gcc42 From ryandesign at macports.org Tue Jan 1 15:39:11 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Jan 1 15:37:44 2008 Subject: gcc42 target bootstrap runs forever? In-Reply-To: <6977BAF9-F1F3-4AA4-99EC-718276B521DF@macports.org> References: <18298.51367.714305.630046@montanaro.dyndns.org> <6977BAF9-F1F3-4AA4-99EC-718276B521DF@macports.org> Message-ID: On Jan 1, 2008, at 17:11, skip@pobox.com wrote: > I executed sudo port upgrade active this morning. [snip] FYI: "sudo port upgrade active" probably isn't best. You probably want "sudo port upgrade outdated" From skip at pobox.com Tue Jan 1 16:00:26 2008 From: skip at pobox.com (skip@pobox.com) Date: Tue Jan 1 15:58:44 2008 Subject: gcc42 target bootstrap runs forever? In-Reply-To: <6977BAF9-F1F3-4AA4-99EC-718276B521DF@macports.org> References: <18298.51367.714305.630046@montanaro.dyndns.org> <6977BAF9-F1F3-4AA4-99EC-718276B521DF@macports.org> Message-ID: <18298.54298.79567.420660@montanaro.dyndns.org> Ryan> gcc42 took about 6 hours to build and install on my 1.5-GHz Ryan> PowerBook G4 back when I had it. If your PowerBook is slower, Ryan> it'll take even longer. Ah, okay. That's good to know. Yes, my PB is only 800MHz. I'll give it a try with -v so I can see what's happening. Skip From skip at pobox.com Tue Jan 1 16:01:34 2008 From: skip at pobox.com (skip@pobox.com) Date: Tue Jan 1 15:59:47 2008 Subject: gcc42 target bootstrap runs forever? In-Reply-To: References: <18298.51367.714305.630046@montanaro.dyndns.org> <6977BAF9-F1F3-4AA4-99EC-718276B521DF@macports.org> Message-ID: <18298.54366.729333.297004@montanaro.dyndns.org> Ryan> FYI: "sudo port upgrade active" probably isn't best. You probably Ryan> want "sudo port upgrade outdated" I trust that upgrade active will only update those activated items which are out-of-date, yes? Skip From tabithamc at gmail.com Tue Jan 1 16:03:11 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Tue Jan 1 16:01:21 2008 Subject: Some confusion about XFree86 In-Reply-To: References: <7fccb3000801010535q293e1c56pf41e1f80ce19eff3@mail.gmail.com> Message-ID: <7fccb3000801011603y2e0a64a0g66a283356a5637ad@mail.gmail.com> On 1/1/08, Ryan Schmidt wrote: > > On Jan 1, 2008, at 07:35, Tabitha McNerney wrote: > > > Its been a while since I've made a bunch of MacPorts, but I have an > > Xserve running Leopard Server 10.5.1 and wanted to give it a try > > with MacPorts 1.6.0. > > > > I had problems building XFree86 (I tried to install with the -d > > debug option and have saved the output in case it might be useful > > to submit to the Trac bug reporting system). Before submitting > > anything, I started poking around a bit, looking at some of the > > more recent posts about Leopard and XFree86 on the MacPorts mailing > > list and also noticing that Apple's X11 app is now based on X.org. > > > > I noticed that there are also some new (well, new since I last > > tried MacPorts 1.5.0 on a Tiger Server system in August of 2007), > > ports that seem to be related to X, such as xorg-util-macros and > > xorg-xproto (but even these newish ports still depend on XFree86). > > > > I'm wondering if anyone can provide a little clearer lay of the > > land / big picture to help me fill in the missing pieces (with > > apologies if there is a lot more details interwoven into these mail > > threads). Are there any recommended paths to take with regard to > > X11 app or building XFree86 port? Has anyone else had failure > > building XFree86 on Leopard Server 10.5.1 or Leopard 10.5.1? > > I guess the first question is: why do you want to build XFree86? > Ports that depend on XFree86 only do so in the event that you have > not installed Apple X11. MacPorts installation documents state that > you must install Apple X11. Therefore, nobody should need to install > the XFree86 port, and in fact, you cannot do so if Apple X11 is > already installed, which it is now by default on Leopard. Ryan, this is, in hindsight, a good question. I had, by habit in the past, been building the Mac(Darwin) Port, XFree86, mostly because IIRC the Apple X11 app was historically not open source totally and I was concerned about moving to a possible proprietary application. But, based on what I've read yesterday, I guess X11 from Apple has been re-based on X.org now so I can see how that would, in essence, deprecate the need to build XFree86. With that being said, so if XFree86 is pretty much no longer needed in lieu of the changes to Apple's X11 app on Leopard, then what about some of the X Windows ports such as wireshark? Checking out the dependencies for wireshark, I can trace its dependencies to the XFree86 port: $ ports deps wireshark > wireshark has library dependencies on: > glib2 > gtk2 > openssl > libpcap > zlib > ... $ port deps gtk2 > gtk2 has library dependencies on: > cairo > fontconfig > freetype > glib2 > jpeg > tiff > libiconv > libpng > atk > pango > gettext > render > zlib > xrender > xorg > ... $ port deps pango > glib2 > XFree86 > Xft2 > cairo > fontconfig > Thanks for the clearing some of my confusion. Best regards, T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080101/06058e15/attachment.html From ryandesign at macports.org Tue Jan 1 16:14:27 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Jan 1 16:13:00 2008 Subject: Some confusion about XFree86 In-Reply-To: <7fccb3000801011603y2e0a64a0g66a283356a5637ad@mail.gmail.com> References: <7fccb3000801010535q293e1c56pf41e1f80ce19eff3@mail.gmail.com> <7fccb3000801011603y2e0a64a0g66a283356a5637ad@mail.gmail.com> Message-ID: <10E62387-1073-44E8-A181-2C3BDB0024B6@macports.org> On Jan 1, 2008, at 18:03, Tabitha McNerney wrote: > On 1/1/08, Ryan Schmidt wrote: > >> On Jan 1, 2008, at 07:35, Tabitha McNerney wrote: >> >> > Its been a while since I've made a bunch of MacPorts, but I have an >> > Xserve running Leopard Server 10.5.1 and wanted to give it a try >> > with MacPorts 1.6.0. >> > >> > I had problems building XFree86 (I tried to install with the -d >> > debug option and have saved the output in case it might be useful >> > to submit to the Trac bug reporting system). Before submitting >> > anything, I started poking around a bit, looking at some of the >> > more recent posts about Leopard and XFree86 on the MacPorts mailing >> > list and also noticing that Apple's X11 app is now based on X.org. >> > >> > I noticed that there are also some new (well, new since I last >> > tried MacPorts 1.5.0 on a Tiger Server system in August of 2007), >> > ports that seem to be related to X, such as xorg-util-macros and >> > xorg-xproto (but even these newish ports still depend on XFree86). >> > >> > I'm wondering if anyone can provide a little clearer lay of the >> > land / big picture to help me fill in the missing pieces (with >> > apologies if there is a lot more details interwoven into these mail >> > threads). Are there any recommended paths to take with regard to >> > X11 app or building XFree86 port? Has anyone else had failure >> > building XFree86 on Leopard Server 10.5.1 or Leopard 10.5.1? >> >> I guess the first question is: why do you want to build XFree86? >> Ports that depend on XFree86 only do so in the event that you have >> not installed Apple X11. MacPorts installation documents state that >> you must install Apple X11. Therefore, nobody should need to install >> the XFree86 port, and in fact, you cannot do so if Apple X11 is >> already installed, which it is now by default on Leopard. > > Ryan, this is, in hindsight, a good question. I had, by habit in > the past, been building the Mac(Darwin) Port, XFree86, mostly > because IIRC the Apple X11 app was historically not open source > totally and I was concerned about moving to a possible proprietary > application. But, based on what I've read yesterday, I guess X11 > from Apple has been re-based on X.org now so I can see how that > would, in essence, deprecate the need to build XFree86. > > With that being said, so if XFree86 is pretty much no longer needed > in lieu of the changes to Apple's X11 app on Leopard, then what > about some of the X Windows ports such as wireshark? Checking out > the dependencies for wireshark, I can trace its dependencies to the > XFree86 port: > > $ ports deps wireshark > wireshark has library dependencies on: > glib2 > gtk2 > openssl > libpcap > zlib > > ... > > $ port deps gtk2 > gtk2 has library dependencies on: > cairo > fontconfig > freetype > glib2 > jpeg > tiff > libiconv > libpng > atk > pango > gettext > render > zlib > xrender > xorg > > ... > > $ port deps pango > glib2 > XFree86 > Xft2 > cairo > fontconfig > > > Thanks for the clearing some of my confusion. As I explained, "Ports that depend on XFree86 only do so in the event that you have not installed Apple X11." To take your example of pango, look at how the dependency is defined in the pango portfile: depends_lib \ ... lib:libX11.6:XFree86 \ That means: it depends on the library libX11.6, and if that library does not exist, then install it via the XFree86 port. libX11.6 will already exist on your system if Apple X11 is installed, therefore the XFree86 port will not be installed. From tabithamc at gmail.com Tue Jan 1 16:23:14 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Tue Jan 1 16:21:24 2008 Subject: Some confusion about XFree86 In-Reply-To: <10E62387-1073-44E8-A181-2C3BDB0024B6@macports.org> References: <7fccb3000801010535q293e1c56pf41e1f80ce19eff3@mail.gmail.com> <7fccb3000801011603y2e0a64a0g66a283356a5637ad@mail.gmail.com> <10E62387-1073-44E8-A181-2C3BDB0024B6@macports.org> Message-ID: <7fccb3000801011623q3b8c714cmb7235043a7121c91@mail.gmail.com> On 1/1/08, Ryan Schmidt wrote: > > On Jan 1, 2008, at 18:03, Tabitha McNerney wrote: [SNIP] As I explained, "Ports that depend on XFree86 only do so in the event > that you have not installed Apple X11." To take your example of > pango, look at how the dependency is defined in the pango portfile: > > depends_lib \ > ... > lib:libX11.6:XFree86 \ > > That means: it depends on the library libX11.6, and if that library > does not exist, then install it via the XFree86 port. libX11.6 will > already exist on your system if Apple X11 is installed, therefore the > XFree86 port will not be installed. > Hmm ... ok, I must have done something without realizing it or basing off of my Tiger documentation because I have the X11 app and I could swear that I installed the X11 headers from the Leopard Server DVD. Thanks again for reinforcing this. -T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080101/721b05ac/attachment-0001.html From jkh at apple.com Tue Jan 1 17:39:02 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Tue Jan 1 17:38:41 2008 Subject: Ok to switch from Crypt to Shadow Password? In-Reply-To: <7fccb3000801011509p6b2af9fdtcf7c43ea37d4bf27@mail.gmail.com> References: <7fccb3000801010204h5ae2eafdh59a27ef74e07d24f@mail.gmail.com> <3B72B247-8516-4405-BDB2-21164DE4134F@apple.com> <7fccb3000801011509p6b2af9fdtcf7c43ea37d4bf27@mail.gmail.com> Message-ID: <15FA2886-6246-4108-A45D-C2D552AC287B@apple.com> I see your confusion. The documentation only mentions Crypt passwords as and old-style way of leaving passwords around if you need interoperability with 10.0 or 10.1 machines. By default, you're already using a shadow password and have been for quite a few releases now. - Jordan On Jan 1, 2008, at 3:09 PM, Tabitha McNerney wrote: > > On 1/1/08, Jordan K. Hubbard wrote: > Let's ask a different question: What are you trying to achieve? > > - Jordan > > Hi Jordan, > > You raise a good question, about what I am trying to achieve. My > concern is that, after reading Apple's Mac OS X Server Leopard > documentation, it strikes me that crypt passwords are less secure > compared to other options such as Shadow Passwords, as I quote the > Leopard Server OpenDirectory documentation (PDF): > > User accounts not used on computers that require a crypt password > should have an > Open Directory password or a shadow password. A crypt password is > required only for > logging in to a computer with Mac OS X v10.1 or earlier and on > computers with some > types of UNIX. > > A crypt password is stored as an encrypted value, or hash, in the > user account record in > the directory domain. Because the crypt password can be recovered > from the directory > domain, it is subject to offline attack and is less secure than > other password types. > > Maybe I am misinterpreting, but it strikes me that Apple is > recommending that, if possible, a crypt password should be last on > the list of password type choices. > > Thanks, > > T.M. > > On Jan 1, 2008, at 2:04 AM, Tabitha McNerney wrote: > > > Hello all -- > > > > I am happily running Leopard Server and installing MacPorts 1.6.0. > > Some of the ports install users in the local directory domain (with > > Leopard Apple has officially done away with NetInfo by the way). > > There is an option using Workgroup Manager -- a GUI tool only > > bundled by Apple with Mac OS X Server, to change the password type > > of local directory domain users (for example, the user "ldap" > > installed by MacPorts as part of the openldap port) from crypt to > > Shadow Password. Has anyone ever tried this and if so are there any > > reasons not to switch from crypt to Shadow Password? > > > > Thank, > > > > -T.M. > > _______________________________________________ > > macports-users mailing list > > macports-users@lists.macosforge.org > > http://lists.macosforge.org/mailman/listinfo/macports-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080101/24e9fa48/attachment.html From harrylparker at gmail.com Tue Jan 1 19:02:50 2008 From: harrylparker at gmail.com (Harry Parker) Date: Tue Jan 1 19:01:01 2008 Subject: unable to upgrade port py25-scipy In-Reply-To: <2a77b9140801011349tf3fe815ne7899ce218c12748@mail.gmail.com> References: <2a77b9140801011349tf3fe815ne7899ce218c12748@mail.gmail.com> Message-ID: <2a77b9140801011902r3e72f5canc5def3df77dc7cb4@mail.gmail.com> I submitted this to TRAC as ticket # 13776. -- Harry On Jan 1, 2008 4:49 PM, Harry Parker wrote: > I have been having trouble for several weeks upgrading port py25-scipy. > > Today I did a port selfupdate and successfully upgraded g95 and tried to > upgrade py25-scipy from from version 0.6.0_0. > The attempted upgrade ends with: > > ------- > building 'scipy.interpolate.dfitpack' extension > error: extension 'scipy.interpolate.dfitpack' has Fortran sources but no > Fortran compiler found > > Warning: the following items did not execute (for py25-scipy): > org.macports.destroot org.macports.build > Error: Unable to upgrade port: 1 > ------- > > I tried this with the default variant and with the +g95 variant set > explicitly. > This is on a PowerPC G4 recently upgraded to Mac OS X 10.4.11. > > Any ideas? > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080101/3c0b27a8/attachment.html From boeyms at macports.org Tue Jan 1 19:36:13 2008 From: boeyms at macports.org (Boey Maun Suang) Date: Tue Jan 1 19:34:21 2008 Subject: Rebuild after Xcode update? In-Reply-To: <6D1FBB42-3EBB-4152-BE2B-1635B5686522@macports.org> References: <6D1FBB42-3EBB-4152-BE2B-1635B5686522@macports.org> Message-ID: <21757.203.20.35.28.1199244973.squirrel@webmail.tuffmail.net> On Wed, January 2, 2008 8:18 am, Ryan Schmidt wrote: > > On Dec 31, 2007, at 23:19, Skip Montanaro wrote: > >> I'm currently using Xcode 2.2.1 and am having trouble building the >> Python >> 2.5 port. A little searching suggested I should update my Xcode, >> so I'm >> downloading the Xcode 2.5 image as I write this. >> >> Once I've updated my Xcode installation, what should I do on the >> MacPorts >> side of things? Is there some way to say "rebuild all" or do I >> just plow >> ahead with the Python 2.5 install and ignore the fact that >> everything else >> was built up to that point with Xcode 2.2.1? > > There isn't a way to say "rebuild all" that I know of. I'm not sure > if it's necessary. I would begin with the assumption that it is not > necessary. Just upgrade to Xcode 2.5 and then install whatever ports > you wanted to install. I think that, should you find it necessary, a forced upgrade of all your installed ports (sudo port -ufn upgrade installed) has the effect of rebuilding everything that you have installed. (The -n is needed to avoid unnecessary multiple rebuilds of ports that are dependencies of others -- this is a bug in MacPorts; -u is needed to uninstall the installed ports so that the the automatic reinstallation works properly). As for the compatibility of code built with Xcode 2.5 with that built with Xcode 2.2.1, I think that they should be largely compatible, as my reading of the release notes from 2.2.1 to 2.5 is that there have only been bugfixes and feature enhancements to Xcode's GCC in that time, rather than any deliberate compatibility-breaking changes. If that's the case, any incompatibilities ought to be due to incorrect code produced by Xcode. Kind regards, Maun Suang -- Boey Maun Suang Email: boeyms@macports.org From jkh at apple.com Tue Jan 1 19:38:45 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Tue Jan 1 19:36:53 2008 Subject: Some confusion about XFree86 In-Reply-To: <10E62387-1073-44E8-A181-2C3BDB0024B6@macports.org> References: <7fccb3000801010535q293e1c56pf41e1f80ce19eff3@mail.gmail.com> <7fccb3000801011603y2e0a64a0g66a283356a5637ad@mail.gmail.com> <10E62387-1073-44E8-A181-2C3BDB0024B6@macports.org> Message-ID: <9AE497DC-41B5-495F-99C1-A86B11E9170F@apple.com> On Jan 1, 2008, at 4:14 PM, Ryan Schmidt wrote: > As I explained, "Ports that depend on XFree86 only do so in the > event that you have not installed Apple X11." To take your example > of pango, look at how the dependency is defined in the pango portfile: I think Tabitha's question suggests another, however. Given that the center of gravity has clearly shifted over to X.org (and the fact that Jeremy Huddleston and Ben Byer have substantially evolved that code base over what shipped in Leopard, said collection of packages / git branch checkouts needing a bit of manual labor to currently install), why is XFree86 the fall back at all? Even if the intention is not to install it, it seems like there should still be a more sensible default now. - Jordan From matrixm at gmail.com Tue Jan 1 19:40:10 2008 From: matrixm at gmail.com (Matrix Mole) Date: Tue Jan 1 19:38:23 2008 Subject: Pidgin with OTR? In-Reply-To: <477A9B49.7070701@reifferscheid.org> References: <4776C0FE.1010604@gmail.com> <4776F44C.8030804@reifferscheid.org> <47779628.3090005@reifferscheid.org> <4779E0A3.3090106@gmail.com> <477A9B49.7070701@reifferscheid.org> Message-ID: <477B079A.40001@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thomas Reifferscheid wrote: > pigdin-encryption is http://pidgin-encrypt.sourceforge.net/ it has nothing > to do with pidgin-otr. Thank you for pointing that out, I didn't realize that they were two distinct different encryption builds. > pidgin-otr is not available yet in macports. You find details here: > http://trac.macosforge.org/projects/macports/ticket/13759 Using the tarball file from that site, where would I place it so that I could then install it into my port tree? I'd be more than willing to install the build and report back any bugs I run across while using it. Matrix Mole -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHeweaNtosHRPp48MRAigAAJ9uXSSqMZ4NI43RbNupG2/pLZ4IKQCeIt/H REecfnukwpcX0o5nNapwC8Q= =wdqE -----END PGP SIGNATURE----- From tabithamc at gmail.com Tue Jan 1 20:01:26 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Tue Jan 1 19:59:37 2008 Subject: Ok to switch from Crypt to Shadow Password? In-Reply-To: <15FA2886-6246-4108-A45D-C2D552AC287B@apple.com> References: <7fccb3000801010204h5ae2eafdh59a27ef74e07d24f@mail.gmail.com> <3B72B247-8516-4405-BDB2-21164DE4134F@apple.com> <7fccb3000801011509p6b2af9fdtcf7c43ea37d4bf27@mail.gmail.com> <15FA2886-6246-4108-A45D-C2D552AC287B@apple.com> Message-ID: <7fccb3000801012001r2baa29a9g547dd19e3052ee69@mail.gmail.com> On 1/1/08, Jordan K. Hubbard wrote: > > I see your confusion. The documentation only mentions Crypt passwords as > and old-style way of leaving passwords around if you need interoperability > with 10.0 or 10.1 machines. By default, you're already using a shadow > password and have been for quite a few releases now. > Jordan, appreciate the further clarity. Quick question then (just to make sure I'm ultra clear) -- even if a MacPort installs a new entry in the local directory domain with a "Crypt Password" type, what you're saying is that in reality, under Leopard Server (and the past few versions of Mac OS X Server) this password is a Shadow Password disguised to the system as a Crypt Password? I ask because using Workgroup Manager on Leopard Server, I can select the user that was installed by the MacPort (for example, take the openldap MacPort which installs a local directory domain entry with the username "ldap", UID "500" and a User Password Type of "Crypt Password" and I can select the pop-up menu with the "Crypt Password" selection and change the type to either "Shadow Password" or "OpenDirectory" because I am also running an OpenDirectory Master on the same machine). I appreciate the insight as this is actually quite interesting! Thanks, T.M. - Jordan > > On Jan 1, 2008, at 3:09 PM, Tabitha McNerney wrote: > > > On 1/1/08, Jordan K. Hubbard wrote: > > > > Let's ask a different question: What are you trying to achieve? > > > > - Jordan > > > Hi Jordan, > > You raise a good question, about what I am trying to achieve. My concern > is that, after reading Apple's Mac OS X Server Leopard documentation, it > strikes me that crypt passwords are less secure compared to other options > such as Shadow Passwords, as I quote the Leopard Server OpenDirectory > documentation (PDF): > > User accounts not used on computers that require a crypt password should > > have an > > Open Directory password or a shadow password. A crypt password is > > required only for > > logging in to a computer with Mac OS X v10.1 or earlier and on computers > > with some > > types of UNIX. > > > > A crypt password is stored as an encrypted value, or hash, in the user > > account record in > > the directory domain. Because the crypt password can be recovered from > > the directory > > domain, it is subject to offline attack and is less secure than other > > password types. > > > > Maybe I am misinterpreting, but it strikes me that Apple is recommending > that, if possible, a crypt password should be last on the list of password > type choices. > > Thanks, > > T.M. > > On Jan 1, 2008, at 2:04 AM, Tabitha McNerney wrote: > > > > > Hello all -- > > > > > > I am happily running Leopard Server and installing MacPorts 1.6.0. > > > Some of the ports install users in the local directory domain (with > > > Leopard Apple has officially done away with NetInfo by the way). > > > There is an option using Workgroup Manager -- a GUI tool only > > > bundled by Apple with Mac OS X Server, to change the password type > > > of local directory domain users (for example, the user "ldap" > > > installed by MacPorts as part of the openldap port) from crypt to > > > Shadow Password. Has anyone ever tried this and if so are there any > > > reasons not to switch from crypt to Shadow Password? > > > > > > Thank, > > > > > > -T.M. > > > _______________________________________________ > > > macports-users mailing list > > > macports-users@lists.macosforge.org > > > http://lists.macosforge.org/mailman/listinfo/macports-users > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080101/92df5cd4/attachment-0001.html From jkh at apple.com Tue Jan 1 20:32:31 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Tue Jan 1 20:32:09 2008 Subject: Ok to switch from Crypt to Shadow Password? In-Reply-To: <7fccb3000801012001r2baa29a9g547dd19e3052ee69@mail.gmail.com> References: <7fccb3000801010204h5ae2eafdh59a27ef74e07d24f@mail.gmail.com> <3B72B247-8516-4405-BDB2-21164DE4134F@apple.com> <7fccb3000801011509p6b2af9fdtcf7c43ea37d4bf27@mail.gmail.com> <15FA2886-6246-4108-A45D-C2D552AC287B@apple.com> <7fccb3000801012001r2baa29a9g547dd19e3052ee69@mail.gmail.com> Message-ID: On Jan 1, 2008, at 8:01 PM, Tabitha McNerney wrote: > Jordan, appreciate the further clarity. Quick question then (just to > make sure I'm ultra clear) -- even if a MacPort installs a new entry > in the local directory domain with a "Crypt Password" type, what > you're saying is that in reality, under Leopard Server (and the past > few versions of Mac OS X Server) this password is a Shadow Password > disguised to the system as a Crypt Password? I ask because using > Workgroup Manager on Leopard Server, I can select the user that was > installed by the MacPort (for example, take the openldap MacPort > which installs a local directory domain entry with the username > "ldap", UID "500" and a User Password Type of "Crypt Password" and I > can select the pop-up menu with the "Crypt Password" selection and > change the type to either "Shadow Password" or "OpenDirectory" > because I am also running an OpenDirectory Master on the same > machine). I'm not sure how MacPorts installs user records on Leopard (I've never looked). Presumably, it just drops a plist file into /var/db/dslocal/ nodes/Default/users since that's all you need to do in Leopard. The contents of that plist file, however, can specify a number of different password types - "it all depends" is about the best answer I can give you there. You should look at the authentication_authority array in the user plists you're wondering about and verify that they're doing whatever it is you want them to do (this is an array value, so there are multiple options here). I'd be surprised if MacPorts was using some obsolete password types, but you never know I guess. - Jordan From ryandesign at macports.org Tue Jan 1 20:39:54 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Tue Jan 1 20:45:08 2008 Subject: Ok to switch from Crypt to Shadow Password? In-Reply-To: References: <7fccb3000801010204h5ae2eafdh59a27ef74e07d24f@mail.gmail.com> <3B72B247-8516-4405-BDB2-21164DE4134F@apple.com> <7fccb3000801011509p6b2af9fdtcf7c43ea37d4bf27@mail.gmail.com> <15FA2886-6246-4108-A45D-C2D552AC287B@apple.com> <7fccb3000801012001r2baa29a9g547dd19e3052ee69@mail.gmail.com> Message-ID: <14A27BBE-CB12-403B-9878-D01AA8FFA227@macports.org> On Jan 1, 2008, at 22:32, Jordan K. Hubbard wrote: > On Jan 1, 2008, at 8:01 PM, Tabitha McNerney wrote: > >> Jordan, appreciate the further clarity. Quick question then (just >> to make sure I'm ultra clear) -- even if a MacPort installs a new >> entry in the local directory domain with a "Crypt Password" type, >> what you're saying is that in reality, under Leopard Server (and >> the past few versions of Mac OS X Server) this password is a >> Shadow Password disguised to the system as a Crypt Password? I ask >> because using Workgroup Manager on Leopard Server, I can select >> the user that was installed by the MacPort (for example, take the >> openldap MacPort which installs a local directory domain entry >> with the username "ldap", UID "500" and a User Password Type of >> "Crypt Password" and I can select the pop-up menu with the "Crypt >> Password" selection and change the type to either "Shadow >> Password" or "OpenDirectory" because I am also running an >> OpenDirectory Master on the same machine). > > I'm not sure how MacPorts installs user records on Leopard (I've > never looked). Presumably, it just drops a plist file into /var/db/ > dslocal/nodes/Default/users since that's all you need to do in > Leopard. The contents of that plist file, however, can specify a > number of different password types - "it all depends" is about the > best answer I can give you there. You should look at the > authentication_authority array in the user plists you're wondering > about and verify that they're doing whatever it is you want them to > do (this is an array value, so there are multiple options here). > I'd be surprised if MacPorts was using some obsolete password > types, but you never know I guess. It looks like MacPorts uses dscl to create users and groups, on all versions of Mac OS X. See src/port1.0/portutil.tcl. proc adduser {name args} { global os.platform set passwd {*} set uid [nextuid] set gid [existsgroup nogroup] set realname ${name} set home /dev/null set shell /dev/null foreach arg $args { if {[regexp {([a-z]*)=(.*)} $arg match key val]} { regsub -all " " ${val} "\\ " val set $key $val } } if {[existsuser ${name}] != 0 || [existsuser ${uid}] != 0} { return } if {${os.platform} eq "darwin"} { exec dscl . -create /Users/${name} Password ${passwd} exec dscl . -create /Users/${name} UniqueID ${uid} exec dscl . -create /Users/${name} PrimaryGroupID ${gid} exec dscl . -create /Users/${name} RealName ${realname} exec dscl . -create /Users/${name} NFSHomeDirectory ${home} exec dscl . -create /Users/${name} UserShell ${shell} } else { # XXX adduser is only available for darwin, add more support here ui_warn "WARNING: adduser is not implemented on $ {os.platform}." ui_warn "The requested user was not created." } } From tabithamc at gmail.com Tue Jan 1 20:47:41 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Tue Jan 1 20:45:49 2008 Subject: Ok to switch from Crypt to Shadow Password? In-Reply-To: <14A27BBE-CB12-403B-9878-D01AA8FFA227@macports.org> References: <7fccb3000801010204h5ae2eafdh59a27ef74e07d24f@mail.gmail.com> <3B72B247-8516-4405-BDB2-21164DE4134F@apple.com> <7fccb3000801011509p6b2af9fdtcf7c43ea37d4bf27@mail.gmail.com> <15FA2886-6246-4108-A45D-C2D552AC287B@apple.com> <7fccb3000801012001r2baa29a9g547dd19e3052ee69@mail.gmail.com> <14A27BBE-CB12-403B-9878-D01AA8FFA227@macports.org> Message-ID: <7fccb3000801012047x360ce69as3da24aa7f8dd7b9@mail.gmail.com> On 1/1/08, Ryan Schmidt wrote: > > > On Jan 1, 2008, at 22:32, Jordan K. Hubbard wrote: > > > On Jan 1, 2008, at 8:01 PM, Tabitha McNerney wrote: > > > >> Jordan, appreciate the further clarity. Quick question then (just > >> to make sure I'm ultra clear) -- even if a MacPort installs a new > >> entry in the local directory domain with a "Crypt Password" type, > >> what you're saying is that in reality, under Leopard Server (and > >> the past few versions of Mac OS X Server) this password is a > >> Shadow Password disguised to the system as a Crypt Password? I ask > >> because using Workgroup Manager on Leopard Server, I can select > >> the user that was installed by the MacPort (for example, take the > >> openldap MacPort which installs a local directory domain entry > >> with the username "ldap", UID "500" and a User Password Type of > >> "Crypt Password" and I can select the pop-up menu with the "Crypt > >> Password" selection and change the type to either "Shadow > >> Password" or "OpenDirectory" because I am also running an > >> OpenDirectory Master on the same machine). > > > > I'm not sure how MacPorts installs user records on Leopard (I've > > never looked). Presumably, it just drops a plist file into /var/db/ > > dslocal/nodes/Default/users since that's all you need to do in > > Leopard. The contents of that plist file, however, can specify a > > number of different password types - "it all depends" is about the > > best answer I can give you there. You should look at the > > authentication_authority array in the user plists you're wondering > > about and verify that they're doing whatever it is you want them to > > do (this is an array value, so there are multiple options here). > > I'd be surprised if MacPorts was using some obsolete password > > types, but you never know I guess. > > It looks like MacPorts uses dscl to create users and groups, on all > versions of Mac OS X. See src/port1.0/portutil.tcl. > > proc adduser {name args} { > global os.platform > set passwd {*} > set uid [nextuid] > set gid [existsgroup nogroup] > set realname ${name} > set home /dev/null > set shell /dev/null > > foreach arg $args { > if {[regexp {([a-z]*)=(.*)} $arg match key val]} { > regsub -all " " ${val} "\\ " val > set $key $val > } > } > > if {[existsuser ${name}] != 0 || [existsuser ${uid}] != 0} { > return > } > > if {${os.platform} eq "darwin"} { > exec dscl . -create /Users/${name} Password ${passwd} I just checked the man page for dscl on Leopard Server (sorry I don't have a copy of Leopard (non-Server) but its probably the same). It strikes me that dscl is just fine (it would be a major hassle to change MacPorts ports) and it should be left up to the system administrator who takes responsibility for installing and maintaining MacPorts on a Mac OS X / Mac OS X Server system to decide what to do with passwords after the installation by MacPorts: passwd > Usage: passwd user_path [new_pasword | old_password new_pasword] > > Changes a password for a user. The user must be specified by full > path, not just a username. If you are authenticated to the node (either by > specifying the -u > and -P flags or by using the auth command when in interactive node) > then you can simply specify a new password. If you are not authenticated > then the user's old > password must be specified. If passwords are not specified while in > interactive mode, you will be prompted for them. > Thanks for touching on this subject, T.M. exec dscl . -create /Users/${name} UniqueID ${uid} > exec dscl . -create /Users/${name} PrimaryGroupID ${gid} > exec dscl . -create /Users/${name} RealName ${realname} > exec dscl . -create /Users/${name} NFSHomeDirectory ${home} > exec dscl . -create /Users/${name} UserShell ${shell} > } else { > # XXX adduser is only available for darwin, add more support > here > ui_warn "WARNING: adduser is not implemented on $ > {os.platform}." > ui_warn "The requested user was not created." > } > } > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080101/84f31370/attachment.html From rsync at reifferscheid.org Wed Jan 2 00:10:24 2008 From: rsync at reifferscheid.org (Thomas Reifferscheid) Date: Wed Jan 2 00:08:30 2008 Subject: Pidgin with OTR? In-Reply-To: <477B079A.40001@gmail.com> References: <4776C0FE.1010604@gmail.com> <4776F44C.8030804@reifferscheid.org> <47779628.3090005@reifferscheid.org> <4779E0A3.3090106@gmail.com> <477A9B49.7070701@reifferscheid.org> <477B079A.40001@gmail.com> Message-ID: <477B46F0.6010602@reifferscheid.org> You can have the portfile in a local repository. You find all the details here: http://guide.macports.org/#development.local-repositories However, it would be more easier, if someone would commit the port to the global macports repository. Kind regards Thomas Reifferscheid Matrix Mole wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Thomas Reifferscheid wrote: > >> pigdin-encryption is http://pidgin-encrypt.sourceforge.net/ it has nothing >> to do with pidgin-otr. >> > > Thank you for pointing that out, I didn't realize that they were two > distinct different encryption builds. > > >> pidgin-otr is not available yet in macports. You find details here: >> http://trac.macosforge.org/projects/macports/ticket/13759 >> > > Using the tarball file from that site, where would I place it so that I > could then install it into my port tree? I'd be more than willing to > install the build and report back any bugs I run across while using it. > > Matrix Mole > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (Darwin) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFHeweaNtosHRPp48MRAigAAJ9uXSSqMZ4NI43RbNupG2/pLZ4IKQCeIt/H > REecfnukwpcX0o5nNapwC8Q= > =wdqE > -----END PGP SIGNATURE----- > From ludwig at fh-worms.de Wed Jan 2 00:18:28 2008 From: ludwig at fh-worms.de (Christoph Ludwig) Date: Wed Jan 2 00:16:43 2008 Subject: gpgme variant for mutt-devel? Message-ID: <20080102081828.GB3170@castellio.ztt.fh-worms.de> Hi, I have a request: I'd be grateful if support for mutt's gpgme crypto backend was added to the port mutt-devel, at least as a variant. Unfortunately, I am swamped so I do not have the time to come up with a portfile patch myself. I'd like to take advantage of the bug fixes that went into mutt over the last year, but right now I am stuck at 1.5.11. Since I need S/MIME support and I am not satisfied with the S/MIME support provided by the "classic" crypto backend that calls openssl's command line tools, I cannot switch to the mutt-devel port. Thanks Christoph -- FH Worms - University of Applied Sciences Fachbereich Informatik / Telekommunikation Erenburgerstr. 19, 67549 Worms, Germany From afb at macports.org Wed Jan 2 01:26:00 2008 From: afb at macports.org (=?ISO-8859-1?Q?Anders_F_Bj=F6rklund?=) Date: Wed Jan 2 01:24:24 2008 Subject: Rebuild after Xcode update? In-Reply-To: <21757.203.20.35.28.1199244973.squirrel@webmail.tuffmail.net> References: <6D1FBB42-3EBB-4152-BE2B-1635B5686522@macports.org> <21757.203.20.35.28.1199244973.squirrel@webmail.tuffmail.net> Message-ID: <624c7a7b8979f04ef4633b9c442a20fe@macports.org> Boey Maun Suang wrote: > As for the compatibility of code built with Xcode 2.5 with that built > with > Xcode 2.2.1, I think that they should be largely compatible, as my > reading > of the release notes from 2.2.1 to 2.5 is that there have only been > bugfixes and feature enhancements to Xcode's GCC in that time, rather > than > any deliberate compatibility-breaking changes. If that's the case, any > incompatibilities ought to be due to incorrect code produced by Xcode. Xcode 2.4.1 is largely compatible, and fixes the Intel 64-bit issues that makes using Xcode 2.2.1 not work for compiling some ports that want it... Xcode 2.5, on the other hand, introduces some breaking changes so that it can run in a prefix on Leopard - such as not including /usr/share/libtool: http://trac.macports.org/projects/macports/ticket/13334 http://trac.macports.org/projects/macports/ticket/13736 --anders From ramercer at gmail.com Wed Jan 2 03:37:30 2008 From: ramercer at gmail.com (Adam Mercer) Date: Wed Jan 2 03:35:38 2008 Subject: unable to upgrade port py25-scipy In-Reply-To: <2a77b9140801011349tf3fe815ne7899ce218c12748@mail.gmail.com> References: <2a77b9140801011349tf3fe815ne7899ce218c12748@mail.gmail.com> Message-ID: <799406d60801020337v3fc42d1ev2c1aa3527ab7fbe7@mail.gmail.com> On Jan 1, 2008 9:49 PM, Harry Parker wrote: > ------- > building 'scipy.interpolate.dfitpack' extension > error: extension 'scipy.interpolate.dfitpack' has Fortran sources but no > Fortran compiler found > > Warning: the following items did not execute (for py25-scipy): > org.macports.destroot org.macports.build > Error: Unable to upgrade port: 1 > ------- Already requested this in #13776 but the full debug output of the build would be very helpful here. Cheers Adam From mjs at beebo.org Wed Jan 2 06:16:53 2008 From: mjs at beebo.org (Michael Stillwell) Date: Wed Jan 2 06:15:01 2008 Subject: what configuration files are read? In-Reply-To: References: <37CF4227-52D1-4159-9BD8-31451BAA84C7@beebo.org> Message-ID: <140eba4e0801020616r3dbd7b28k2e7ffe56cbfa8bf9@mail.gmail.com> On Jan 1, 2008 12:00 AM, Ryan Schmidt wrote: > > On Dec 31, 2007, at 06:48, Michael Stillwell wrote: > > > How does "port" figure out which configuration files to read? Mine > > is now trying to get configuration information from a non-existent > > file: [ ... ] > > Issue #1: The reason why your two installations are conflicting with > one another is that they both installed their Tcl components to / > Library/Tcl/macports1.0, and the $HOME/scratch/ports instalation's / > Library/Tcl/macports1.0 has overwritten the one from $HOME/Ports. > > [ ... ] > > You could bypass all the arguments and just do it yourself. You > should reinstall both of your installations (or at least the /Ports > one, since its /Library/Tcl/macports1.0 is gone), making sure that at > least one, or perhaps both, of them put their Tcl directory > elsewhere, for example: > > PATH=/usr/bin:/usr/sbin:/bin:/sbin ./configure \ > --prefix=$HOME/Ports \ > --with-tclpackage=$HOME/Ports/share/macports/Tcl Thanks; this worked perfectly. Is it possible to improve the --prefix documentation? "./configure --help" doesn't make it clear that 99% (but not 100%) of the installed files will go into the specified directory, and it's somewhat unexpected that the crucial missing directory of files is configured via --with-tclinclude. --M. -- http://beebo.org +44 78 2118 9049 From hashashin at gmail.com Wed Jan 2 07:16:13 2008 From: hashashin at gmail.com (=?ISO-8859-1?Q?Alberto_Sim=F5es?=) Date: Wed Jan 2 07:14:20 2008 Subject: Activating stalls Message-ID: <2b670b7e0801020716u72327632q2424aa559169491a@mail.gmail.com> Hi I have a Leopard and until some time ago, port worked fine. At the moment, I have a problem with activation. I mean, any package compiles correctly, installs on destroot, and everything, but the 'activating' line appears, and no more information is given. It just freezes. I tried to get with 'top' information about the stalled process, but I did not find anything suspicious. Any hint on what might be happening? Thanks Alberto PS: Also, why 'man' does not find the 'port' manpage? I think this worked correctly on my old Tiger.... :-S -- Alberto Sim?es From macleod at cvrti.utah.edu Wed Jan 2 07:46:48 2008 From: macleod at cvrti.utah.edu (Rob MacLeod) Date: Wed Jan 2 07:45:03 2008 Subject: Emacs and Leopard problems continue In-Reply-To: <88E9028D-D470-43E5-BD51-0EE50D328E3F@apple.com> References: <887865AB-59C2-436B-99CC-15C7CCE06CF4@cvrti.utah.edu> <88E9028D-D470-43E5-BD51-0EE50D328E3F@apple.com> Message-ID: <6154BF4D-DE56-41D0-A12A-B72683275543@cvrti.utah.edu> Hi, This is pretty easy--I want emacs to work in X11. Cheers, Rob On Jan 1, 2008, at 1:16 PM, Jordan K. Hubbard wrote: > OK, I'll bite. What specifically is wrong with the system emacs > that requires folks to struggle so hard to build another copy? It > even supports carbon if you add an app wrapper (like the one I just > attached - a mere 55k, and most of that is the icon), so I'm not > sure what would lead one to struggle so hard to build emacs again. > Yes, the macports version should certainly work just on general > principle, but that's not the question I'm asking. > > - Jordan > > > > > p > On Dec 31, 2007, at 2:58 PM, Rob MacLeod wrote: > >> Hi folks, >> >> I am still struggling with Leopard woes with emacs. >> >> I was able to get emacs, emacs-devel, and emacs-app all made by >> manually applying the patch provided in ticket #13294. emacs made >> in the wrong directory while emacs-devel did better and ended up >> properly placed. >> >> However, neither emacs nor emacs-devel launch a new X window when I >> start them. I vaguely recall that this was a problem in the past >> but I was able with Tiger to get at least one of them (no longer >> sure which) to work in the proper X window mode. >> >> Does anyone know if there are some other settings I need to get a >> full functioning X11 based emacs to work? >> >> In the meantime, I will experiment with emacs-app to see if I can >> get it to work the way I am used to... >> >> Good thing this is the break and I have time to deal with all the >> frustrations of Leopard.... >> >> Happy New Year, >> >> Rob >> >> _______________________________________________ >> macports-users mailing list >> macports-users@lists.macosforge.org >> http://lists.macosforge.org/mailman/listinfo/macports-users > From liontooth at cogweb.net Wed Jan 2 08:31:00 2008 From: liontooth at cogweb.net (David Liontooth) Date: Wed Jan 2 08:29:40 2008 Subject: Display separate cpu states in top Message-ID: <477BBC44.5010007@cogweb.net> Dual-core CPUs are now commonplace on Macs. Can top display the load on each core? In Linux, the top from procps has for a while now included this option: <1> :Toggle_Single/Separate_Cpu_States -- On/Off This command affects how the 't' command's Cpu States portion is shown. Although this toggle exists primarily to serve massively-parallel SMP machines, it is not restricted to solely SMP environments. When you see 'Cpu(s):' in the summary area, the '1' toggle is On and all cpu information is gathered in a single line. Otherwise, each cpu is displayed separately as: 'Cpu0, Cpu1, ...' Any way to get this functionality in OSX? Cheers, Dave From caliel at caliel.no-ip.org Wed Jan 2 08:56:18 2008 From: caliel at caliel.no-ip.org (caliel) Date: Wed Jan 2 08:54:27 2008 Subject: Kismet on OSX 10.5.1 Leopard In-Reply-To: References: Message-ID: <610e924ffeded3be62c97f03405596fc@localhost> Paul, Sorry for the delayed response, but I wanted to make sure that the thread is complete for others who are researching. From the KisMAC faq (http://kismac.macpirate.ch/wiki/doku.php?id=faq) ----- If you've updated to OS 10.4.10, you MUST use r239. OS 10.5 (Leopard) breaks AirPort Extreme passive mode support again, but shouldn't break support for other devices (USB and PCMCIA). ----- This is what the Kismet team told me they are also facing. I assume both parties are working on the issue, but it seems to be a communication problem between Apple developers and Kis[Mm]?? developers. Naturally, the proper solution is to use 1.4.10, then I could use either of them. Pioneers, as they say, take the arrows :) --caliel On Sat, 8 Dec 2007 19:33:00 -0800, "paul beard" wrote: > On 11/28/07, caliel wrote: >> >> I have returned home from my holiday travels with eager anticipation to >> try >> kismet with my ralink USB Wi-Fi card. Just as I plugged it in, I > realized >> ...... ...... darwin and viha are the only valid capture sources for > OSX! >> > > Any reason not to use KisMac? > > > > -- > Paul Beard / www.paulbeard.org/ > From ryandesign at macports.org Wed Jan 2 09:15:28 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed Jan 2 09:14:01 2008 Subject: what configuration files are read? In-Reply-To: <140eba4e0801020616r3dbd7b28k2e7ffe56cbfa8bf9@mail.gmail.com> References: <37CF4227-52D1-4159-9BD8-31451BAA84C7@beebo.org> <140eba4e0801020616r3dbd7b28k2e7ffe56cbfa8bf9@mail.gmail.com> Message-ID: <0FABD196-47B8-4B61-B5DA-11E37BFB90CA@macports.org> On Jan 2, 2008, at 08:16, Michael Stillwell wrote: > On Jan 1, 2008 12:00 AM, Ryan Schmidt wrote: > >> On Dec 31, 2007, at 06:48, Michael Stillwell wrote: >> >>> How does "port" figure out which configuration files to read? Mine >>> is now trying to get configuration information from a non-existent >>> file: [ ... ] >> >> Issue #1: The reason why your two installations are conflicting with >> one another is that they both installed their Tcl components to / >> Library/Tcl/macports1.0, and the $HOME/scratch/ports instalation's / >> Library/Tcl/macports1.0 has overwritten the one from $HOME/Ports. >> >> [ ... ] >> >> You could bypass all the arguments and just do it yourself. You >> should reinstall both of your installations (or at least the /Ports >> one, since its /Library/Tcl/macports1.0 is gone), making sure that at >> least one, or perhaps both, of them put their Tcl directory >> elsewhere, for example: >> >> PATH=/usr/bin:/usr/sbin:/bin:/sbin ./configure \ >> --prefix=$HOME/Ports \ >> --with-tclpackage=$HOME/Ports/share/macports/Tcl > > Thanks; this worked perfectly. > > Is it possible to improve the --prefix documentation? "./configure > --help" doesn't make it clear that 99% (but not 100%) of the installed > files will go into the specified directory, and it's somewhat > unexpected that the crucial missing directory of files is configured > via --with-tclinclude. I agree. It's so unclear that I read the ./configure --help, couldn't figure it out, and went searching for Daniel's email (because I remembered seeing it before). But that doesn't help people who don't know to go looking for it. From bengt.nilsson11 at spray.se Wed Jan 2 10:20:13 2008 From: bengt.nilsson11 at spray.se (Bengt Nilsson) Date: Wed Jan 2 10:18:21 2008 Subject: tsclient missing Message-ID: <4B1C0DE4-D01A-438F-A6BD-E850F4509F33@spray.se> Hi! tsclient seems to be missing from the repositories: sh-3.2# port install tsclient ---> Fetching tsclient ---> Attempting to fetch tsclient-0.148.tar.gz from http://www.gnomepro.com/tsclient/ ---> Attempting to fetch tsclient-0.148.tar.gz from http://svn.macports.org/repository/macports/distfiles/tsclient ---> Attempting to fetch tsclient-0.148.tar.gz from http://svn.macports.org/repository/macports/distfiles/general/ ---> Attempting to fetch tsclient-0.148.tar.gz from http://svn.macports.org/repository/macports/downloads/tsclient Error: Target org.macports.fetch returned: fetch failed Error: Status 1 encountered during processing. sh-3.2# Is it coming back, is it just not there yet? BN From matrixm at gmail.com Wed Jan 2 10:24:27 2008 From: matrixm at gmail.com (Matrix Mole) Date: Wed Jan 2 10:22:35 2008 Subject: Activating stalls In-Reply-To: <2b670b7e0801020716u72327632q2424aa559169491a@mail.gmail.com> References: <2b670b7e0801020716u72327632q2424aa559169491a@mail.gmail.com> Message-ID: <477BD6DB.1010808@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alberto Sim?es wrote: > Hi > > I have a Leopard and until some time ago, port worked fine. At the > moment, I have a problem with activation. I mean, any package compiles > correctly, installs on destroot, and everything, but the 'activating' > line appears, and no more information is given. It just freezes. > Any hint on what might be happening? I would suggest using the -d flag for port (ie, sudo port -d install foo) this will give debug information that will be helpful in seeing exactly where the error is occurring. > PS: Also, why 'man' does not find the 'port' manpage? I think this > worked correctly on my old Tiger.... :-S Check your $MANPATH variable at the command prompt 'echo $MANPATH' and see what it lists. I know some time back I had to add /opt/local/man to $MANPATH in my .bashrc file (add a line that says 'export MANPATH=/opt/local/man:$MANPATH' without the quotes) so that it would be able to find the man page for port along with all the files that are installed via macports. Matrix Mole -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHe9bbNtosHRPp48MRAvwzAKCKNz4eV/L/VJXYw8g0BS0hhjawGACffSqE t7oNgpIdND9wTMzgsMu+2lw= =vgjn -----END PGP SIGNATURE----- From ryandesign at macports.org Wed Jan 2 10:44:12 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed Jan 2 10:42:44 2008 Subject: tsclient missing In-Reply-To: <4B1C0DE4-D01A-438F-A6BD-E850F4509F33@spray.se> References: <4B1C0DE4-D01A-438F-A6BD-E850F4509F33@spray.se> Message-ID: <5D715D6E-DEEE-40B7-B659-2466632022CF@macports.org> On Jan 2, 2008, at 12:20, Bengt Nilsson wrote: > tsclient seems to be missing from the repositories: > > sh-3.2# port install tsclient > ---> Fetching tsclient > ---> Attempting to fetch tsclient-0.148.tar.gz from http:// > www.gnomepro.com/tsclient/ > ---> Attempting to fetch tsclient-0.148.tar.gz from http:// > svn.macports.org/repository/macports/distfiles/tsclient > ---> Attempting to fetch tsclient-0.148.tar.gz from http:// > svn.macports.org/repository/macports/distfiles/general/ > ---> Attempting to fetch tsclient-0.148.tar.gz from http:// > svn.macports.org/repository/macports/downloads/tsclient > Error: Target org.macports.fetch returned: fetch failed > Error: Status 1 encountered during processing. > sh-3.2# > > > Is it coming back, is it just not there yet? www.gnomepro.com appears to be inaccessible at the moment, hence the distfile cannot be downloaded from that website. According to the wiki page http://en.wikipedia.org/wiki/Tsclient it has been offline for several weeks already. I added a few backup download locations to the portfile in r32452. Wait 30 minutes, then "sudo port selfupdate", then try installing tsclient again and it should work. From ryandesign at macports.org Wed Jan 2 10:48:08 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed Jan 2 10:46:40 2008 Subject: Display separate cpu states in top In-Reply-To: <477BBC44.5010007@cogweb.net> References: <477BBC44.5010007@cogweb.net> Message-ID: On Jan 2, 2008, at 10:31, David Liontooth wrote: > Dual-core CPUs are now commonplace on Macs. Can top display the > load on each core? > > In Linux, the top from procps has for a while now included this > option: > > <1> :Toggle_Single/Separate_Cpu_States -- On/Off > This command affects how the 't' command's Cpu States > portion is shown. Although this toggle exists primarily to serve > massively-parallel > SMP machines, it is not restricted to solely SMP > environments. > > When you see 'Cpu(s):' in the summary area, the '1' > toggle is On and all cpu information is gathered in a single line. > Otherwise, each cpu > is displayed separately as: 'Cpu0, Cpu1, ...' > > Any way to get this functionality in OSX? A quick glance at the top manpage doesn't show me any way to do this. And a quick look through "port search top" doesn't show me any alternate versions of top available. From ryandesign at macports.org Wed Jan 2 10:50:20 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed Jan 2 10:48:54 2008 Subject: gpgme variant for mutt-devel? In-Reply-To: <20080102081828.GB3170@castellio.ztt.fh-worms.de> References: <20080102081828.GB3170@castellio.ztt.fh-worms.de> Message-ID: On Jan 2, 2008, at 02:18, Christoph Ludwig wrote: > I have a request: I'd be grateful if support for mutt's gpgme > crypto backend > was added to the port mutt-devel, at least as a variant. > Unfortunately, I am > swamped so I do not have the time to come up with a portfile patch > myself. [snip] Then you should file an enhancement request ticket in Trac. From ludwig at fh-worms.de Wed Jan 2 11:08:12 2008 From: ludwig at fh-worms.de (Christoph Ludwig) Date: Wed Jan 2 11:06:37 2008 Subject: gpgme variant for mutt-devel? In-Reply-To: References: <20080102081828.GB3170@castellio.ztt.fh-worms.de> Message-ID: <20080102190812.GA3356@castellio.local> On Wed, Jan 02, 2008 at 12:50:20PM -0600, Ryan Schmidt wrote: > On Jan 2, 2008, at 02:18, Christoph Ludwig wrote: > >I have a request: I'd be grateful if support for mutt's gpgme > >crypto backend > >was added to the port mutt-devel, at least as a variant. > >Unfortunately, I am > >swamped so I do not have the time to come up with a portfile patch > >myself. > > > [snip] > > Then you should file an enhancement request ticket in Trac. done, it is #13788. Thanks Christoph -- FH Worms - University of Applied Sciences Fachbereich Informatik / Telekommunikation Erenburgerstr. 19, 67549 Worms, Germany From hashashin at gmail.com Wed Jan 2 11:26:54 2008 From: hashashin at gmail.com (=?ISO-8859-1?Q?Alberto_Sim=F5es?=) Date: Wed Jan 2 11:25:01 2008 Subject: Activating stalls In-Reply-To: <477BD6DB.1010808@gmail.com> References: <2b670b7e0801020716u72327632q2424aa559169491a@mail.gmail.com> <477BD6DB.1010808@gmail.com> Message-ID: <2b670b7e0801021126r4615b4d1vd764caf531ce2ddf@mail.gmail.com> Hi, Matrix. On Jan 2, 2008 6:24 PM, Matrix Mole wrote: > > I have a Leopard and until some time ago, port worked fine. At the > > moment, I have a problem with activation. I mean, any package compiles > > correctly, installs on destroot, and everything, but the 'activating' > > line appears, and no more information is given. It just freezes. > I would suggest using the -d flag for port (ie, sudo port -d install > foo) this will give debug information that will be helpful in seeing > exactly where the error is occurring. It did not help much :( [ambs@rachmaninoff ~]$ sudo port -d install ispell Password: DEBUG: Found port in file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/ispell DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/ispell DEBUG: Requested variant darwin is not provided by port ispell. DEBUG: Requested variant i386 is not provided by port ispell. DEBUG: Requested variant macosx is not provided by port ispell. DEBUG: Skipping completed org.macports.main (ispell) DEBUG: Skipping completed org.macports.fetch (ispell) DEBUG: Skipping completed org.macports.checksum (ispell) DEBUG: Skipping completed org.macports.extract (ispell) DEBUG: Skipping completed org.macports.patch (ispell) DEBUG: Skipping completed org.macports.configure (ispell) DEBUG: Skipping completed org.macports.build (ispell) DEBUG: Skipping completed org.macports.destroot (ispell) DEBUG: Skipping org.macports.install (ispell) since this port is already installed DEBUG: Executing org.macports.activate (ispell) ---> Activating ispell 3.3.02_0 Thanks -- Alberto Sim?es From frstan at bellsouth.net Wed Jan 2 12:06:55 2008 From: frstan at bellsouth.net (William Davis) Date: Wed Jan 2 12:05:02 2008 Subject: Display separate cpu states in top In-Reply-To: References: <477BBC44.5010007@cogweb.net> Message-ID: <1E9BB937-0520-45D0-BB23-0F2CBE96EAE8@bellsouth.net> see On Jan 2, 2008, at 1:48 PM, Ryan Schmidt wrote: > > On Jan 2, 2008, at 10:31, David Liontooth wrote: > >> Dual-core CPUs are now commonplace on Macs. Can top display the >> load on each core? >> >> In Linux, the top from procps has for a while now included this >> option: >> >> <1> :Toggle_Single/Separate_Cpu_States -- On/Off >> This command affects how the 't' command's Cpu States >> portion is shown. Although this toggle exists primarily to serve >> massively-parallel >> SMP machines, it is not restricted to solely SMP >> environments. >> >> When you see 'Cpu(s):' in the summary area, the '1' >> toggle is On and all cpu information is gathered in a single line. >> Otherwise, each cpu >> is displayed separately as: 'Cpu0, Cpu1, ...' >> >> Any way to get this functionality in OSX? > > A quick glance at the top manpage doesn't show me any way to do > this. And a quick look through "port search top" doesn't show me any > alternate versions of top available. > > > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users William Davis frstanATbellsouthDOTnet Mac OS X.5.1 Darwin 9.1.0 X11.app 2.1.1 - (xorg-server 1.3.0-apple5) Mac Mini Intel Duo @ 1.86 GHz Mundus vult decepi, ego non -------------- next part -------------- Skipped content of type multipart/related From tabithamc at gmail.com Wed Jan 2 12:22:54 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Wed Jan 2 12:21:00 2008 Subject: Incredible speed ups on Leopard!? Message-ID: <7fccb3000801021222s6e85adfdu900f1da36fbc879c@mail.gmail.com> Has anyone else noticed incredible MacPorts speed up improvements when installing various ports? Here's an example: The same hardware (Xserve Intel 2 x 2 GhZ Dual Core Intel). Once this machine was running Tiger Server with MacPorts 1.5.0 and I installed the gcc41 port which (if my notes are accurate) took about 88minutes to install from beginning to end (some of the time could have been eaten up in the "fetching" of the resource source files). Anyway, the same port on Leopard Server on the same machine with MacPort 1.6.0 took me roughly 20 minutes to install today. From 88 to 20 minutes is almost unheard of. I checked the port files too, to make sure the version of the gcc41 port I was installing was the same: Tiger Server: gcc41 4.1.2, Revision 2, lang/gcc41 (Variants: universal, darwin_8, > darwin_i386, powerpc, odcctools) > Leopard Server: gcc41 4.1.2, Revision 2, lang/gcc41 (Variants: universal, darwin_8, > darwin_i386, powerpc, odcctools) > I presume this is because Leopard and Leopard Server are now leveraging the Apple Developer tools with a complete 64-bit wide architecture (both the hardware and the software)? Thanks, T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080102/55a771dc/attachment.html From tabithamc at gmail.com Wed Jan 2 13:17:06 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Wed Jan 2 13:15:12 2008 Subject: Incredible speed ups on Leopard!? In-Reply-To: <7fccb3000801021222s6e85adfdu900f1da36fbc879c@mail.gmail.com> References: <7fccb3000801021222s6e85adfdu900f1da36fbc879c@mail.gmail.com> Message-ID: <7fccb3000801021317y364a39adre1d11a6b4b6962c4@mail.gmail.com> I may have spoken too soon without investigating under the hood because building the gcc42 port took the same amount of time on Leopard Server as Tiger Server on the same Xserve (70 minute). -T.M. On 1/2/08, Tabitha McNerney wrote: > > Has anyone else noticed incredible MacPorts speed up improvements when > installing various ports? > > Here's an example: The same hardware (Xserve Intel 2 x 2 GhZ Dual Core > Intel). Once this machine was running Tiger Server with MacPorts 1.5.0 and > I installed the gcc41 port which (if my notes are accurate) took about 88minutes to install from beginning to end (some of the time could have been > eaten up in the "fetching" of the resource source files). Anyway, the same > port on Leopard Server on the same machine with MacPort 1.6.0 took me > roughly 20 minutes to install today. From 88 to 20 minutes is almost > unheard of. I checked the port files too, to make sure the version of the > gcc41 port I was installing was the same: > > Tiger Server: > > gcc41 4.1.2, Revision 2, lang/gcc41 (Variants: universal, darwin_8, > > darwin_i386, powerpc, odcctools) > > > > Leopard Server: > > gcc41 4.1.2, Revision 2, lang/gcc41 (Variants: universal, darwin_8, > > darwin_i386, powerpc, odcctools) > > > > I presume this is because Leopard and Leopard Server are now leveraging > the Apple Developer tools with a complete 64-bit wide architecture (both the > hardware and the software)? > > Thanks, > > T.M . > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080102/e6ca96b0/attachment.html From tabithamc at gmail.com Wed Jan 2 15:01:09 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Wed Jan 2 14:59:17 2008 Subject: gnustep family of ports and Leopard Message-ID: <7fccb3000801021501l2ea51371y839c4c454bfb388b@mail.gmail.com> Hello all -- I noticed ticket #13466 which states that there are problems building the gnustep port on Leopard 10.5.1 I discovered today that building the actual "gnustep" port worked fine (Leopard Server 10.5.1) but then attempting to build gnustep-gui and its dependencies had problems. I can either update ticket #13466 or issue a new ticket. What would be the best course to take? Has anyone else had problems building various gnustep related family of ports on Leopard? Thanks, T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080102/fdde055b/attachment.html From spindle23 at gmail.com Wed Jan 2 15:03:39 2008 From: spindle23 at gmail.com (spindle) Date: Wed Jan 2 15:01:47 2008 Subject: darwin ports and xfree86 Message-ID: <477C184B.5070805@gmail.com> Hello everybody, i want to install ddd package with darwin ports (with sudo port install ddd) but this wants to compile xfree86 packet,and it gets errors. i want it to use Apple X11 instead of xfree86,how can i do that? Thanks... From tabithamc at gmail.com Wed Jan 2 15:33:34 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Wed Jan 2 15:31:39 2008 Subject: darwin ports and xfree86 In-Reply-To: <477C184B.5070805@gmail.com> References: <477C184B.5070805@gmail.com> Message-ID: <7fccb3000801021533w41c9b9edhc7ac168215247b2@mail.gmail.com> On 1/2/08, spindle wrote: > > Hello everybody, > > i want to install ddd package with darwin ports > > (with sudo port install ddd) > > but this wants to compile xfree86 packet,and it gets errors. > > i want it to use Apple X11 instead of xfree86,how can i do that? spindle, what version of Mac OS X are you use? I'm using Leopard and some of the well seasoned respected MacPorts maintainers and I had a threaded discussion about this yesterday (check the archives for yesterday, 1 January 2008) -T.M. Thanks... > > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080102/58ca22ce/attachment.html From walt at wump.org Wed Jan 2 16:12:22 2008 From: walt at wump.org (Walt Pawley) Date: Wed Jan 2 16:18:00 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> Message-ID: At 8:12 AM -0700 12/29/07, Chris Janton wrote: >I would be glad to help figure things out for Panther. I don't expect >to be upgrading that OS for some time (long) so having a working, >viable MacPorts is important to me. Sadly, supporting older versions of Mac OS X is not something the MacPorts effort has been "up" for. The excuse is always the same - no one else is using that old stuff. Which bothers me just a bit as I see far more Mac users not using the latest stuff than I do those who bleed along with the progressing edge and not just because I look in a mirror once a day at least. I could be wrong, but I suspect that the gestalt of the MacPorts effort would have to change to capture old source distributions of the ports referenced files before it'd make a lot of sense to "retain compatibility". -- Walter M. Pawley Wump Research & Company 676 River Bend Road, Roseburg, OR 97470 541-672-8975 From ryandesign at macports.org Wed Jan 2 16:34:58 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed Jan 2 16:33:29 2008 Subject: Pidgin with OTR? In-Reply-To: <477B46F0.6010602@reifferscheid.org> References: <4776C0FE.1010604@gmail.com> <4776F44C.8030804@reifferscheid.org> <47779628.3090005@reifferscheid.org> <4779E0A3.3090106@gmail.com> <477A9B49.7070701@reifferscheid.org> <477B079A.40001@gmail.com> <477B46F0.6010602@reifferscheid.org> Message-ID: Anders committed it. On Jan 2, 2008, at 02:10, Thomas Reifferscheid wrote: > You can have the portfile in a local repository. You find all the > details here: > > http://guide.macports.org/#development.local-repositories > > However, it would be more easier, if someone would commit the port to > the global macports repository. > > Kind regards > Thomas Reifferscheid > > > Matrix Mole wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Thomas Reifferscheid wrote: >> >>> pigdin-encryption is http://pidgin-encrypt.sourceforge.net/ it >>> has nothing >>> to do with pidgin-otr. >>> >> >> Thank you for pointing that out, I didn't realize that they were two >> distinct different encryption builds. >> >> >>> pidgin-otr is not available yet in macports. You find details here: >>> http://trac.macosforge.org/projects/macports/ticket/13759 >>> >> >> Using the tarball file from that site, where would I place it so >> that I >> could then install it into my port tree? I'd be more than willing to >> install the build and report back any bugs I run across while >> using it. From ryandesign at macports.org Wed Jan 2 16:53:20 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed Jan 2 16:51:51 2008 Subject: darwin ports and xfree86 In-Reply-To: <477C184B.5070805@gmail.com> References: <477C184B.5070805@gmail.com> Message-ID: On Jan 2, 2008, at 17:03, spindle wrote: > Hello everybody, > > i want to install ddd package with darwin ports > > (with sudo port install ddd) > > but this wants to compile xfree86 packet,and it gets errors. > > i want it to use Apple X11 instead of xfree86,how can i do that? You need both X11User.pkg and X11SDK.pkg. Depending on your version of Mac OS X, these are found in different places. For Leopard: X11User is already installed. Install Xcode 3 to get X11SDK. For Tiger: X11User is an optional install on your Mac OS X DVD. After you do that, install X11SDK from the Xcode 2.5 disk image downloaded from Apple Developer Connection. For Panther: X11User is available from Apple Support Downloads. After that's installed, install the X11SDK from the Xcode 1.5 disk image downloaded from Apple Developer Connection. Once X11User and X11SDK are installed, ports that claim to depend on XFree86 will make use of Apple X11 instead of using XFree86. From liontooth at cogweb.net Wed Jan 2 19:09:07 2008 From: liontooth at cogweb.net (David Liontooth) Date: Wed Jan 2 19:07:18 2008 Subject: Display separate cpu states in top In-Reply-To: <1E9BB937-0520-45D0-BB23-0F2CBE96EAE8@bellsouth.net> References: <477BBC44.5010007@cogweb.net> <1E9BB937-0520-45D0-BB23-0F2CBE96EAE8@bellsouth.net> Message-ID: <477C51D3.6020405@cogweb.net> William Davis wrote: > see Thanks, that works; I was hoping for a CLI version. Dave > On Jan 2, 2008, at 1:48 PM, Ryan Schmidt wrote: > >> >> On Jan 2, 2008, at 10:31, David Liontooth wrote: >> >>> Dual-core CPUs are now commonplace on Macs. Can top display the load >>> on each core? >>> >>> In Linux, the top from procps has for a while now included this option: >>> >>> <1> :Toggle_Single/Separate_Cpu_States -- On/Off >>> This command affects how the 't' command's Cpu States >>> portion is shown. Although this toggle exists primarily to serve >>> massively-parallel >>> SMP machines, it is not restricted to solely SMP >>> environments. >>> >>> When you see 'Cpu(s):' in the summary area, the '1' >>> toggle is On and all cpu information is gathered in a single line. >>> Otherwise, each cpu >>> is displayed separately as: 'Cpu0, Cpu1, ...' >>> >>> Any way to get this functionality in OSX? >> >> A quick glance at the top manpage doesn't show me any way to do this. >> And a quick look through "port search top" doesn't show me any >> alternate versions of top available. >> >> >> _______________________________________________ >> macports-users mailing list >> macports-users@lists.macosforge.org >> >> http://lists.macosforge.org/mailman/listinfo/macports-users > > > > William Davis > frstanATbellsouthDOTnet > Mac OS X.5.1 Darwin 9.1.0 > X11.app 2.1.1 - (xorg-server 1.3.0-apple5) > Mac Mini Intel Duo @ 1.86 GHz > > Mundus vult decepi, ego non > From jkh at apple.com Wed Jan 2 19:08:57 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Wed Jan 2 19:08:32 2008 Subject: Incredible speed ups on Leopard!? In-Reply-To: <7fccb3000801021222s6e85adfdu900f1da36fbc879c@mail.gmail.com> References: <7fccb3000801021222s6e85adfdu900f1da36fbc879c@mail.gmail.com> Message-ID: [ Resent from correct account, so MacPorts won't bounce it back again ] On Jan 2, 2008, at 12:22 PM, Tabitha McNerney wrote: > Has anyone else noticed incredible MacPorts speed up improvements > when installing various ports? > > Here's an example: The same hardware (Xserve Intel 2 x 2 GhZ Dual > Core Intel). Once this machine was running Tiger Server with > MacPorts 1.5.0 and I installed the gcc41 port which (if my notes are > accurate) took about 88 minutes to install from beginning to end > (some of the time could have been eaten up in the "fetching" of the > resource source files). Anyway, the same port on Leopard Server on > the same machine with MacPort 1.6.0 took me roughly 20 minutes to > install today. From 88 to 20 minutes is almost unheard of. I checked > the port files too, to make sure the version of the gcc41 port I was > installing was the same: > > Tiger Server: > > gcc41 4.1.2, Revision 2, lang/gcc41 (Variants: universal, darwin_8, > darwin_i386, powerpc, odcctools) > > Leopard Server: > > gcc41 4.1.2, Revision 2, lang/gcc41 (Variants: universal, darwin_8, > darwin_i386, powerpc, odcctools) > > I presume this is because Leopard and Leopard Server are now > leveraging the Apple Developer tools with a complete 64-bit wide > architecture (both the hardware and the software)? No, I think it's because Leopard's Tcl no longer searches an insane search path (including network volumes) as part of its startup. When we made this change in Leopard (largely because of pathological performance problems I noticed with MacPorts and fs_usage(1)), a full minute was shaved off the most basic port operations, including build/ install (it's more observable with something like "port search"). - Jordan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080102/dfee8b98/attachment.html From scacinto at gmail.com Wed Jan 2 21:56:26 2008 From: scacinto at gmail.com (Scott Petersen) Date: Wed Jan 2 21:54:30 2008 Subject: arts fails to build Message-ID: <9c7c33430801022156t168342cdk9129613279ddbf3a@mail.gmail.com> hi, i've attempted to install the arts port. It fails with the following error: Error: Target org.macports.patch returned: shell command "cd '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_audio_arts/work/arts- 1.1.2' && sed -e 's#@PREFIX@#/opt/local#g' '/opt/local/var/macports/sources/rsync.macports.org/release/ports/audio/arts/files/stable/patch- arts-artsc-artsc-config.in.diff' | patch -p0" returned error 1 Command output: patching file artsc/artsc-config.in Reversed (or previously applied) patch detected! Assume -R? [n] Apply anyway? [n] Skipping patch. 1 out of 1 hunk ignored -- saving rejects to file artsc/artsc-config.in.rej Error: Status 1 encountered during processing. Is there something I am doing wrong? I had previously gotten an autoconf version error (it said KDE needs 2.54, etc. and that I was using 2.61.) I uninstalled autoconf 2.61 and tried an earlier version, but no go. Upon reinstalling the newest version the above error appeared. Many thanks for any and all advice. -Scott -- Scott Petersen, composer Eastman Computer Music Center Eastman School of Music www.scottpetersen.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080103/66449362/attachment.html From ryandesign at macports.org Wed Jan 2 22:21:06 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Wed Jan 2 22:19:38 2008 Subject: arts fails to build In-Reply-To: <9c7c33430801022156t168342cdk9129613279ddbf3a@mail.gmail.com> References: <9c7c33430801022156t168342cdk9129613279ddbf3a@mail.gmail.com> Message-ID: On Jan 2, 2008, at 23:56, Scott Petersen wrote: > hi, i've attempted to install the arts port. It fails with the > following error: > > Error: Target org.macports.patch returned: shell command "cd '/opt/ > local/var/macports/build/ > _opt_local_var_macports_sources_rsync.macports.org_release_ports_audio > _arts/work/arts- 1.1.2' && sed -e 's#@PREFIX@#/opt/local#g' '/opt/ > local/var/macports/sources/rsync.macports.org/release/ports/audio/ > arts/files/stable/patch-arts-artsc-artsc-config.in.diff' | patch - > p0" returned error 1 > Command output: patching file artsc/artsc-config.in > Reversed (or previously applied) patch detected! Assume -R? [n] > Apply anyway? [n] > Skipping patch. > 1 out of 1 hunk ignored -- saving rejects to file artsc/artsc- > config.in.rej > > Error: Status 1 encountered during processing. > > > Is there something I am doing wrong? I had previously gotten an > autoconf version error (it said KDE needs 2.54, etc. and that I > was using 2.61.) I uninstalled autoconf 2.61 and tried an earlier > version, but no go. Upon reinstalling the newest version the above > error appeared. > > Many thanks for any and all advice. Hi Scott. You're not doing anything wrong. I just took a look at the aRts portfile, and it's pretty screwy. I get a different error but it also doesn't work for me. I filed a ticket. http://trac.macosforge.org/projects/macports/ticket/13800 From tabithamc at gmail.com Thu Jan 3 03:01:05 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Thu Jan 3 02:59:12 2008 Subject: Incredible speed ups on Leopard!? In-Reply-To: References: <7fccb3000801021222s6e85adfdu900f1da36fbc879c@mail.gmail.com> Message-ID: <7fccb3000801030301xddcb884wbc2153b60da86f8a@mail.gmail.com> On 1/2/08, Jordan K. Hubbard wrote: > > [ Resent from correct account, so MacPorts won't bounce it back again ] > On Jan 2, 2008, at 12:22 PM, Tabitha McNerney wrote: > > Has anyone else noticed incredible MacPorts speed up improvements when > installing various ports? > > Here's an example: The same hardware (Xserve Intel 2 x 2 GhZ Dual Core > Intel). Once this machine was running Tiger Server with MacPorts 1.5.0 and > I installed the gcc41 port which (if my notes are accurate) took about 88minutes to install from beginning to end (some of the time could have been > eaten up in the "fetching" of the resource source files). Anyway, the same > port on Leopard Server on the same machine with MacPort 1.6.0 took me > roughly 20 minutes to install today. From 88 to 20 minutes is almost > unheard of. I checked the port files too, to make sure the version of the > gcc41 port I was installing was the same: > > Tiger Server: > > gcc41 4.1.2, Revision 2, lang/gcc41 (Variants: universal, darwin_8, > > darwin_i386, powerpc, odcctools) > > > > Leopard Server: > > gcc41 4.1.2, Revision 2, lang/gcc41 (Variants: universal, darwin_8, > > darwin_i386, powerpc, odcctools) > > > > I presume this is because Leopard and Leopard Server are now leveraging > the Apple Developer tools with a complete 64-bit wide architecture (both the > hardware and the software)? > > > No, I think it's because Leopard's Tcl no longer searches an insane search > path (including network volumes) as part of its startup. When we made this > change in Leopard (largely because of pathological performance problems I > noticed with MacPorts and fs_usage(1)), a full minute was shaved off the > most basic port operations, including build/install (it's more observable > with something like "port search"). > Jordan, Thank you for providing a reality check (and thanks to Apple for modifying Leopard's Tcl to speed things up). I wonder then, will having a 64-bit operating system with 64-bit tools (e.g., Xcode) assist anywhere in the process of compiling a MacPort (or running a MacPort)? I think I did read in a much earlier post several weeks ago whereby someone asked a similar question about gaining 64-bit binaries and I think I recall that the answer is that its possible (but forgot the details of how -- perhaps just "automagic" with the gcc compiler provided by Apple with Xcode dev tools? For what its worth, I'm having quite an enjoyable time using Leopard Server and am thankful to the MacPorts community for making the transition to Leopard / Leopard Server quite smooth with MacPorts 1.6.0. Thanks, T.M. - Jordan > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080103/d01741a1/attachment-0001.html From mww at macports.org Thu Jan 3 04:11:53 2008 From: mww at macports.org (Markus Weissmann) Date: Thu Jan 3 04:10:08 2008 Subject: MacPorts 1.6 still supports OS X 10.3 Panther? In-Reply-To: References: <07E049E1-FBB6-4242-B10E-1CA2CA2ABEF9@macports.org> <33911.202.81.69.153.1198123540.squirrel@webmail.tuffmail.net> <399E83DE-C56F-4260-BD6A-20AD0C0D9F84@centosprime.com> <55053.203.20.35.28.1198930564.squirrel@webmail.tuffmail.net> <3AC3F72B-9533-4197-8074-009AAD45356C@CentosPrime.COM> Message-ID: <41C29E3E-E827-4654-9FBB-C3D78664C3DD@macports.org> On 3 Jan 2008, at 01:12, Walt Pawley wrote: > At 8:12 AM -0700 12/29/07, Chris Janton wrote: >> I would be glad to help figure things out for Panther. I don't expect >> to be upgrading that OS for some time (long) so having a working, >> viable MacPorts is important to me. > > Sadly, supporting older versions of Mac OS X is not something > the MacPorts effort has been "up" for. The excuse is always the > same - no one else is using that old stuff. Which bothers me > just a bit as I see far more Mac users not using the latest > stuff than I do those who bleed along with the progressing edge > and not just because I look in a mirror once a day at least. > > I could be wrong, but I suspect that the gestalt of the > MacPorts effort would have to change to capture old source > distributions of the ports referenced files before it'd make a > lot of sense to "retain compatibility". It is not like we actively oppose supporting 10.3, but our manpower is very limited and some maintainers might even have access to either 10.4 or 10.5 only. So if you want to work on a "long term support" version of ports, you're welcome to join us -- we'll see if perhaps an alternative ports tree could be a solution to this problem. Regards, -Markus -- Dipl. Inf. (FH) Markus W. Weissmann http://www.macports.org/ http://www.mweissmann.de/ From hashashin at gmail.com Thu Jan 3 06:31:03 2008 From: hashashin at gmail.com (=?ISO-8859-1?Q?Alberto_Sim=F5es?=) Date: Thu Jan 3 06:29:07 2008 Subject: Activating stalls In-Reply-To: <2b670b7e0801021126r4615b4d1vd764caf531ce2ddf@mail.gmail.com> References: <2b670b7e0801020716u72327632q2424aa559169491a@mail.gmail.com> <477BD6DB.1010808@gmail.com> <2b670b7e0801021126r4615b4d1vd764caf531ce2ddf@mail.gmail.com> Message-ID: <2b670b7e0801030631h4919b7fey2f34273e82d0e362@mail.gmail.com> A reboot seems to have helped with this. On Jan 2, 2008 7:26 PM, Alberto Sim?es wrote: > Hi, Matrix. > > On Jan 2, 2008 6:24 PM, Matrix Mole wrote: > > > I have a Leopard and until some time ago, port worked fine. At the > > > moment, I have a problem with activation. I mean, any package compiles > > > correctly, installs on destroot, and everything, but the 'activating' > > > line appears, and no more information is given. It just freezes. > > > I would suggest using the -d flag for port (ie, sudo port -d install > > foo) this will give debug information that will be helpful in seeing > > exactly where the error is occurring. > > It did not help much :( > > [ambs@rachmaninoff ~]$ sudo port -d install ispell > Password: > DEBUG: Found port in > file:///opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/ispell > DEBUG: Changing to port directory: > /opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/ispell > DEBUG: Requested variant darwin is not provided by port ispell. > DEBUG: Requested variant i386 is not provided by port ispell. > DEBUG: Requested variant macosx is not provided by port ispell. > DEBUG: Skipping completed org.macports.main (ispell) > DEBUG: Skipping completed org.macports.fetch (ispell) > DEBUG: Skipping completed org.macports.checksum (ispell) > DEBUG: Skipping completed org.macports.extract (ispell) > DEBUG: Skipping completed org.macports.patch (ispell) > DEBUG: Skipping completed org.macports.configure (ispell) > DEBUG: Skipping completed org.macports.build (ispell) > DEBUG: Skipping completed org.macports.destroot (ispell) > DEBUG: Skipping org.macports.install (ispell) since this port is > already installed > DEBUG: Executing org.macports.activate (ispell) > ---> Activating ispell 3.3.02_0 > > Thanks > -- > Alberto Sim?es > -- Alberto Sim?es From someguyonearth at gmail.com Thu Jan 3 07:35:58 2008 From: someguyonearth at gmail.com (Some Guy) Date: Thu Jan 3 07:34:02 2008 Subject: problem using port to install gnucash on mac 10.5 In-Reply-To: <38E322B1-12C0-4F25-B921-6010027D3CCE@macports.org> References: <9153cb050801010540y6a8f53cdw501b27bcb636174f@mail.gmail.com> <38E322B1-12C0-4F25-B921-6010027D3CCE@macports.org> Message-ID: <9153cb050801030735o54ecd589u3ad4e46ee2cde1ab@mail.gmail.com> thanks. Unfortunately i now get a problem with avahi ---> Configuring avahi > Error: Target org.macports.configure returned: configure failure: shell > command " cd > "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_net_avahi/work/avahi- > 0.6.17" && ./configure --prefix=/opt/local --disable-autoipd --disable-qt3 > --disable-qt4 --disable-mono --disable-monodoc --with-distro=darwin " > returned error 1 > Command output: checking for sys/prctl.h... no > checking for chroot... yes > checking for dlopen in -ldl... yes > checking for dlfcn.h... (cached) yes > checking for pkg-config... yes > checking for pkg-config... /opt/local/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for GLIB20... yes > checking for GTK20... yes > checking for GLADE20... yes > checking for DBUS... yes > Your D-Bus version is 1,0,2. > checking for dbus_connection_close... yes > checking for dbus_bus_get_private... yes > checking for XML_ParserCreate in -lexpat... yes > checking expat.h usability... yes > checking expat.h presence... yes > checking for expat.h... yes > checking for gdbm_open in -lgdbm... yes > checking gdbm.h usability... yes > checking gdbm.h presence... yes > checking for gdbm.h... yes > checking for LIBDAEMON... yes > checking whether /opt/local/bin/python2.5 version >= 2.4... yes > checking for /opt/local/bin/python2.5 version... 2.5 > checking for /opt/local/bin/python2.5 platform... darwin > checking for /opt/local/bin/python2.5 script directory... > ${prefix}/lib/python2.5/site-packages > checking for /opt/local/bin/python2.5 extension module directory... > ${exec_prefix}/lib/python2.5/site-packages > checking for python module gtk... no > configure: error: Could not find Python module gtk > > Error: The following dependencies failed to build: evince avahi esound > gconf intltool orbit2 libidl gnome-doc-utils iso-codes py25-hashlib openssl > py25-libxml2 gnome-icon-theme icon-naming-utils p5-getopt-long p5-pathtools > p5-xml-simple p5-test-simple p5-test-harness p5-xml-namespacesupport > p5-xml-sax gnome-keyring libgcrypt libgpg-error gnome-vfs gnome-mime-data > howl neon libart_lgpl libgnome libbonobo popt libgnomecanvas gail libgnomeui > libbonoboui m4 nautilus eel gnome-desktop fribidi startup-notification > gnome-menus libexif librsvg libcroco libgsf shared-mime-info poppler > poppler-data gnucash-docs yelp firefox-x11 zip libgtkhtml goffice03 > libgnomeprintui libgnomeprint bison libgnomecups pcre guile16 readline > ncurses ncursesw gawk libgtkhtml3 p5-finance-quote p5-crypt-ssleay > p5-libwww-perl p5-compress-zlib p5-compress-raw-zlib p5-io-compress-base > p5-scalar-list-utils p5-io-compress-zlib p5-html-parser p5-html-tagset > p5-uri p5-datemanip p5-html-tableextract slib slib-guile16 > Error: Status 1 encountered during processing. > On Jan 1, 2008 9:17 PM, Ryan Schmidt wrote: > On Jan 1, 2008, at 07:40, Some Guy wrote: > > > could anyone please help, i have been trying to install gnucash on > > my mac but i get this; > > > > > > "---> Building aqbanking with target all > [snip] > > ld: cycle in dylib re-exports with /usr/X11R6/lib/libGL.dylib > > You are experiencing this bug: > > http://trac.macosforge.org/projects/macports/ticket/13173 > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080103/3c050444/attachment.html From tom at vilot.com Thu Jan 3 08:31:10 2008 From: tom at vilot.com (Tom Vilot) Date: Thu Jan 3 08:29:19 2008 Subject: Install fails Message-ID: <3442B39B-8364-4C0C-AD93-7009A068FCE1@vilot.com> I tried the disk image and received an error: The following install step failed: run preflight script. I tried from source, and got: ===> making all in src/registry2.0 cc -dynamiclib -L/usr/local/lib registry.o util.o entry.o entryobj.o - o registry.dylib -L/System/Library/Frameworks/Tcl.framework/Versions/ 8.4 -ltclstub8.4 -L/usr/local/lib ../cregistry/cregistry.a -lsqlite3 ld: in ../cregistry/cregistry.a, archive has no table of contents collect2: ld returned 1 exit status make[2]: *** [registry.dylib] Error 1 make[1]: *** [all] Error 1 make: *** [all] Error 1 From jkh at apple.com Thu Jan 3 11:10:05 2008 From: jkh at apple.com (Jordan K. Hubbard) Date: Thu Jan 3 11:09:37 2008 Subject: Incredible speed ups on Leopard!? In-Reply-To: <7fccb3000801030301xddcb884wbc2153b60da86f8a@mail.gmail.com> References: <7fccb3000801021222s6e85adfdu900f1da36fbc879c@mail.gmail.com> <7fccb3000801030301xddcb884wbc2153b60da86f8a@mail.gmail.com> Message-ID: <12A83712-83A5-4B5F-98E9-30AE99F9F47F@apple.com> On Jan 3, 2008, at 3:01 AM, Tabitha McNerney wrote: > Thank you for providing a reality check (and thanks to Apple for > modifying Leopard's Tcl to speed things up). I wonder then, will > having a 64-bit operating system with 64-bit tools ( e.g., Xcode) > assist anywhere in the process of compiling a MacPort (or running a > MacPort)? I think I did read in a much earlier post several weeks > ago whereby someone asked a similar question about gaining 64-bit > binaries and I think I recall that the answer is that its possible > (but forgot the details of how -- perhaps just "automagic" with the > gcc compiler provided by Apple with Xcode dev tools? I think that for the most part, the 64 bit environment is not going to impact MacPorts as a whole. You gain some performance due to having the extra registers, but you also lose performance due to increased memory pressure and, at least right now, there's just no reason to compile something 64 bit unless it's the sort of application with a really large working set (scientific simulation, photo processing tools working on RAW images, etc). - Jordan From guido.soranzio at gmail.com Thu Jan 3 11:36:43 2008 From: guido.soranzio at gmail.com (Guido Soranzio) Date: Thu Jan 3 11:34:50 2008 Subject: problem using port to install gnucash on mac 10.5 Message-ID: Some Guy wrote: > thanks. Unfortunately i now get a problem with avahi: >> checking for python module gtk... no >> configure: error: Could not find Python module gtk A temporary workaround has been committed today: you should reinstall py25-gobject, py25-cairo and py25-gtk. Regards, Guido From tabithamc at gmail.com Thu Jan 3 12:17:21 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Thu Jan 3 12:15:24 2008 Subject: Standardizing a MacPorts system Message-ID: <7fccb3000801031217g68fc8832h1df1d9b4cd156fe9@mail.gmail.com> Hello all -- I would like to build, from source, on an Xserve running Leopard Server, a "standard" MacPorts system that could be deployed, in an organization, on numerous other Apple servers running the same version of the OS (e.g. Leopard Server). In doing so I would use Apple's command-line tools (such as hdiutil and asr) create a restorable disk image (.dmg) file of a disc volume that hangs off an external disk on my original Xserve which houses the MacPorts prefix (e.g., /opt/local). I would then restore from this disc image to the additional machines slated to be the recipients of the original standard. I don't see any immediate problems in doing so, however I have noticed when installing some ports (when I have occasionally enabled verbose mode "-v" during the install), depending on the port, some ports seem to take into consideration the Hostname of the Xserve I'm running it on. On my Xserve running Leopard Server, the Hostname is very importantly tied to the DNS name because I am running Apple's DNS server that is buncled with Leopard Server since I need it for other services on the machine which are not directly related to MacPorts such as running an OpenDirectory Master. The problem is, with hundreds of MacPorts tied together and with complex dependency chains, how can anyone determine when a specific MacPort reads the hostname and uses the hostname of the machine during the configuration process (unless a sys admin such as myself builds each and every port with verbose mode and analysis the output grepping for the hostname)? It might be problematic if the hostname of any given MacPort somehow becomes "hard wired" into the port itself during the configuration / install processing. Then again, I might be making a mountain out of a mole hill. Has anyone else built a Standardized MacPorts system that is cloned to multiple Macs? Thanks, T.M. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080103/65702ac8/attachment.html From macports.users at gmail.com Thu Jan 3 12:18:47 2008 From: macports.users at gmail.com (Charlse Darwin) Date: Thu Jan 3 12:17:06 2008 Subject: sudo port upgrade outdated > PortUpgradeOutdated.log Message-ID: <9345764E-E5AA-4069-A4E9-0568B9E84C89@gmail.com> How do I get the port to write the output to a log file? `$ sudo port upgrade outdated > PortUpgradeOutdated.log' didn't fly well. From macports.users at gmail.com Thu Jan 3 14:32:10 2008 From: macports.users at gmail.com (Charlse Darwin) Date: Thu Jan 3 14:30:16 2008 Subject: $ sudo port -f install MacPorts Message-ID: <76AEA96B-0DD7-41DC-919E-A498DF38B3C4@gmail.com> $ sudo port -f install MacPorts Portfile changed since last build; discarding previous state. ---> Fetching MacPorts ---> Attempting to fetch MacPorts-1.6.0.tar.gz from http:// svn.macports.org/repository/macports/distfiles/MacPorts-1.6.0 ---> Attempting to fetch MacPorts-1.6.0.tar.gz from http:// svn.macports.org/repository/macports/distfiles/general/MacPorts-1.6.0 ---> Attempting to fetch MacPorts-1.6.0.tar.gz from http:// svn.macports.org/repository/macports/downloads/MacPorts-1.6.0 ---> Verifying checksum(s) for MacPorts ---> Extracting MacPorts ---> Configuring MacPorts Fixing your MacOSX10.4u installation by copying libtclstub8.4.a to / Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks/ Tcl.framework/Versions/8.4/libtclstub8.4.a Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_sysutil s_MacPorts/work/MacPorts-1.6.0" && ./configure --prefix=/opt/local -- enable-readline " returned error 1 Command output: configure: error: cannot run /bin/sh ./config.sub Error: Status 1 encountered during processing. $ From macports.users at gmail.com Thu Jan 3 14:40:21 2008 From: macports.users at gmail.com (Charlse Darwin) Date: Thu Jan 3 14:38:25 2008 Subject: $ sudo port -f install MacPorts Message-ID: <87FFC008-A323-415C-ADF4-88A4E3A69370@gmail.com> $ sudo port -fvd install MacPorts DEBUG: Found port in file:///opt/local/var/macports/sources/ rsync.macports.org/release/ports/sysutils/MacPorts DEBUG: Changing to port directory: /opt/local/var/macports/sources/ rsync.macports.org/release/ports/sysutils/MacPorts DEBUG: Requested variant powerpc is not provided by port MacPorts. DEBUG: Requested variant darwin is not provided by port MacPorts. DEBUG: Requested variant macosx is not provided by port MacPorts. DEBUG: Executing variant darwin_8 provides darwin_8 DEBUG: Executing variant darwin_8_powerpc provides darwin_8_powerpc DEBUG: Skipping completed org.macports.main (MacPorts) DEBUG: Skipping completed org.macports.fetch (MacPorts) DEBUG: Skipping completed org.macports.checksum (MacPorts) DEBUG: Skipping completed org.macports.extract (MacPorts) DEBUG: Skipping completed org.macports.patch (MacPorts) ---> Configuring MacPorts DEBUG: Executing proc-pre-org.macports.configure-configure-0 DEBUG: Executing org.macports.configure (MacPorts) DEBUG: Using compiler 'Mac OS X gcc 4.0' DEBUG: Environment: CFLAGS='-O2 -isysroot /Developer/SDKs/ MacOSX10.4u.sdk -arch ppc -arch i386' CXXFLAGS='-O2' CPP='/usr/bin/ cpp-4.0' CXX='/usr/bin/g++-4.0' F90FLAGS='-O2' SHLIB_LDFLAGS='-Wl,- syslibroot,/Developer/SDKs/MacOSX10.4u.sdk -arch ppc -arch i386' OBJC='/usr/bin/gcc-4.0' FCFLAGS='-O2' INSTALL='/usr/bin/install' OBJCFLAGS='-O2' FFLAGS='-O2' CC='/usr/bin/gcc-4.0' DEBUG: Assembled command: 'cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_sysutil s_MacPorts/work/MacPorts-1.6.0" && ./configure --prefix=/opt/local -- enable-readline' configure: error: cannot run /bin/sh ./config.sub Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_release_ports_sysutil s_MacPorts/work/MacPorts-1.6.0" && ./configure --prefix=/opt/local -- enable-readline " returned error 1 Command output: configure: error: cannot run /bin/sh ./config.sub Warning: the following items did not execute (for MacPorts): org.macports.activate org.macports.configure org.macports.build org.macports.destroot org.macports.install Error: Status 1 encountered during processing. $ From paulbeard at gmail.com Thu Jan 3 16:42:10 2008 From: paulbeard at gmail.com (paul beard) Date: Thu Jan 3 16:40:10 2008 Subject: Standardizing a MacPorts system In-Reply-To: <7fccb3000801031217g68fc8832h1df1d9b4cd156fe9@mail.gmail.com> References: <7fccb3000801031217g68fc8832h1df1d9b4cd156fe9@mail.gmail.com> Message-ID: On Jan 3, 2008 12:17 PM, Tabitha McNerney wrote: > Hello all -- > > I would like to build, from source, on an Xserve running Leopard Server, a > "standard" MacPorts system that could be deployed, in an organization, on > numerous other Apple servers running the same version of the OS ( e.g. > Leopard Server). In doing so I would use Apple's command-line tools (such as > hdiutil and asr) create a restorable disk image (.dmg) file of a disc volume > that hangs off an external disk on my original Xserve which houses the > MacPorts prefix ( e.g., /opt/local). I would then restore from this disc > image to the additional machines slated to be the recipients of the original > standard. > I wonder if some combination of nfs (to mount your master repository), rsync (to update your local store) and some voodoo with a regex to update any files that are tied to hostnames (all your master builds might be tagged with "master" or "changeme"). > > I don't see any immediate problems in doing so, however I have noticed > when installing some ports (when I have occasionally enabled verbose mode > "-v" during the install), depending on the port, some ports seem to take > into consideration the Hostname of the Xserve I'm running it on. On my > Xserve running Leopard Server, the Hostname is very importantly tied to the > DNS name because I am running Apple's DNS server that is buncled with > Leopard Server since I need it for other services on the machine which are > not directly related to MacPorts such as running an OpenDirectory Master. > The problem is, with hundreds of MacPorts tied together and with complex > dependency chains, how can anyone determine when a specific MacPort reads > the hostname and uses the hostname of the machine during the configuration > process (unless a sys admin such as myself builds each and every port with > verbose mode and analysis the output grepping for the hostname)? It might be > problematic if the hostname of any given MacPort somehow becomes "hard > wired" into the port itself during the configuration / install processing. > Then again, I might be making a mountain out of a mole hill. > > Has anyone else built a Standardized MacPorts system that is cloned to > multiple Macs? > > Thanks, > > T.M. > > > > _______________________________________________ > macports-users mailing list > macports-users@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-users > > -- Paul Beard / www.paulbeard.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080103/d866def1/attachment.html From tabithamc at gmail.com Thu Jan 3 17:15:49 2008 From: tabithamc at gmail.com (Tabitha McNerney) Date: Thu Jan 3 17:13:50 2008 Subject: Standardizing a MacPorts system In-Reply-To: References: <7fccb3000801031217g68fc8832h1df1d9b4cd156fe9@mail.gmail.com> Message-ID: <7fccb3000801031715r8993d73ocf8f0887a4d518db@mail.gmail.com> On 1/3/08, paul beard wrote: > > > > On Jan 3, 2008 12:17 PM, Tabitha McNerney wrote: > > > Hello all -- > > > > I would like to build, from source, on an Xserve running Leopard Server, > > a "standard" MacPorts system that could be deployed, in an organization, on > > numerous other Apple servers running the same version of the OS ( e.g. > > Leopard Server). In doing so I would use Apple's command-line tools (such as > > hdiutil and asr) create a restorable disk image (.dmg) file of a disc volume > > that hangs off an external disk on my original Xserve which houses the > > MacPorts prefix ( e.g., /opt/local). I would then restore from this disc > > image to the additional machines slated to be the recipients of the original > > standard. > > > > I wonder if some combination of nfs (to mount your master repository), > rsync (to update your local store) and some voodoo with a regex to update > any files that are tied to hostnames (all your master builds might be tagged > with "master" or "changeme"). > Paul, Appreciate the directional suggestion! Probably I could live without NFS and rsync, as I'd probably be ok with with cloning a master courtesy of the diskutil, hdiutil and asr tools on OS X. The regex is probably the way to go! Thanks, T.M. [SNIP] -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20080103/0010f133/attachment-0001.html From ryandesign at macports.org Thu Jan 3 18:17:26 2008 From: ryandesign at macports.org (Ryan Schmidt) Date: Thu Jan 3 18:15:55 2008 Subject: sudo port upgrade outdated > PortUpgradeOutdated.log In-Reply-To: <9345764E-E5AA-4069-A4E9-0568B9E84C89@gmail.com> References: <9345764E-E5AA-4069-A4E9-0568B9E84C89@gmail.com> Message-ID: On Jan 3, 2008, at 14:18, Charlse Darwin wrote: > How do I get the port to write the output to a log file? `$ sudo > po