> On 12 Aug 2017, at 16:48, Ken Cunningham
> wrote:
>
>
>> On Aug 11, 2017, at 7:05 PM, Ken Cunningham
>> wrote:
>>
>> While this is getting sorted out properly...
>
>
> See: https://github.com/macports/macports-ports/pull/662
I am amazed at what you have achieved. All I’ve managed to do
> On 11 Aug 2017, at 09:50, Ken Cunningham
> wrote:
>
> indeed, without the full log cant tell what is wrong.
>
> Best, K
Sorry about that. Here is the full log.
Barrie.
main.log
Description: Binary data
> On Aug 11, 2017, at 10:41 AM, Barrie Stott wrote:
>>
On 11 Aug 2017, at 08:52, Ryan Schmidt wrote:
>
> On Aug 11, 2017, at 01:21, Barrie Stott wrote:
>
>> I don’t remember having a problem with the lout port until I moved to
>> Sierra. Now all my ports are fine except lout.
>
> Could you be more specific about wha
I don’t remember having a problem with the lout port until I moved to Sierra.
Now all my ports are fine except lout.
Barrie.
On 27 May 2017, at 13:11, Ryan Schmidt wrote:
>
> Barrie,
>
> The error in your log says:
>
>> :error:install Failed to install bash: no destroot found at:
>> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_shells_bash/bash/work/
On 27 May 2017, at 09:13, Dave Horsfall wrote:
>
> Does not /bin/bash come with the base system on your box? It does on
> mine, and has for years.
>
> --
> Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
Thanks for the reply and yes it does. I’ve been behaving
Many thanks to the 5 people who wrote in answer to my query about using
+universal. Your contributions all pointed the same way so I am now fully
convinced that I have NEVER needed i386 and will not be using +universal in the
future. Your help has been invaluable and I’m very grateful.
Barrie.
On 29 Apr 2017, at 16:13, Richard L. Hamilton wrote:
>
> In favor of getting rid of it, the pre-built binaries (much faster to install
> or upgrade) aren't built +universal; so if you get rid of it, you'll often
> get them. Some things aren't pre-built, so you won't always get them, but
> it'
> On 4 Apr 2017, at 15:36, Ryan Schmidt wrote:
>
> On Apr 4, 2017, at 02:44, Barrie Stott wrote:
>
>> I have some questions:
>>
>> 1. After loading Sierra I noticed that the m/c was slower. Looking at a file
>> to display a dozen or so lines in an
> On 4 Apr 2017, at 12:02, db wrote:
>
> On 4 Apr 2017, at 09:44, Barrie Stott wrote:
>> 2. I would like to be able to take a requested port and find the tree of
>> ports that would need to be installed before this port.
>
> http://apple.stackexchange.com/questio
A couple of weeks ago I had a bit of spare time so I looked at the inability of
my iMac to put itself to sleep: something that has caused mild irritation from
time to time. Cutting a long story short it eventually involved someone from
Apple Care being involved. He said that I did not have the l
On 30 Mar 2017, at 16:38, Chris Jones wrote:
>
> Hi,
>
> On 30/03/17 16:32, Barrie Stott wrote:
>> I recently installed Sierra and am now coming to migrating my MacPorts ports
>> using https://trac.macports.org/wiki/Migration. Steps 1 and 2 seemed ok but
>> ste
I recently installed Sierra and am now coming to migrating my MacPorts ports
using https://trac.macports.org/wiki/Migration. Steps 1 and 2 seemed ok but
step 3 failed with the following information:
gbs:macports $ port -qv installed > myports.txt
Error: Current platform "darwin 16" does not mat
> On 21 Nov 2016, at 09:59, Rainer Müller wrote:
>
> On 2016-11-21 10:39, Barrie Stott wrote:
>> -
>> Password:
>> ---> Updating MacPorts base sources using rsync
>> MacPorts base version 2.3.4 installed,
>> MacPorts base version 2.3.5 do
I had an email saying that MacPorts 2.3.5 was available so I ran
'sudo port selfupdate’. The following, between ‘——‘ lines, appeared:
-
Password:
---> Updating MacPorts base sources using rsync
MacPorts base version 2.3.4 installed,
MacPorts base version 2.3.5 downloaded.
---> Updating the
15 matches
Mail list logo
