reverting to a previous version of a port?
I foolishly upgraded to subversion 1.5 without checking to see if my other tools play nicely. Well, they don't. I need to revert to the previous version of Subversion, but I don't see how to. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Howto
Leaving aside the issue of what the best platform for sharing the info might be. If nobody knows it's there, the kick-assingest wiki server the world has or will ever see is not going to address my suggestion in the slightest. My point was that it's quite a challenge finding the current how-to's even if you already know they exist. If you are not in that smallish (I'm guessing--but I've been using *Ports for a fairly long time, and it was a recent message on this list that made me aware) category, then the chances this very useful series of articles will reach the audience that needs it is quite small. Just to refresh, there needs to be a link from the main MacPorts documentation site to the how-to's. As a first step, it's awesome. On Thu, Jun 5, 2008 at 2:22 PM, Jordan K. Hubbard [EMAIL PROTECTED] wrote: On Jun 5, 2008, at 8:42 AM, Lorin Rivers wrote: Awesome! I did not even know about these How To's. You know, it's actually kind of hard to find them, if you don't know about where they are in the first place. I think they deserve more prominence. There should be a link from the documentation area of the main MacPorts site to the HowTo's. I'm still of the opinion that we should install mediawiki on the site and turn these howtos into full-blown, collaboratively maintained reference pages worthy of wikipedia (but, unlike wikipedia, also free to be relevant only in the context of projects hosted at macosforge). What do other folks think? - Jordan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: New Howto
Awesome! I did not even know about these How To's. You know, it's actually kind of hard to find them, if you don't know about where they are in the first place. I think they deserve more prominence. There should be a link from the documentation area of the main MacPorts site to the HowTo's. On Mon, Jun 2, 2008 at 1:11 PM, Martin Krischik [EMAIL PROTECTED] wrote: Hello, just wanted to let you know that I finished a new Howto http://trac.macports.org/wiki/howto/SetupDovecot It's the first of a 3 part series and I hope finish the other parts soon. Martin ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Reading apache, mysql, etc. logs in Console.app automatically
Is there a way to have Console load the logs from /opt/local/apache2/logs automatically? Likewise, mysql, etc? I know I can load them via the open dialog and so on, but it would be nice to not have to do that step ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Apache not starting at boot
That worked! Thanks Robert. On Mon, May 19, 2008 at 11:57 AM, Lorin Rivers [EMAIL PROTECTED] wrote: OK, thanks, I'll try the unload/load mambo and see what happens On Mon, May 19, 2008 at 11:21 AM, Robert Liesenfeld [EMAIL PROTECTED] wrote: On May 19, 2008, at 8:14 AM, Lorin Rivers wrote: I have done some extensive research and have followed all the setup instructions I can find, but apache2 still requires a manual start on my 10.4 iMac. When I run sudo launchctl load -w /Library/LaunchDaemons/org.macports.apache2.plist, the response is already loaded. Manual start doesn't report errors and apache works fine once I do that, but I'd like to not have to remember to start apache next time my power goes out. ... snip ... I found I had problems with launchd on 10.4 as well; in your situation I would usually do a 'launchctl unload -w /Library...' followed by a 'launchctl load -w /Library...'. This seemed to give launchd the prodding it needed. Note also that if Apache fails to start, repeatedly (due to configuration errors), I believe launchd will eventually turn off the daemon and leave it off, such as how init under other UNIXes handles runaway processes. The only other bit of info is that occasionally, I see something about bonjour (couldn't find it just now, though). Also, mysql is starting up just fine... Mysql starting OK indicates that launchd is working well (though I suspect you'd be having much bigger problems if launchd was actually broken :). Can't help you with the Bonjour messages, I'm afraid... -Robert ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Apache not starting at boot
I have done some extensive research and have followed all the setup instructions I can find, but apache2 still requires a manual start on my 10.4 iMac. When I run sudo launchctl load -w /Library/LaunchDaemons/org.macports.apache2.plist, the response is already loaded. Manual start doesn't report errors and apache works fine once I do that, but I'd like to not have to remember to start apache next time my power goes out. Here's the plist: ?xml version=1.0 encoding=UTF-8? !DOCTYPE plist PUBLIC -//Apple Computer//DTD PLIST 1.0//EN http://www.apple. com/DTDs/PropertyList-1.0.dtd plist version=1.0 dict keyDebug/key false/ keyLabel/key stringorg.macports.apache2/string keyOnDemand/key false/ keyProgramArguments/key array string/opt/local/bin/daemondo/string string--label=apache2/string string--start-cmd/string string/opt/local/etc/LaunchDaemons/org.macports.apache2/apache 2.wrapper/string stringstart/string string;/string string--stop-cmd/string string/opt/local/etc/LaunchDaemons/org.macports.apache2/apache 2.wrapper/string stringstop/string string;/string string--restart-cmd/string string/opt/local/etc/LaunchDaemons/org.macports.apache2/apache 2.wrapper/string stringrestart/string string;/string string--pid=none/string /array keyRunAtLoad/key true/ /dict /plist The only other bit of info is that occasionally, I see something about bonjour (couldn't find it just now, though). Also, mysql is starting up just fine... ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Apache not starting at boot
OK, thanks, I'll try the unload/load mambo and see what happens On Mon, May 19, 2008 at 11:21 AM, Robert Liesenfeld [EMAIL PROTECTED] wrote: On May 19, 2008, at 8:14 AM, Lorin Rivers wrote: I have done some extensive research and have followed all the setup instructions I can find, but apache2 still requires a manual start on my 10.4 iMac. When I run sudo launchctl load -w /Library/LaunchDaemons/org.macports.apache2.plist, the response is already loaded. Manual start doesn't report errors and apache works fine once I do that, but I'd like to not have to remember to start apache next time my power goes out. ... snip ... I found I had problems with launchd on 10.4 as well; in your situation I would usually do a 'launchctl unload -w /Library...' followed by a 'launchctl load -w /Library...'. This seemed to give launchd the prodding it needed. Note also that if Apache fails to start, repeatedly (due to configuration errors), I believe launchd will eventually turn off the daemon and leave it off, such as how init under other UNIXes handles runaway processes. The only other bit of info is that occasionally, I see something about bonjour (couldn't find it just now, though). Also, mysql is starting up just fine... Mysql starting OK indicates that launchd is working well (though I suspect you'd be having much bigger problems if launchd was actually broken :). Can't help you with the Bonjour messages, I'm afraid... -Robert ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
samba3 fails to build
I've cleaned and synced and I'm getting failures trying to build Samba. --- Fetching samba3 --- Attempting to fetch samba-3.0.28.tar.gz from http://us1.samba.org/samba/ftp/stable/ --- Verifying checksum(s) for samba3 --- Extracting samba3 --- Configuring samba3 --- Building samba3 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_net_samba3/work/samba-3.0.28/source make all returned error 2 Command output: Compiling libads/ldap_utils.c Compiling libads/authdata.c Compiling libads/cldap.c Compiling libads/kerberos.c Compiling libads/ads_status.c Compiling libads/util.c Compiling libads/kerberos_verify.c Compiling libads/ldap_schema.c Compiling registry/reg_frontend.c Compiling registry/reg_cachehook.c Compiling registry/reg_printing.c Compiling registry/reg_db.c Compiling registry/reg_eventlog.c Compiling registry/reg_shares.c Compiling registry/reg_util.c Compiling registry/reg_dynamic.c Compiling registry/reg_perfcount.c Compiling lib/popt_common.c Compiling smbd/build_options.c Compiling lib/smbldap.c Compiling lib/smbldap_util.c Compiling smbd/server.c mkdir bin Linking bin/smbd Undefined symbols: _updwtmpx, referenced from: _sys_utmp_update in utmp.o ld: symbol(s) not found collect2: ld returned 1 exit status make: *** [bin/smbd] Error 1 Error: Unable to upgrade port: 1 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: samba3 fails to build
PowerBook G4, 10.5.1 On Dec 11, 2007 5:24 PM, Weissmann Markus [EMAIL PROTECTED] wrote: what system are you on? -Markus On 11.12.2007, at 23:36, Lorin Rivers wrote: I've cleaned and synced and I'm getting failures trying to build Samba. --- Fetching samba3 --- Attempting to fetch samba-3.0.28.tar.gz from http://us1.samba.org/samba/ftp/stable/ --- Verifying checksum(s) for samba3 --- Extracting samba3 --- Configuring samba3 --- Building samba3 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_net_s amba3/work/samba-3.0.28/source make all returned error 2 Command output: Compiling libads/ldap_utils.c Compiling libads/authdata.c Compiling libads/cldap.c Compiling libads/kerberos.c Compiling libads/ads_status.c Compiling libads/util.c Compiling libads/kerberos_verify.c Compiling libads/ldap_schema.c Compiling registry/reg_frontend.c Compiling registry/reg_cachehook.c Compiling registry/reg_printing.c Compiling registry/reg_db.c Compiling registry/reg_eventlog.c Compiling registry/reg_shares.c Compiling registry/reg_util.c Compiling registry/reg_dynamic.c Compiling registry/reg_perfcount.c Compiling lib/popt_common.c Compiling smbd/build_options.c Compiling lib/smbldap.c Compiling lib/smbldap_util.c Compiling smbd/server.c mkdir bin Linking bin/smbd Undefined symbols: _updwtmpx, referenced from: _sys_utmp_update in utmp.o ld: symbol(s) not found collect2: ld returned 1 exit status make: *** [bin/smbd] Error 1 Error: Unable to upgrade port: 1 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users --- Dipl. Inf. (FH) Markus W. Weissmann http://www.mweissmann.de/ http://www.macports.org/ ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
port -f upgrade port rebuilds already installed stuff
I recall that using port -f upgrade outdated would do this (reinstall stuff that was not outdated) but that, until today, performing the same command on an individual port would only install what was out-of-date. Today, however, when I upgrade the few ports that were outdated, lots of stuff was rebuilt, some of it for every port I upgraded. What changed to cause this? I'm pretty sure this is new. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Cannot install PNGmeta
Maybe you could try PMT? It seems pngmeta is part of that and maybe it's cleaner. I don't know. http://sourceforge.net/projects/pmt/ On 10/11/07, Martin Stadler [EMAIL PROTECTED] wrote: Hi! I just tried to install pngmeta with the output below. I use MacPorts 1.520 on OS-X 10.4.10 (intel). Xcode 2.4.1 libpng @1.2.21_0+darwin_8 (active) zlib @1.2.3_1 (active) $ sudo port install pngmeta Password: --- Fetching pngmeta --- Attempting to fetch pngmeta-1.11.tar.gz from http:// downloads.sourceforge.net/pmt --- Verifying checksum(s) for pngmeta --- Extracting pngmeta --- Configuring pngmeta --- Building pngmeta 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_graphic s_pngmeta/work/pngmeta-1.11 make all returned error 2 Command output: gcc -DPACKAGE=\pngmeta\ -DVERSION=\1.11\ - DHAVE_LIBZ=1 -DHAVE_LIBPNG=1 -DHAVE_PNG_CREATE_READ_STRUCT=1 - DHAVE_PNG_GET_TEXT=1 -I. -I.-I/opt/local/include -O2 -I/opt/ local/include -I/opt/local/include -c pngmeta.c gcc -O2 -I/opt/local/include -I/opt/local/include -L/opt/local/lib - o pngmeta pngmeta.o -lpng -lz -L/opt/local/include -L/opt/local/ include -lpng -L/opt/local/lib -lm -L/opt/local/lib /usr/bin/ld: Undefined symbols: _png_IDAT _png_IEND _png_IHDR _png_crc_finish _png_crc_read _png_handle_IEND _png_handle_IHDR _png_handle_tEXt _png_handle_tIME _png_handle_unknown _png_handle_zTXt _png_read_data _png_read_destroy _png_reset_crc _png_tEXt _png_tIME _png_zTXt collect2: ld returned 1 exit status make: *** [pngmeta] Error 1 Error: Status 1 encountered during processing. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Installing MacPorts
Jason,
I reckon that your problems will be solved by fixing the last export
PATH. Unless it's a typo in your email, it appears that you forgot
the :$PATH at the end of your last export PATH.
There's a priority in the ordering that's normally not super-critical.
In your case, if you want MacPython to be used instead of other
installed Pythons, that requires MacPython to be at the front of the
PATH variable. The same is true regarding MySQL. FYI.
HTH
On 9/19/07, Jason Nerida [EMAIL PROTECTED] wrote:
Hello,
I'm new to MacPorts and have a question regarding install of MacPorts:
How do I correct the PATH to point to the MacPorts path?
I combined my .bash_login AND .bash_profile into .profile as
instructed and also tried deleting them and leaving only .profile, but
the PATH will not report the MacPorts path
files:
.bash_login:
export PATH=/usr/local/bin:/usr/local/sbin:$PATH
.bash_profile:
export PATH=/usr/local/mysql/bin:$PATH
# Setting PATH for MacPython 2.5
# The orginal version is saved in .bash_profile.pysave
PATH=/Library/Frameworks/Python.framework/Versions/Current/bin:${PATH}
export PATH
combined into .profile:
##
# DELUXE-USR-LOCAL-BIN-INSERT
# (do not remove this comment)
##
echo $PATH | grep -q -s /usr/local/bin
if [ $? -eq 1 ] ; then
PATH=$PATH:/usr/local/bin
export PATH
fi
#
# Your previous .profile (if any) is saved as .profile.mpsaved
# Setting the path for MacPorts.
export PATH=/opt/local/bin:/opt/local/sbin:$PATH
export DISPLAY=:0.0
export PATH=/usr/local/mysql/bin:$PATH
# Setting PATH for MacPython 2.5
# The orginal version is saved in .bash_profile.pysave
PATH=/Library/Frameworks/Python.framework/Versions/Current/bin:${PATH}
export PATH
export PATH=/usr/local/bin:/usr/local/sb
Thanks for any help with this,
Jason
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Cannot execute sudo port selfupdate
I was getting this error message on a different port and I was able to get past it by doing: sudo port clean all sudo port sync sudo port selfupdate Hope that helps. On 9/12/07, M.W. Rails [EMAIL PROTECTED] wrote: When I try to perform the selfupdate I get the following error message: MacPorts base version 1.5 installed Downloaded MacPorts base version 1.520 Configuring, Building and Installing new MacPorts base Error: /opt/local/bin/port: selfupdate failed: Error installing new MacPorts base: shell command cd /opt/local/var/macports/sources/rsync.macports.org/release/base ./configure --prefix=/opt/local --with-install-user=root --with-install-group=admin --with-tclpackage=/Library/Tcl make make install returned error 77 Command output: checking build system type... i686-apple-darwin8.10.1 checking host system type... i686-apple-darwin8.10.1 checking target system type... i686-apple-darwin8.10.1 checking for gcc... gcc checking for C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details. I cannot find any config.log anywhere on the system so I do not think it is being created. I have downloaded and installed the Apple Developer Tools gcc -v shows gcc version 4.0.1 (Apple Computer, Inc. build 5367) Can anyone help me figure out what I am doing wrong. Thank you! mwrails ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
What does Milestone: Port Bugs mean?
I've noticed some of the ports that are triggering this getting fixed right away. What does this disposition indicate? -- Forwarded message -- From: MacPorts [EMAIL PROTECTED] Date: Aug 14, 2007 6:40 PM Subject: Re: [MacPorts] #12476: cadaver install fails with mtree violation To: [EMAIL PROTECTED] #12476: cadaver install fails with mtree violation +--- Reporter: [EMAIL PROTECTED] | Owner: [EMAIL PROTECTED] Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.5.0 Resolution: |Keywords: cadaver mtree +--- Changes (by [EMAIL PROTECTED]): * milestone: = Port Bugs * cc: = [EMAIL PROTECTED], [EMAIL PROTECTED] -- Ticket URL: https://trac.macports.org/projects/macports/ticket/12476 MacPorts /projects/macports Ports system for Mac OS ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
cadaver install fails with mtree violation
Here's a ilnk to the trac ticket http://trac.macports.org/projects/macports/ticket/12476 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Discover new ports
Is there an easy way to discover what new ports have been added to MacPorts? By new, I mean not previously part of MacPorts as opposed to an existing port that's been updated. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts roadmap new milestones
I found the change notes. As a marketing gesture, I suggest you post same on the Wiki as part of the release process. On 3/27/07, Lorin Rivers [EMAIL PROTECTED] wrote: Is there a What's new document (short of reading all the tickets)? On 3/25/07, Juan Manuel Palacios [EMAIL PROTECTED] wrote: Evening everyone! Thanks to the kind help provided by Elias Pipping, our new project roadmap is up at: http://trac.macports.org/projects/macports/roadmap For those of you who actively use it, the major changes you'll notice are that the Available Ports milestone has been deleted (tickets belonging to it reassigned according to the new guidelines referenced below) and four new ones have been added: Port Bugs, Port Enhancements, Port Updates and Needs developer review. The guidelines to use them all will be shortly up at: http://trac.macports.org/projects/macports/wiki/TracTicketing [1] Needless to say, these wont be Godly mandates, but I would still like to request that all those of you with Wiki edit privileges wishing to give your feedback input on them run by me any edits you might want to make to that document (Elias and I just spent several hours cleaning up the old roadmap, so we can tell you that dealing with so many tickets gets a bit tiring a bit too quickly, and therefore we would like to avoid ambiguous instructions as much as possible!). Regards to all and thanks again to Elias! -jmpp [1] Out of date with respect to the new layout as of this posting, g'me some time to work on the document and bring it up to speed, I'm beat right now! I am nevertheless still sending this message *now* (with an old document in place) because I fear some might get confused with the new and missing milestones and no information what-so-ever on the changes. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
mysql5 checksum failures
Something odd appears to be going on with the mysql port, ca. mysql-5.0.36. The checksums (md5 and sha1) are reported to be different in the portfile and in the distfile. If I replace the values in the portfile with those reported in the error message for the distfiles, I subsequently get a message about the downloaded file not being in gzip format. Inspecting the download sites listed in the porfile, the highest version number I see is 5.0.27. There's a 5.1.16 and a 5.2.3 (in other directories). I'm not sure what to do to get mysql installed, though, which I would like to do... Thanks! ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: mysql5 checksum failures
There a ticket open in Trac about this: http://trac.macports.org/projects/macports/ticket/11487 On 3/6/07, Lorin Rivers [EMAIL PROTECTED] wrote: Something odd appears to be going on with the mysql port, ca. mysql-5.0.36. The checksums (md5 and sha1) are reported to be different in the portfile and in the distfile. If I replace the values in the portfile with those reported in the error message for the distfiles, I subsequently get a message about the downloaded file not being in gzip format. Inspecting the download sites listed in the porfile, the highest version number I see is 5.0.27. There's a 5.1.16 and a 5.2.3 (in other directories). I'm not sure what to do to get mysql installed, though, which I would like to do... Thanks! ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
