On Sep 18, 2014, at 10:45, David Strubbe wrote:
>
> Is there a way to access a file such as a config.log from a failed port build
> on a buildslave?
>
> After my recent changes r125398 and r125404 to the abinit port, the build
> failed on Mountain Lion, in the configure stage, as follows:
>
>
On Sep 18, 2014, at 5:13 PM, petr <9...@ingv.it> wrote:
> Not all py24 and py25 subports have py27 equivalents. At first sight it seems
> that quite some of these are no required anymore because either part of the
> standard library (replaced_by python27 ???) or old unmaintained software. But
>
On Sep 18, 2014, at 4:48 PM, petr <9...@ingv.it> wrote:
> +1 for removing 2.4 and 2.5. I would not remove 2.6 for now. It is still well
> supported
By whom? Certainly not by upstream.
> There is also some value in having around for testing, as some very
> conservative Linux distributions still
On 17 Sep 2014, at 16:48, Lawrence Velázquez wrote:
> On Sep 16, 2014, at 5:53 AM, Rainer Müller wrote:
>
>> As soon as they are removed from the PortIndex, they will be matched by
>> the 'obsolete' pseudo-port. You can check for installed ports that are
>> no longer in any ports tree with the
On Sep 18, 2014, at 4:58 PM, petr <9...@ingv.it> wrote:
> On 17 Sep 2014, at 03:43, Ned Deily wrote:
Ned didn't say this; I did.
>> Please don't create new py24, py25, py31, and py32 subports from now on. I'd
>> like to phase out and remove python{26,27,31,32} in the near future.
>
> Is there
On 17 Sep 2014, at 03:43, Ned Deily wrote:
> Please don't create new py24, py25, py31, and py32 subports from now on. I'd
> like to phase out and remove python{26,27,31,32} in the near future.
>
Is there a typo here? Should this read `... remove python{24,25,31,32} in the
near future.` ?
~pe
Hi all,
I already wanted to make a similar proposal (at least for py24) so I am in
favour of this proposal.
+1 for removing 2.4 and 2.5. I would not remove 2.6 for now. It is still well
supported and py26 subports are in general easier to maintain. There is also
some value in having around fo
Hi all,
Is there a way to access a file such as a config.log from a failed port
build on a buildslave?
After my recent changes r125398 and r125404 to the abinit port, the build
failed on Mountain Lion, in the configure stage, as follows:
checking for mpicc-mpich-mp... /opt/local/bin/mpicc-mpich-
On 18/set/2014, at 11:54, Ryan Schmidt wrote:
>
> On Sep 18, 2014, at 4:50 AM, Aljaž Srebrnič wrote:
>>
>> On 18/set/2014, at 03:58, Ryan Schmidt wrote:
>>
>>>
>>>
>>> Checksum mismatch, unsurprisingly:
>>> […]
>>>
>>
>> Yeah, I figured, but a port clean —all && port checksum didn’t show a
On Sep 18, 2014, at 4:50 AM, Aljaž Srebrnič wrote:
>
> On 18/set/2014, at 03:58, Ryan Schmidt wrote:
>
>>
>>> On Sep 17, 2014, at 5:17 AM, g...@macports.org wrote:
>>>
>>> Revision
>>> 125415
>>> Author
>>> g...@macports.org
>>> Date
>>> 2014-09-17 03:17:24 -0700 (Wed, 17 Sep 2014)
>>> Log Mes
On 18/set/2014, at 03:58, Ryan Schmidt wrote:
>
>> On Sep 17, 2014, at 5:17 AM, g...@macports.org wrote:
>>
>> Revision
>> 125415
>> Author
>> g...@macports.org
>> Date
>> 2014-09-17 03:17:24 -0700 (Wed, 17 Sep 2014)
>> Log Message
>>
>> sysutils/rcm
>> move upstream to github
>>
>
> Checks
Thanks, 125454.
On 18/set/2014, at 04:11, Ryan Schmidt wrote:
>
>> On Sep 17, 2014, at 8:40 AM, g...@macports.org wrote:
>>
>> Revision
>> 125429
>> Author
>> g...@macports.org
>> Date
>> 2014-09-17 06:40:55 -0700 (Wed, 17 Sep 2014)
>> Log Message
>>
>> textproc/colout:
>> use python34
>> a
12 matches
Mail list logo
