Some months ago I moved to Sierra from El Capitan and started upgrading my
ports. Nothing went as it should and I became ill at about the same time. I
abandoned everything until I was feeling better and that time has now arrived.
Following the instructions in MacPorts Guide I cleaned out all my
I have an iMac as my only computer and am near the beginning of installing
ports for Sierra so it’s a good time to change from +universal way of working
to -universal; it should save space and installations should be quicker. Does
anyone know any good reasons why I should not go ahead? Are there
I recently moved from El Capitan to Sierra and failed miserably when trying to
upgrade MacPorts. I am now trying to get MacPorts going again from scratch
rather than upgrading and had occasion to use port diagnose. Here’s what was
displayed on the screen:
sudo port diagnose
Password:
Error: cur
> On 24 Jun 2016, at 18:56, Bachsau wrote:
>
> Barrie Stott wrote on 24.06.2016 19:10:
>> I am not experiencing any issues and am unsure whether I need to uninstall
>> MacPorts. Can someone tell me if I need to uninstall Macports?
>
> You don't. Just dow
On 24 Jun 2016, at 18:18, Daniel J. Luke wrote:
>
> On Jun 24, 2016, at 1:10 PM, Barrie Stott wrote:
>> I am currently upgrading from Snow Leopard to El Capitan and have completed
>> to OS X install. I now want to migrate my MacPorts to the new OS and, to
>> this end
I am currently upgrading from Snow Leopard to El Capitan and have completed to
OS X install. I now want to migrate my MacPorts to the new OS and, to this end,
I have installed Xcode and am contemplating installing MacPorts. In the
MacPorts Guide section 2.4 I read the following paragraph:
Unins
On 17 Jul 2015, at 17:25, Mihai Moldovan wrote:
> On 17.07.2015 05:00 PM, Barrie Stott wrote:
>> In trying to upgrade, an error occurred with libnetpbm. I cleaned it and
>> tried again only to get the same error. I have no idea how to get past this
>> so I am asking for he
In trying to upgrade, an error occurred with libnetpbm. I cleaned it and tried
again only to get the same error. I have no idea how to get past this so I am
asking for help.
I enclose what I think is the relevant information: what was displayed in
getting to the error and the log file for libne
On 26 Jun 2015, at 03:36, Ryan Schmidt wrote:
>
> On Jun 12, 2015, at 10:21 AM, Barrie Stott wrote:
>
>> Whenever I perform such an 'upgrade outdated', a message is displayed when
>> trying to configure netpbm saying that I should force a deactivation of
>&
, Ryan Schmidt wrote:
> On Jun 13, 2015, at 02:56, Barrie Stott wrote:
>
>>> Yes, if "port outdated" shows that netpbm is outdated, running "sudo port
>>> -f deactivate netpbm" before running "sudo port upgrade outdated" is fine;
>>>
On 12 Jun 2015, at 22:08, Brandon Allbery wrote:
> On Fri, Jun 12, 2015 at 1:26 PM, Mihai Moldovan wrote:
> That would break other ports that depend upon netpbm. Worse, I think port will
> automatically re-activate it, if it comes to such a port.
>
> I would hope those are only upgraded *after*
On 12 Jun 2015, at 21:57, Ryan Schmidt wrote:
>
> On Jun 12, 2015, at 10:21 AM, Barrie Stott wrote:
>
>> Whenever I perform such an 'upgrade outdated', a message is displayed when
>> trying to configure netpbm saying that I should force a deactivation of
>&
On 12 Jun 2015, at 18:26, Mihai Moldovan wrote:
> On 12.06.2015 05:21 PM, Barrie Stott wrote:
>> Whenever I perform such an 'upgrade outdated', a message is displayed when
>> trying to configure netpbm saying that I should force a deactivation of
>> netpbm and t
Whenever I perform such an 'upgrade outdated', a message is displayed when
trying to configure netpbm saying that I should force a deactivation of netpbm
and then the upgrade stops. Normally I deactivate netpbm, upgrade netpbm and
upgrade outdated.
Is there any reason why I cannot force deactiv
On 28 Oct 2014, at 08:36, Chris Jones wrote:
>
>> in an attempt to minimize exposure to Shellshock. IIRC I got the above
>> from someone on this list.
>
> Together, if I recall, with a number of posts saying it was also a very bad
> idea
There was also a post from Greg Earle giving a scr
On 11 Oct 2014, at 13:35, Ryan Schmidt wrote:
> On Oct 11, 2014, at 7:29 AM, Barrie Stott wrote:
>
>> I have no objection at all to rebuilding Apple's /bin/bash and /bin/sh when
>> all I have to do is run the given script. However, Greg, do I need to do it?
>> I
On 10 Oct 2014, at 23:45, Greg Earle wrote:
> On Oct 10, 2014, at 16:06 PM, Barrie Stott wrote:
>
>> On 10 Oct 2014, at 15:27, Brandon Allbery wrote:
>>
>>> That said, 10.6 being unsupported by Apple, it is possible that your best
>>> bet is to copy /bin/b
On 10 Oct 2014, at 15:27, Brandon Allbery wrote:
> That said, 10.6 being unsupported by Apple, it is possible that your best bet
> is to copy /bin/bash to /bin/bash.apple and then copy MacPorts' bash to
> /bin/bash. (But beware, if you remove MacPorts in the future your /bin/bash
> will break;
On 10 Oct 2014, at 13:48, Brandon Allbery wrote:
> On Fri, Oct 10, 2014 at 6:13 AM, Barrie Stott wrote:
> Wouldn't the stopping of function export from MacPorts' bash be a big
> restriction on bash use. For example, I want to be able to type "mvim", with
>
On 10 Oct 2014, at 12:19, Mathias Laurin wrote:
>> Wouldn't the stopping of function export from MacPorts' bash be a big
>> restriction on bash use. For example, I want to be able to type "mvim", with
>> or without parameters, to open a MacVim window. At present, I get the error:
>> "/bin/sh: l
On 9 Oct 2014, at 23:27, Jeremy Lavergne wrote:
> Off the top of my head:
> * Rosetta (for PPC)
> * Apple Mail in Mavericks cannot do any searching without spotlight (among
> other bugs)
> * Mavericks Messages keeps records of every chat you’ve had, the option to
> explicitly “close” can cause
On 9 Oct 2014, at 21:51, Brandon Allbery wrote:
> On Thu, Oct 9, 2014 at 4:46 PM, Barrie Stott wrote:
> On 9 Oct 2014, at 21:10, Brandon Allbery wrote:
> > On Thu, Oct 9, 2014 at 4:06 PM, Barrie Stott wrote:
> > function ttr()
> >
> > You should use wither "
On 9 Oct 2014, at 22:07, Lawrence Velázquez wrote:
> On Oct 9, 2014, at 4:46 PM, Barrie Stott wrote:
>
>> Also all the old versions of the functions have been present for well over 6
>> months so I reckon something else is involved.
>
> I expect you installed OS
On 9 Oct 2014, at 21:10, Brandon Allbery wrote:
> On Thu, Oct 9, 2014 at 4:06 PM, Barrie Stott wrote:
> function ttr()
>
> You should use wither "ttr()" or "function ttr", not both. It's replacing ()
> with %% and then tripping over it later (possibl
On 9 Oct 2014, at 19:08, Lawrence Velázquez wrote:
> On Oct 9, 2014, at 12:25 PM, Barrie Stott wrote:
>
>> On trying to get MacVim going I typed something like 'mvim file1 file' in a
>> terminal and the error message in the Subject line appeared.
>
> Do
On 9 Oct 2014, at 19:30, Brandon Allbery wrote:
> On Thu, Oct 9, 2014 at 12:25 PM, Barrie Stott wrote:
> This is the sequence of events that led to me getting the error in the
> Subject line.
>
> Check your .bash_profile / .bashrc; you appear to be defining a function
> nam
Many thanks,
Barrie
> On Thu, Oct 9, 2014 at 9:25 AM, Barrie Stott wrote:
>> This is the sequence of events that led to me getting the error in the
>> Subject line.
>>
>> I had used MacVim on the previous day with no problem and had used mail and
>> Skype today
This is the sequence of events that led to me getting the error in the Subject
line.
I had used MacVim on the previous day with no problem and had used mail and
Skype today and the iMac was left switched on with several tabs open in the
browser and files open in MacVim.
Unrelated to the comput
During an 'upgrade outdated' the dialog port failed. I had forgotten about
dialog, no longer use it and have now uninstalled it.
However, someone may want to know about how it failed so I enclose the log
mentioned with in the error message.
Barrie.
main.log
Description: Binary data
_
On 7 Sep 2013, at 09:58, Rainer Müller wrote:
> On 2013-09-07 10:16, Barrie Stott wrote:
>> I did an upgrade recently and a binary was installed. In the console log
>> were a couple of lines:
>>
>> ---> Attempting to fetch bash-completion-2.1_5.darwi
I did an upgrade recently and a binary was installed. In the console log were a
couple of lines:
---> Attempting to fetch bash-completion-2.1_5.darwin_10.noarch.tbz2 from
http://mse.uk.packages.macports.org/sites/packages.macports.org/bash-completion
---> Attempting to fetch bash-completion-2
On 12 Aug 2012, at 17:30, Brandon Allbery wrote:
> On Sun, Aug 12, 2012 at 12:16 PM, Peng Yu wrote:
> I don't see man page of ack. Is it available from macports? Or my
>
> It's not available as a manpage; "perldoc ack-5.12" works to get
> documentation, to the extent that ack *has* documentati
On 21 Jul 2012, at 11:07, Ryan Schmidt wrote:
>
> On Jul 21, 2012, at 04:53, Barrie Stott wrote:
>
>>
>> On 20 Jul 2012, at 16:08, Clemens Lang wrote:
>>
>>> On Fri, Jul 20, 2012 at 09:56:24AM -0500, Ryan Schmidt wrote:
>>>> I am still
On 21 Jul 2012, at 13:19, Damon McDougall wrote:
> On Sat, Jul 21, 2012 at 12:51:04PM +0100, Barrie Stott wrote:
>>
>> On 21 Jul 2012, at 12:01, Clemens Lang wrote:
>>
>>>> I have now edited /etc/shells with MacVim to add /opt/local/bin/bash
>>>>
On 21 Jul 2012, at 12:01, Clemens Lang wrote:
>> I have now edited /etc/shells with MacVim to add /opt/local/bin/bash
>> as the first in the list. I then ran 'chsh -s /opt/local/bin/bash'.
>
> I have done this on my system, too, and it works fine for me.
>
>
>> I had already done what you sugg
On 21 Jul 2012, at 11:07, Ryan Schmidt wrote:
>
> On Jul 21, 2012, at 04:53, Barrie Stott wrote:
>
>>
>> On 20 Jul 2012, at 16:08, Clemens Lang wrote:
>>
>>> On Fri, Jul 20, 2012 at 09:56:24AM -0500, Ryan Schmidt wrote:
>>>> I am still
On 20 Jul 2012, at 16:08, Clemens Lang wrote:
> On Fri, Jul 20, 2012 at 09:56:24AM -0500, Ryan Schmidt wrote:
>> I am still not sure what to change or how to verify it was successful.
>> In Lion's Terminal.app, I have opened Preferences -> Settings ->
>> Shell, checked the "Run command" box, and
On 8 Apr 2012, at 06:51, Ryan Schmidt wrote:
>
> On Apr 7, 2012, at 05:48, Barrie Stott wrote:
>
>> 'port outgraded' showed that p5-app-ack and p5.14-app-ack (but no other
>> *-app-ack) needed to be upgraded and p5.14-app-ack did so without a hitch.
>>
'port outgraded' showed that p5-app-ack and p5.14-app-ack (but no other
*-app-ack) needed to be upgraded and p5.14-app-ack did so without a hitch.
The ports I have of the form p5* are:
p5-app-ack @1.940.0_2 (active)
p5.12-file-next @1.20.0_2
p5.12-locale-gettext @1.50.0_6+universal (active
On 19 Mar 2012, at 15:02, Ryan Schmidt wrote:
>
> On Mar 19, 2012, at 09:27, Ryan Schmidt wrote:
>
>> * Destroot: interrupting ok; resuming might not work; if not, remove "$(port
>> workpath foo)/destroot" or clean and try again
>
> Make that "$(port work foo)/destroot".
>
>
Will do and th
On 19 Mar 2012, at 14:27, Ryan Schmidt wrote:
> On Mar 19, 2012, at 09:02, Barrie Stott wrote:
>
>> On 19 Mar 2012, at 01:10, Ryan Schmidt wrote:
>>
>>> Personally I just run "port outdated" and then individually upgrade the
>>> specific
On 19 Mar 2012, at 01:10, Ryan Schmidt wrote:
> Personally I just run "port outdated" and then individually upgrade the
> specific ports I want to upgrade. If it starts building something I didn't
> want it to build, I cancel it. (For example, I'm not ready to upgrade to
> Subversion 1.7 yet,
On 8 Nov 2011, at 15:02, Ryan Schmidt wrote:
>
> On Nov 7, 2011, at 14:12, Jeremy Lavergne wrote:
>
>>> Error: Unable to upgrade port: couldn't open
>>> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_databases_sqlite3/sqlite3/work/.macports.sqlit
I ran the following:
sudo port selfupdate
port echo outdated
port upgrade outdated
This gave the message
---> Computing dependencies for sqlite3
---> Fetching archive for sqlite3
Error: Target org.macports.archivefetch returned:
/opt/local/var/macports/software/sqlite3 must be writable
Log for
On 6 Apr 2011, at 18:42, Jason Swails wrote:
> These were there before. MacPorts carries along with it a complete list of
> sources that are supported and maintained. Rest assured that the only things
> that reside here are patches required to make the build process go smoothly
> for Macs an
I installed a port because it read as though it was just what I wanted. When I
started to use it I found it wasn't so I uninstalled it using 'sudo port
uninstall --follow-dependencies openbrowser'. Will this get rid of ALL the
files that were brought across in the install?
The reason I ask is t
On 5 Mar 2011, at 11:43, Joshua Root wrote:
> On 2011-3-5 20:58 , Barrie Stott wrote:
>>
>> On 5 Mar 2011, at 05:21, Joshua Root wrote:
>>
>>> On 28164-7-23 05:59 , Barrie Stott wrote:
>>>> I have dokuwiki installed and want to uninstall it together
On 5 Mar 2011, at 05:21, Joshua Root wrote:
> On 28164-7-23 05:59 , Barrie Stott wrote:
>> I have dokuwiki installed and want to uninstall it together with all the
>> other ports on which it depends that are not being used elsewhere.
>>
>> Will the single command &#
On 4 Mar 2011, at 15:50, Harald Hanche-Olsen wrote:
> [Ryan Schmidt (2011-03-04 15:06:21 UTC)]
>
>> sudo port uninstall dokuwiki
>> port installed leaves
>> sudo port uninstall leaves
Many thanks for this and clarifying the difference between dependency and
dependent.
> See also the newish r
I have dokuwiki installed and want to uninstall it together with all the other
ports on which it depends that are not being used elsewhere.
Will the single command 'sudo port uninstall --follow-dependents dokuwiki' do
it? I looked in the port manpage and it seemed to be a bit ambiguous when it
On 31 Dec 2010, at 18:08, Arno Hautala wrote:
> On Fri, Dec 31, 2010 at 07:54, Barrie Stott wrote:
>>
>> As I see it I need to do two things: deactivate the working version of a
>> port and activate a different version.
>> I've scoured the Users Guide regardin
I ran 'sudo port upgrade outdated' and macvim was upgraded as part of this. I
suspect that this new version is not working as it should but, being timid, I
accept that it may be as a result of something else. With that in mind, I would
like to try my previous version to see if the problems I am
On 3 Dec 2010, at 14:27, Andrea D'Amore wrote:
> On Fri, Dec 3, 2010 at 11:06 AM, Barrie Stott wrote:
>> I've moved from using linux to using imac with so-called Mighty Mouse. I'm
>> used to programs that use more than a single mouse button, like gv for
>&g
In my previous post I mentioned MIGHTY mouse. It should have been MAGIC mouse.
I apologize for that.
Barrie.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
I've moved from using linux to using imac with so-called Mighty Mouse. I'm used
to programs that use more than a single mouse button, like gv for example, and
several of these are available as ports.
Is there a generally accepted way to access several mouse buttons?
If not, does anyone know how
55 matches
Mail list logo
