On 8 Apr 2017, at 03:18, Ryan Schmidt wrote:
> That does look like the error described in #52922, but it is marked as fixed.
> What version of Xcode do you have on Mountain Lion? If it's not 5.1.1,
> upgrade to that, and the corresponding version of the command line tools.
Xcode 5.1.1, up-to-dat
On 8 Apr 2017, at 03:27, Ryan Schmidt wrote:
> On Apr 1, 2017, at 09:35, db wrote:
>> Could someone from MP team shed some light on this, please?
> All of MacPorts is on a best-effort basis. There is no guarantee of anything.
> Most of us are volunteers working on MacPorts in our spare time on wh
> On Apr 9, 2017, at 04:18, db wrote:
>
> On 8 Apr 2017, at 03:18, Ryan Schmidt wrote:
>> That does look like the error described in #52922, but it is marked as fixed.
>> What version of Xcode do you have on Mountain Lion? If it's not 5.1.1,
>> upgrade to that, and the corresponding version of
> On Apr 9, 2017, at 04:36, db wrote:
>
> On 8 Apr 2017, at 03:27, Ryan Schmidt wrote:
>> On Apr 1, 2017, at 09:35, db wrote:
>>> Could someone from MP team shed some light on this, please?
>> All of MacPorts is on a best-effort basis. There is no guarantee of
>> anything. Most of us are volun
On 9 Apr 2017, at 11:38, Ryan Schmidt wrote:
> I'd file a new ticket to start with, and mention #52922.
Fine, #53949.
On 9 Apr 2017, at 11:39, Ryan Schmidt wrote:
> Whether or not you use non-default variants, you can either automate the
> reinstallation of ports using the script mentioned in 3.e, or you can do it
> manually.
Ok, that tcl script states in the comments
# Once "good enough", integrate into port
On 8 Apr 2017, at 02:28, Stephen Baber wrote:
> JPortsUI has been updated due to an error when loading the port index.
I get an error when launching it from systems almost identical: OS X 10.8.5,
Java 1.6.0_65, port 2.4.1.
One uses rsync for the tree, another uses github and shows this error me
I checked #43923. Is there any workaround?
> On Apr 9, 2017, at 8:03 AM, db wrote:
>
> On 8 Apr 2017, at 02:28, Stephen Baber wrote:
>> JPortsUI has been updated due to an error when loading the port index.
>
> I get an error when launching it from systems almost identical: OS X 10.8.5,
> Java 1.6.0_65, port 2.4.1.
>
> One uses rsync
On Apr 9, 2017, at 10:06, db wrote:
> I checked #43923. Is there any workaround?
Pallet is broken for many reasons; there are many tickets. Someone needs to fix
the code. There may have been some work done on this in another branch some
time ago that hasn't yet been merged to master...
On 10/04/2017, at 12:43 PM, Ryan Schmidt wrote:
> On Apr 9, 2017, at 10:06, db wrote:
>
>> I checked #43923. Is there any workaround?
>
> Pallet is broken for many reasons; there are many tickets. Someone needs to
> fix the code. There may have been some work done on this in another branch
> s
On Apr 9, 2017, at 21:53, Ian Wadham wrote:
> On 10/04/2017, at 12:43 PM, Ryan Schmidt wrote:
>> On Apr 9, 2017, at 10:06, db wrote:
>>
>>> I checked #43923. Is there any workaround?
>>
>> Pallet is broken for many reasons; there are many tickets. Someone needs to
>> fix the code. There may ha
12 matches
Mail list logo