> On Nov 6, 2024, at 1:44 AM, Ryan Carsten Schmidt
> wrote:
>
> Bug reports should be filed in the issue tracker. Please attach the entire
> compressed log file to your ticket.
I think I filed ticked #71266 for this but I’m too stupid to figure out the UX
to see if it actually happened.
H
> On Nov 5, 2024, at 8:26 PM, Ryan Carsten Schmidt
> wrote:
>
> The new instructions don't require you to update MacPorts base first so it's
> not mentioned there.
But I couldn’t run _any_ port command without generating getting the platform
mismatch error—see my original post. I could no
Oops. My mistake. I should have read the instructions more carefully. I might
suggest a link to the installer page on the “Step 0” of the migration page,
https://trac.macports.org/wiki/Migration.
Jerry
> On Nov 4, 2024, at 12:40 PM, Ryan Carsten Schmidt
> wrote:
>
> On Nov 4, 2024, at 00:50,
I have an M1 on which I recently upgraed the os from 12 Monterey to 14 Sonoma.
I don’t have Xcode installed but I do have the latest (Sonoma) version of
Command Line Tools; I think it’s 16.1.
I need to upgrade macports.
I have followed the instructions at https://trac.macports.org/wiki/Migratio
/opt/local/bin/python3 is a symlink that points to itself (Path Finder) or to
nowhere (Finder). Is that correct?
Jerry
M 480 612 4252
L 480 839 3708
Sorry 2
Sorry 1
> On Feb 6, 2022, at 8:16 AM, Mojca Miklavec wrote:
>
> On Sun, 6 Feb 2022 at 09:17, list_email--- via macports-users wrote:
>>
>> Sorry if this has been reported before.
>>
>> The Available Ports page at https://ports.macports.org/ reports Error 503
>
Sorry if this has been reported before.
The Available Ports page at https://ports.macports.org/ reports Error 503
Backend fetch failed.
Jerry
I want to embed the plotter Veusz in a Python script. According to the Veusz
instructions, the path to Veusz should be on the Python path and one is advised
to do this in setup.py. (Python 3.8 here). There are 123 files on my computer
called setup.py and 29 of them are in /opt/local. Which one s
> On Dec 6, 2020, at 9:35 AM, Ken Cunningham
> wrote:
>
> of course the simplest method of reverting to an older binary is to just
> reactivate it if you still have it installed, but inactive, after an update.
>
> This will show you what versions are installed:
>
> port -v installed portna
I am having trouble linking ploplot resulting in this:
dyld: Library not loaded: /opt/local/lib/libshp.1.3.0.dylib
Referenced from: /usr/local/plplot/lib//libplplot.13.dylib
Reason: image not found
I believe this is the shapelib library and that it is used by plplot but I now
have a newer ve
force the activation.
Each time I did "port -f activate foo” I repeated the "port upgrade outdated"
command plus a few other things at other times.
Should I file a ticket for this?
Jerry
> On Sep 26, 2020, at 10:49 PM, list_email--- via macports-users
> wrote:
>
&
plplot comes with Ada bindings. Does MacPorts compile these Ada bindings? And...
...Does MacPorts support GNAT, the gcc Ada compiler? I see it listed as
gcc-gnat, so that seems to imply “yes”. The reason I ask is that I remember
some years ago someone saying that GNAT is a problem because of Ma
> On Sep 26, 2020, at 7:06 AM, Ruben Di Battista
> wrote:
>
> Mh, I think that `pstoedit` port should depend on
> `texlive-latex-recommended`. So try to install it (or upgrade it) before, and
> then try again.
>
I tried that. Here is an abbreviated copy-paste from Terminal with the current
>> Please deactivate this port first, or use 'port -f activate libgcc10' to
>> force the activation.
>> ```
>> So deactivate the libgcc port and run the upgrade again?
>> On Wed, 23 Sep 2020, 12:43 list_email--- via macports-users,
>> wrote:
>>
I had not changed anything in my Macports installation for a long time. Then I
got to messing around with AquaTerm and something in the linking stage kept
crashing, so naturally I decided to freshen up my MacPorts set-up. Here’s what
happened. I have no idea what to do.
macOS 10.11.6
Thanks fo
I have the following item on my computer which is running macOS 10.11.6. I have
Mac Ports installed.
/Library/StartupItems/daemonic-dbus
I think this is cruft but I’m wondering if it is part of Mac Ports or if not,
where it came from. X11? I really want to throw it away.
Jerry
There are complaints on the Octave list that Octave on MacPorts is out of date
and that support has moved to homebrew. I don’t use Octave much but would also
appreciate it being kept up-to-date on MacPorts.
Jerry
I just ran port selfupdate after several months and experienced the following
oddities.
* readline was reported as disabled:
$ sudo port selfupdate
Password:
---> Updating MacPorts base sources using rsync
MacPorts base version 2.4.0 installed,
MacPorts base version 2.4.1 downloaded.
---> Upd
> On Feb 2, 2017, at 12:56 AM, Ryan Schmidt wrote:
>
> On Feb 1, 2017, at 23:42, list_em...@icloud.com wrote:
>>
>> Trying to do selfupdate and had the following problem. Using Version 2.3.4,
>> hoping to upgrade.
>>
>> Is this a permissions problem on /opt? If so, what should the permissions
Trying to do selfupdate and had the following problem. Using Version 2.3.4,
hoping to upgrade.
Is this a permissions problem on /opt? If so, what should the permissions be? I
prefer changing permissions with Finder or Path Finder.
Many thanks as always,
Jerry
MBPro:~ me$ port -v selfupdate
--
22 matches
Mail list logo
