On Feb 21, 2012, at 00:48, Joshua Root wrote:
> 'port sync' now fails for me with
> https://svn.macports.org/repository/macports/trunk/dports in
> sources.conf. Error is "Server certificate verification failed: issuer
> is not trusted".
>
> It seems that the subversion port doesn't know about th
On Feb 19, 2012, at 9:57 PM, Dan Ports wrote:
> I haven't found anything that depends on autoconf being in /usr/bin,
> but I did see a couple ports (metakit and pfe) that try to copy
> /usr/bin/glibtool into their build directory.
Somewhere out there, I hear the sound of MacPorts' decision to i
On Tue, Feb 21, 2012 at 05:14:36PM +1100, Joshua Root wrote:
> Seems to work OK in my basic testing. The sooner we catch any problems
> and get a release out, the better.
I have been testing this and think we're close to ready for release.
I haven't had any problems with it once correctly set up.
Please try running 'sudo xcodebuild' and accepting the license as root. That
should allow all users on the system to use XCode (including the macports user).
--Jeremy
On Feb 18, 2012, at 02:11, Joshua Root wrote:
> So it looks like we can't support Xcode 4.3 until there's a fix or
> workaround
'port sync' now fails for me with
https://svn.macports.org/repository/macports/trunk/dports in
sources.conf. Error is "Server certificate verification failed: issuer
is not trusted".
It seems that the subversion port doesn't know about the Apple-supplied
root certs, and it's really inconvenient to
Seems to work OK in my basic testing. The sooner we catch any problems
and get a release out, the better.
- Josh
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
On Feb 20, 2012, at 10:52 PM, Ryan Schmidt wrote:
>
> On Feb 20, 2012, at 23:27, macsforever2...@macports.org wrote:
>
>> Revision: 90078
>>http://trac.macports.org/changeset/90078
>> Author: macsforever2...@macports.org
>> Date: 2012-02-20 21:27:58 -0800 (Mon, 20 Feb 2012)
>> Log
On Feb 20, 2012, at 23:27, macsforever2...@macports.org wrote:
> Revision: 90078
> http://trac.macports.org/changeset/90078
> Author: macsforever2...@macports.org
> Date: 2012-02-20 21:27:58 -0800 (Mon, 20 Feb 2012)
> Log Message:
> ---
> dvdisaster: maintainer update to ve
On 2012-2-21 08:06 , Blair Zajac wrote:
> # /usr/bin/sqlite3 registry.db
> SQLite version 3.7.7 2011-06-25 16:35:41
> Enter ".help" for instructions
> Enter SQL statements terminated with a ";"
> sqlite> select id from ports where name = 'mercurial';
> Error: no such collation sequence: VERSION
Ah
On Feb 20, 2012, at 5:40 PM, Dan Ports wrote:
> On Mon, Feb 20, 2012 at 07:41:00AM -0800, James Berry wrote:
>> Any more information you can give about the failure mode would be
>> appreciated. According to my testing, xcode-select -print-path can be safely
>> run even if you've never agreed to
On Mon, Feb 20, 2012 at 07:41:00AM -0800, James Berry wrote:
> Any more information you can give about the failure mode would be
> appreciated. According to my testing, xcode-select -print-path can be safely
> run even if you've never agreed to the Xcode agreement, so I don't think
> that's what
On Feb 20, 2012, at 15:06, Blair Zajac wrote:
> # /usr/bin/sqlite3 registry.db
> SQLite version 3.7.7 2011-06-25 16:35:41
> Enter ".help" for instructions
> Enter SQL statements terminated with a ";"
> sqlite> select id from ports where name = 'mercurial';
> Error: no such collation sequence: VER
On 2/17/12 11:54 PM, Joshua Root wrote:
On 2012-2-18 08:15 , Blair Zajac wrote:
:msg:deactivate ---> Deactivating mercurial @2.0.1_0+bash_completion
:debug:deactivate
/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/mercerial/locale/zh_CN/LC_MESSAGES/hg.m
On Feb 19, 2012, at 9:40 PM, Dan Ports wrote:
> On Sun, Feb 19, 2012 at 04:45:44PM -0500, Daniel J. Luke wrote:
>> It's somewhat debatable that 'fixing' this by having the modules build with
>> configure.compiler is really the right thing here (there is a reason why
>> upstream tries to make both
On Feb 19, 2012, at 8:06 PM, Ryan Schmidt wrote:
> On Feb 19, 2012, at 16:11, Art McGee wrote:
I've got MacPorts, Fink, and Pkgsrc co-existing on my machine, and
they're working OK so far.
>>>
>>> I hope that means that you have both MacPorts and Fink configured for
>>> nonstandard pref
On Feb 20, 2012, at 1:49 AM, Joshua Root wrote:
> On 2012-2-20 19:32 , Dan Ports wrote:
>> On Mon, Feb 20, 2012 at 05:48:55PM +1100, Joshua Root wrote:
>>> On 2012-2-20 11:14 , jberry at macports.org wrote:
Use xcrun -find to find xcode compiler if it's not found in /usr/bin.
>>>
>>> I deli
On Feb 20, 2012, at 3:15 AM, Dan Ports wrote:
> On Fri, Feb 17, 2012 at 10:32:48AM -0800, James Berry wrote:
>>> (2) If developer_dir is not set, or is not correct, do the following,
>>> in order
>>>
>>> (a) Use any valid value from: xcode-select -print-path (the
>>> user has c
On Fri, Feb 17, 2012 at 10:32:48AM -0800, James Berry wrote:
> > (2) If developer_dir is not set, or is not correct, do the following,
> > in order
> >
> > (a) Use any valid value from: xcode-select -print-path (the
> > user has chosen an Xcode, or Xcode's default is correct)
[.
On Mon, Feb 20, 2012 at 08:49:24PM +1100, Joshua Root wrote:
> On 2012-2-20 19:32 , Dan Ports wrote:
> > Does that mean we'll have to require people to have both Xcode and the
> > command-line tools package installed?
>
> Yes, that seems the best way to avoid future problems if the compiler
> path
On 2012-2-20 19:32 , Dan Ports wrote:
> On Mon, Feb 20, 2012 at 05:48:55PM +1100, Joshua Root wrote:
>> On 2012-2-20 11:14 , jberry at macports.org wrote:
>>> Use xcrun -find to find xcode compiler if it's not found in /usr/bin.
>>
>> I deliberately didn't merge these, and the changes in r90031, in
On 02/17/2012 05:03 AM, Jack Howarth wrote:
I've confirmed that for both the clean install of Xcode 4.3/Command Line
Tools
as well as the upgrade install of Xcode 4.3/Command Line Tools over Xcode 4.2.1
that the developer directory path isn't being set. This results in 'xcodebuild
-version'
On Mon, Feb 20, 2012 at 05:48:55PM +1100, Joshua Root wrote:
> On 2012-2-20 11:14 , jberry at macports.org wrote:
> > Use xcrun -find to find xcode compiler if it's not found in /usr/bin.
>
> I deliberately didn't merge these, and the changes in r90031, in order
> to minimise the changes made on t
22 matches
Mail list logo
