subversion 1.7.0

If you use subversion, be aware that the just-released 1.7.0 seems to have a few problems. I for one am waiting until at least Subversion 1.7.1 before I upgrade. Summary of the issues I've seen mentioned on the Subversion users mailing list so far: * Working copies, especially month

Re: MacPorts-1.7.0-10.5-Leopard.dmg.asc or MacPorts-1.7.0-10.5-Leopard.dmg

two for Leopard: >> >> MacPorts-1.7.0-10.5-Leopard.dmg.asc< >> http://svn.macports.org/repository/macports/downloads/MacPorts-1.7.0/MacPorts-1.7.0-10.5-Leopard.dmg.asc >> > >> >> and >> >> MacPorts-1.7.0-10.5-Leopard.dmg.asc< >> http://svn

Re: MacPorts-1.7.0-10.5-Leopard.dmg.asc or MacPorts-1.7.0-10.5-Leopard.dmg

The .asc is a GPG signature to verify your download. Just grab the dmg. On Jan 17, 2009, at 13:20, Liz Panton wrote: I have got as far as the list of downloads, but there are two for Leopard: MacPorts-1.7.0-10.5-Leopard.dmg.asc<http://svn.macports.org/repository/macports/downloads/MacPo

MacPorts-1.7.0-10.5-Leopard.dmg.asc or MacPorts-1.7.0-10.5-Leopard.dmg

I have got as far as the list of downloads, but there are two for Leopard: MacPorts-1.7.0-10.5-Leopard.dmg.asc<http://svn.macports.org/repository/macports/downloads/MacPorts-1.7.0/MacPorts-1.7.0-10.5-Leopard.dmg.asc> and MacPorts-1.7.0-10.5-Leopard.dmg.asc<http://svn.macports.org/r

Re: MacPorts 1.7.0 has been released

Bart Masschelein wrote: > Well, appart from sth I don't know if it is a MacPorts issue. I did an > upgrade of my outdated ports, and iso-codes needed to be installed as > well apparantly. And it was waiting to fetch the source for half an > hour at least, waiting on: > > ---> Attempting to

Re: MacPorts 1.7.0 has been released

A big thanks to the developers for their hard work with all of the various features and bug fixes in 1.7.0. Many thanks and congratulations from a happy user indeed!!! Upgrade went smooth... Well, appart from sth I don't know if it is a MacPorts issue. I did an upgrade of my out

Re: MacPorts 1.7.0 has been released

On Sun, Dec 14, 2008 at 09:58:02AM +0100, Jochen Küpper said: [...] > > Anyway, here's my experience, showing one old bug (which currently has a > trac milestone of 1.7.1) and an issue with sources.conf, which might be > due to a change of the files' format? Anyway, easy to get along, hope > it'

Re: MacPorts 1.7.0 has been released

On 14.12.2008, at 05:13, Bryan Blackburn wrote: The MacPorts Project is happy to announce that, after nearly a year in the making, the 1.7.0 version has been released. Great. Thank you very much, all you have contributed! It's nice to see that "restructuring of the organizat

Re: MacPorts 1.7.0 has been released

Bryan Blackburn wrote: > The MacPorts Project is happy to announce that, after nearly a year in > the making, the 1.7.0 version has been released. It is now available > via the usual methods: Kudos to Bryan for his work in packaging this release. > The list of what's new

Re: MacPorts 1.7.0 has been released

On Dec 13, 2008, at 11:13 PM, Bryan Blackburn wrote: The MacPorts Project is happy to announce that, after nearly a year in the making, the 1.7.0 version has been released. It is now available via ./snip/ A big thanks to the developers for their hard work with all of the various

MacPorts 1.7.0 has been released

The MacPorts Project is happy to announce that, after nearly a year in the making, the 1.7.0 version has been released. It is now available via the usual methods: - selfupdate if you already have it installed - package installers in DMGs for 10.3 [1], 10.4 [2], and 10.5 [3] (the latter two

Re: 1.7.0 beta & rc1: libcurl errors

On Dec 9, 2008, at 07:20, Jay Levitt wrote: Joshua Root wrote: Could the wrong libcurl be picked up if there is something like LDFLAGS=-L/opt/local/lib in the environment? If that's what happened to Jay, it shouldn't be a problem with selfupdate because the environment is sanitised. I

Re: 1.7.0 beta & rc1: libcurl errors

On Dec 9, 2008, at 07:38, Jay Levitt wrote: Does MacPorts log any history anywhere? I don't think it does. Nope, MacPorts writes no logfiles. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/l

Re: 1.7.0 beta & rc1: libcurl errors

Vincent Lefevre wrote: > On 2008-12-09 13:45:30 +0100, Rainer Müller wrote: >> MacPorts already removes $prefix/bin and $prefix/sbin from PATH on >> configure. > > Does it also handle environment variables such as LIBRARY_PATH, > CPATH and C_INCLUDE_PATH? It clears the entire environment apart fr

Re: 1.7.0 beta & rc1: libcurl errors

On 2008-12-09 13:45:30 +0100, Rainer Müller wrote: > MacPorts already removes $prefix/bin and $prefix/sbin from PATH on > configure. Does it also handle environment variables such as LIBRARY_PATH, CPATH and C_INCLUDE_PATH? -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: 10

Re: 1.7.0 beta & rc1: libcurl errors

Jay Levitt wrote: > Joshua Root wrote: > >> Could the wrong libcurl be picked up if there is something like >> LDFLAGS=-L/opt/local/lib in the environment? If that's what happened to >> Jay, it shouldn't be a problem with selfupdate because the environment >> is sanitised. > > I do, in fact, have

Re: 1.7.0 beta & rc1: libcurl errors

Bryan Blackburn wrote: On Mon, Dec 08, 2008 at 03:25:19PM -0500, Jay Levitt said: I know this isn't a great bug report, because I already overwrote the fail case; sorry about that. I upgraded from a DMG-installed 1.6.0 to a built-from-source 1.7.0 beta 1. I then updated a bunch of ports

Re: 1.7.0 beta & rc1: libcurl errors

Joshua Root wrote: Could the wrong libcurl be picked up if there is something like LDFLAGS=-L/opt/local/lib in the environment? If that's what happened to Jay, it shouldn't be a problem with selfupdate because the environment is sanitised. I do, in fact, have that: CPATH=/opt/local/include CP

Re: 1.7.0 beta & rc1: libcurl errors

Bryan Blackburn wrote: > Considering that the MacPorts port clears configure.cppflags and > configure.ldflags, I'm guessing the same should probably be done in > macports::selfupdate? MacPorts already removes $prefix/bin and $prefix/sbin from PATH on configure. See MP_PATH_SCAN in aclocal.m4. This

Re: 1.7.0 beta & rc1: libcurl errors

On Tue, Dec 09, 2008 at 10:04:03AM +1100, Joshua Root said: [...] > > Could the wrong libcurl be picked up if there is something like > LDFLAGS=-L/opt/local/lib in the environment? If that's what happened to > Jay, it shouldn't be a problem with selfupdate because the environment > is sanitised.

Re: 1.7.0 beta & rc1: libcurl errors

Bryan Blackburn wrote: > On Mon, Dec 08, 2008 at 04:19:41PM -0600, Ryan Schmidt said: >> On Dec 8, 2008, at 15:41, Bryan Blackburn wrote: >> >>> On Mon, Dec 08, 2008 at 03:25:19PM -0500, Jay Levitt said: >>> I tried to rebuild the port, but the port command had the same problem: >>

Re: 1.7.0 beta & rc1: libcurl errors

Ryan Schmidt wrote: > On Dec 8, 2008, at 15:41, Bryan Blackburn wrote: > >> On Mon, Dec 08, 2008 at 03:25:19PM -0500, Jay Levitt said: >> >>> I tried to rebuild the port, but the port command had the same problem: >>> >>> sudo port clean git >>> couldn't load file >>> "/opt/local/share/macports/Tc

Re: 1.7.0 beta & rc1: libcurl errors

On Mon, Dec 08, 2008 at 04:19:41PM -0600, Ryan Schmidt said: > On Dec 8, 2008, at 15:41, Bryan Blackburn wrote: > >> On Mon, Dec 08, 2008 at 03:25:19PM -0500, Jay Levitt said: >> >>> I tried to rebuild the port, but the port command had the same >>> problem: >>> >>> sudo port clean git >>> couldn

Re: 1.7.0 beta & rc1: libcurl errors

On Dec 8, 2008, at 15:41, Bryan Blackburn wrote: On Mon, Dec 08, 2008 at 03:25:19PM -0500, Jay Levitt said: I tried to rebuild the port, but the port command had the same problem: sudo port clean git couldn't load file "/opt/local/share/macports/Tcl/pextlib1.0/Pextlib.dylib": dlopen(/opt/lo

Re: 1.7.0 beta & rc1: libcurl errors

On Mon, Dec 08, 2008 at 03:25:19PM -0500, Jay Levitt said: > I know this isn't a great bug report, because I already overwrote the fail > case; sorry about that. > > I upgraded from a DMG-installed 1.6.0 to a built-from-source 1.7.0 beta 1. > I then updated a bunch of port

1.7.0 beta & rc1: libcurl errors

I know this isn't a great bug report, because I already overwrote the fail case; sorry about that. I upgraded from a DMG-installed 1.6.0 to a built-from-source 1.7.0 beta 1. I then updated a bunch of ports, but I don't think libcurl was one of them. (Is there a log? I don't

Re: macports 1.7.0 and gnome

On Dec 7, 2008, at 6:36 PM, Joshua Root wrote: William Davis wrote: using MacPorts 1.7.0_rc1 to install gnome (sudo port -d install gnome) I got this error --> Activating gnome-session @2.24.1_0 Error: Target org.macports.activate returned: Image error: /opt/local/share/xsessions/gnome.desk

Re: macports 1.7.0 and gnome

William Davis wrote: > using MacPorts 1.7.0_rc1 to install gnome (sudo port -d install gnome) I > got this error > --> Activating gnome-session @2.24.1_0 > Error: Target org.macports.activate returned: Image error: > /opt/local/share/xsessions/gnome.desktop is being used by the active gdm > port.

macports 1.7.0 and gnome

using MacPorts 1.7.0_rc1 to install gnome (sudo port -d install gnome) I got this error --> Activating gnome-session @2.24.1_0 Error: Target org.macports.activate returned: Image error: /opt/local/ share/xsessions/gnome.desktop is being used by the active gdm port. Please deactivate this po

Re: 1.7.0 release candidate 1 available for testing

On Dec 7, 2008, at 2:10 PM, Joshua Root wrote: William Davis wrote: On Dec 7, 2008, at 6:27 AM, Joshua Root wrote: Hmm, looks like the attachment was scrubbed in the archives, so here's a link to the announcement on -dev:

Re: 1.7.0 release candidate 1 available for testing

William Davis wrote: > > On Dec 7, 2008, at 6:27 AM, Joshua Root wrote: > >> Hmm, looks like the attachment was scrubbed in the archives, so here's a >> link to the announcement on -dev: >> >> >> >> >> - Josh >> __

Re: 1.7.0 release candidate 1 available for testing

On Dec 7, 2008, at 6:27 AM, Joshua Root wrote: Hmm, looks like the attachment was scrubbed in the archives, so here's a link to the announcement on -dev: - Josh ___

Re: 1.7.0 release candidate 1 available for testing

Hmm, looks like the attachment was scrubbed in the archives, so here's a link to the announcement on -dev: - Josh ___ macports-users mailing list macports-users@lists.macosfo

1.7.0 release candidate 1 available for testing

sl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTPSA id 4FCEC835FC for <[EMAIL PROTECTED]>; Sun, 7 Dec 2008 04:44:41 -0500 (EST) Date: Sun, 7 Dec 2008 02:44:39 -0700 From: Bryan Blackburn <[EMAIL PROTECTED]> To: MacPorts Dev <[EMAIL PROTECTED]> Subject: 1.7.

Re: 1.7.0

On Jul 24, 2008, at 01:35, Martin Krischik wrote: > Zitat von Ryan Schmidt <[EMAIL PROTECTED]>: > >> them all. (Before 1.7.0, use "port -f uninstall inactive".) > > I keep reading about 1.7.0 all the time still the website clearly > states > >> L

1.7.0 (Was: Clean way to uninstall outdated inactive ports)

Zitat von Ryan Schmidt <[EMAIL PROTECTED]>: > them all. (Before 1.7.0, use "port -f uninstall inactive".) I keep reading about 1.7.0 all the time still the website clearly states > Latest MacPorts release: 1.6.0 So what is this mystical and sacred 1.7.0 release I