> 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
24, at 00:50, Saagar Jha wrote:
>>
>> This usually means you need to update your MacPorts install. Try downloading
>> a new installer for your OS and seeing if that helps.
>
> Correct. It is step 2 of the old migration procedure.
With the latest Sonoma 14.7.1 on an Intel Mac, the most recent Xcode tools and
Macports 2.10.4 self updated, I ran port upgrade outdated, and after a few port
upgrades, I got this message:
sudo port upgrade outdated
---> Computing dependencies for graphviz
---> Fetching archive for gr
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
I just completed my standard configuration of a Mac Mini, upgraded to Sequoia
as a test machine. I asked to install 27 ports, that including dependencies
ended up in 957 ports being installed, and ffmpeg graphviz are among them:
ffmpeg @4.4.4_10+gpl2 (active)
graphviz @9.0.0_1+pangocairo+x11 (ac
On 29 Oct 2024, at 9:34 am, Fabien Auréjac wrote:
But this suggest me another question, do macports
binaries upload from my computer the results of the compilation
that happened, to help the community in later installations ?No, that does not happen and is
On 29/10/2024 1:11 am, Fabien Auréjac wrote:
Hello, after upgrading to Sequoia, all worked flawlessly without need of
anything, but when I tried to update macports via port selfupdate, it
asked for a migration.
All seems to be working well, but I'm quite surprised about the time it
This means, openvpn3 is ruled out for the moment and for the coming time under
macOS?
What alternatives are there to run a free openvpn client?
--
Christoph
> Am 27.10.2024 um 14:05 schrieb Ryan Carsten Schmidt :
>
>>> Am 27.10.2024 um 11:05 schrieb Christoph Kukulies:
>>>
>>> ---> Activat
stry::write {
foreach file $imagefiles {
incr progress_step
_progress update $progress_step $progress_..."
Error: See
/opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_imath-3.1.11_0_62ba10da924e712f0eae8f146f0fb34217340e8deb5f1d
ecuting
"throw registry::image-error $msg"
("foreach" body line 35)
invoked from within
"foreach file $imagefiles {
incr progress_step
_progress update $progress_step $progress_total_steps
se..."
invoked from w
ncies]
>
> Yes, ffmpeg has a lot of dependencies and even more when building from
> source. Reclaim may have removed some of the latter because they're not
> needed once you have built and installed the ports that use them.
>
>> I just don’t understand this. I am now w
mpting to fetch libvpx-1.13.1_0.darwin_24.arm64.tbz2 from
https://pek.cn.packages.macports.org/macports/packages/libvpx
---> Attempting to fetch libvpx-1.13.1_0.darwin_24.arm64.tbz2 from
https://kmq.jp.packages.macports.org/libvpx
---> Building libvpx
Error: Failed to build libvpx: command
led
Error: See
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_multimedia_aom/aom/main.log
for details.
I believe there is already a ticket open on aom.
And, in ticket #70750 there is this:
Anyway, I was able to get MacPorts fully work
ested ports.
I’ll post again if there are any unwelcome events associated with the currently
running restore.
In summary, this is my third attempt to migrate MacPorts on machines upgraded
to Sequoia. None of the three has gone well.
That’s all folks.
Mike Newman
Korat, Thailand
smim
If this is the case with libressl, and openssl is just a shim on openssl3, can
the dependency in python312 port be changed to openssl3 explicitly? I do have
both libressl and openssl3 installed and active.
This of course could be considered, but not its likely not an entirely
trivial chang
* Paolo Denti via macports-users:
> Dear Ralph, indeed that is the temperature according to iStat Menus.
I sincerely doubt that the CPU temperature hovers anywhere near the 100
Kelvin (!) mark, like you wrote. That was funny to me, especially coming
from a physicist.
-Ralph
Thanks. nbsmtp is now installed.
> On Oct 2, 2024, at 14:04, Ryan Carsten Schmidt
> wrote:
>
> On Oct 2, 2024, at 00:13, Ryan Carsten Schmidt wrote:
>>
>>> On Oct 2, 2024, at 00:06, Michael Newman wrote:
>>>
>>> I did my best with the bug report.
>>
>>
>> Thanks! The ticket URL is https://
be nulls. The bug is
> that the filesystem tells tar there are holes when in fact those holes had
> already been filled with data and should not be excluded, but there's no way
> for tar to know that the filesystem is lying.
>
> We have a workaround we can employ for roo
Sellotape:bin mnewman$ file /opt/local/lib/libavcodec.58.dylib
/opt/local/lib/libavcodec.58.134.100.dylib
/opt/local/lib/libavcodec.58.dylib: data
/opt/local/lib/libavcodec.58.134.100.dylib: data
Unfortunately, I don’t recall if ffmpeg was built from source or via binary.
Sorry.
This o
b: Not a Mach-O file
(referenced from /opt/local/bin/ffmpeg)
---> No broken files found.
---> No broken ports found.
Should I remove the port and install again, or what?
> On Oct 3, 2024, at 09:44, Ken Cunningham
> wrote:
>
> Not a systemic issue with the software or
Sorry to bother everyone again,
I have a shell script that has been working fine for several years which uses
ffmpeg to add audio to a video.
It stopped working after migrating to the latest MacPorts.
I can’t tell you the version of ffmpeg because:
Sellotape:bin mnewman$ ffmpeg -version
dyld
Dear Maxim, Dear Dave, Dear Ralph thank you very much.
Dear Maxim, I shall verify my failing exe according to your suggestions.
About the lack of binaries of gcc14 according to my (poor) experience you are
right, it necessary to expect some time, but I was in hurry to verify if gcc14
works.
Dea
ack portprogress::target_progress_callback
>> build"
>> :debug:build (procedure "portbuild::build_main" line 10)
>> :debug:build invoked from within
>> :debug:build "$procedure $targetname"
>> :error:build See
>> /opt/local/var/macports/l
hin
:debug:build "$procedure $targetname"
:error:build See
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_mail_nbsmtp/nbsmtp/main.log
for details.
When I search for a ticket for nbsmtp I find nothing. (But I’m not very g
* P. Denti via macports-users:
> Otherwise inconvenient is the building procedure of gcc and its library:
> for around an hour the cpu cores temperature is 100-108 Kelvin, on
> account that no fan is present in iMac ...
Are you quite sure about that temperature? That would be one h
ran arrays, IIRC. I use
modern gfortran's on Mac all the time, and they continue to work fine for
complex projects.
On Tue, Oct 1, 2024 at 10:36 AM P. Denti via macports-users <
macports-users@lists.macports.org> wrote:
Subject: Reply to Maxim Abalenkov + a pair of sad reflections
Hel
Failure starting with OS Sonoma, now with Sequoia.
Processor is M3 on iMac.
The following message in Sonoma:
paolo in ~/Desktop/nisclue240 $ ./nisclue
dyld[78445]: dyld cache '(null)' not loaded: syscall to map cache into shared
region failed
dyld[78445]: Library not loaded: /usr/lib/libSystem.B
Hello Maxim,
thank you very much for indicating the article on Apple Developer.
I am final user of Fortran as a physicist who developed some research software
just in Fortran.
The hardware based on Intel CPU i7 is about nine-years-old, so that I bought a
new iMac M3.
The new software Sonoma, now
https://trac.macports.org/ticket/70935
On 30/09/2024 6:00 am, Kenneth Wolcott wrote:
Any update? This is still happening...
On Wed, Sep 25, 2024 at 1:45 AM Chris Jones wrote:
I uninstalled the expect port and then installed the expect port
again and the broken link still happens...
There already is a bug report (#70869). msmtp fails because building gas fails.
> On Sep 30, 2024, at 09:20, Ryan Carsten Schmidt
> wrote:
>
> On Sep 29, 2024, at 19:25, Michael Newman wrote:
>>
>> I’ve been migrating MacPorts both to new machines and as a result of
I’ve been migrating MacPorts both to new machines and as a result of OS
upgrades for many years now. It has always worked OK.
The migration after the Sequoia upgrade on an MBA didn’t go so well; part of
which was my fault. In the end I was able to migrate all ports except for msmtp.
That
bz2 from
> https://packages.macports.org/libmagic
> ---> Attempting to fetch libmagic-5.45_0.darwin_24.arm64.tbz2 from
> https://mirrors.mit.edu/macports/packages/libmagic
> ---> Attempting to fetch libmagic-5.45_0.darwin_24.arm64.tbz2 from
> http://bos.us.packages.macport
pendencies:
>
> ---> Fetching archive for libmagic
> ---> Attempting to fetch libmagic-5.45_0.darwin_24.arm64.tbz2 from
> https://packages.macports.org/libmagic
> ---> Attempting to fetch libmagic-5.45_0.darwin_24.arm64.tbz2 from
> https://mirrors.mit.edu/macports/packages/libmagic
I uninstalled the expect port and then installed the expect port
again and the broken link still happens...
that was entirely my point. to see the issue you needed to ensure you
*didn't* have the old one installed
On 25/09/2024 9:16 am, Saagar Jha wrote:
Reproduced it on a fresh install of MacPorts (I apparently had
libexpect.a hanging around in /opt/local for some reason).
That is completely normal when you build an update. The previous version
is only removed when the update is successfully built
It may have built fine for you if you had an older one already installed
at the same time. Try removing the current version and then rebuild.
On 25/09/2024 4:15 am, Saagar Jha wrote:
I bumped this earlier today to use dynamic libraries instead of static
ones, so I assume that’s related. That
24 Sep 2024, at 5:24 pm, Kenneth Wolcott wrote:
>
> FYI: R depends on g95 which fails to install being too old
>
> I've downloaded R directly, not using MacPorts...
>
> I'm surprised that there haven't been a flurry of email messages
> regarding this g9
snapshot created for migration
I’m usually in bed by 8:30 and asleep by 9:00. There’s little chance that I
would ever be awake after midnight and even less chance that I would be doing a
MacOS upgrade and MacPorts migration at that hour.
However, it appears that’s exactly what I did. I have no
to the ports that I either
migrated or installed?
Many of them simply disappeared after I upgraded to Sequoia and used the new
MacPorts migration procedure.
Fifteen:desktop mnewman$ xargs -n1 sudo port setrequested < old_requested.txt
Password:
Error: exiftool is not installed
Error: jshon
he best I can do; even though
I’m sure I’ve installed several ports since the resurrected requested.txt file
was created.
Please excuse my ignorance in these matters. I’ve been a MacPorts user for a
long time, but don’t know much about it. I’ve done many migrations both after
OS updates and
I did a "port selfupdate" and got this:
$ sudo port install syncscroll
Password:
Warning: port definitions are more than two weeks old, consider updating them
by running 'port selfupdate'.
Error: Port syncscroll not found
$ port selfupdate
Error: Insufficient privileges
Previously I reported.
> On Sep 22, 2024, at 19:00, macports-users-requ...@lists.macports.org wrote:
>
> Attempting to migrate following Sequoia installation I got the following:
>
>Migration finished with errors.
>The following ports could not be restored:
&
> On 22 Sep 2024, at 7:30 pm, Kenneth Wolcott wrote:
>
> Hi;
>
> man port
>
> or
>
> port help
>
> does not clue me in; I need more info regarding port setrequested;
> how to list what ports are already requested?
> port echo requested
>
> Thanks,
> Ken Wolcott
> On 22 Sep 2024, at 10:49 am, Michael Newman wrote:
>
> I’m sorry, but this is way beyond my ability. I have many questions.
>
> The guide to filing a ticket says "Clean and try again”
>
> • Does “clean” mean I should run "sudo port -f clean --all all”
> • Does “try again” mean I should run
I’m sorry, but this is way beyond my ability. I have many questions.
The guide to filing a ticket says "Clean and try again”
• Does “clean” mean I should run "sudo port -f clean --all all”
• Does “try again” mean I should run "sudo port migrate” again, or try to
install each failed port separate
>
> That log file is extremely long; too long to include with this message. But,
> there is this:
you should never send attachments to this list anyway. See below.
>
> :info:build Exit code: 2
> :error:build Failed to build aom: command execution failed
> :debug:build Error code: CHILDSTATUS 2
dependency aom failed
- msmtp
Skipped because its dependency gss failed
- nbsmtp
Failed: Unable to execute target 'activate' for port nbsmtp -
see its log for details
Error: Failed to build aom: command execution failed
Error: See
/opt/local/var/mac
y312-scipy - see
its log for details
I do not know what the problem was with aqua term, since it was successfully
built the previous run of 'port restore —last’. In any case, here are the
errors reported by the main.log of julia, aquaterm and py32-scipy:
julia ====
fortran compiler should configure itself to
use one of the macports gfortran compilers, from one of the GCC ports. If a
build is failing to do this, that is an error in the port configuration.
As always, emails to this list are not the correct way to report port bugs.
Please file as trac ticket
e `rust` port has been updated recently.
>>
>> -a
>>
>> On Wed, Sep 18, 2024 at 6:22 PM Kenneth Wolcott
>> wrote:
>>>
>>> Hi;
>>>
>>> Just did a selfupdate, there's an issue with the rust port...
>>>
>&g
> On 20 Sep 2024, at 01:07, Joshua Root wrote:
>
>>
>> Unfortunately, after executing supo port restore —last I got exactly the
>> same error as before (libgcc14 and lib sodium failed, and cause several
>> ports, like emacs-app, not to compile). I do not know what else to do. Could
>> execut
> On 19 Sep 2024, at 20:46, Joshua Root wrote:
>
> On 19/9/2024 18:30, Artemio González López wrote:
>> Thanks, Josh! In fact, I renamed the /Library/Developer/CommandLineTools and
>> got most of my ports to succesfully build after executing “sudo port restore
>> —last”. Unfortunately, there
> On Sep 18, 2024, at 5:29 PM, Joshua Root wrote:
>
> Artemio González López wrote:
>
>> Yesterday I tried to migrate my Sonoma MacPorts installation to the newly
>> installed Sequoia on a 2019 M1 MacBook Pro 13”. I used the new procedure,
>> i.e.,
>&
Hi everybody,
Yesterday I tried to migrate my Sonoma MacPorts installation to the newly
installed Sequoia on a 2019 M1 MacBook Pro 13”. I used the new procedure, i.e.,
sudo port migrate
The procedure produced the following errors:
Migration finished with errors.
The following ports
gt;
> > It may be a good idea to wait a while to upgrade. If you have to use
> > MacPorts on Sequoia right now, it may work best to install only Xcode 16
> > without the Command Line Tools.
> >
> > - Josh
> >
--
Fausto Maijstral
###
You are asking in the wrong place, the users list is not really the
place for this.
First file a Trac ticket and then ask for feedback on that ticket on the
macports devel list.
Chris
On 15/09/2024 10:07 pm, Dave Horsfall wrote:
Anyone?
-- Dave
-- Forwarded message
Hi,
Bill Cole wrote:
But this was easy to find:https://docs.python.org/3.11/library/imp.html and it
seems to indicate that you should backrev your Python to 3.11 at most.
seamonkey dev guys told me indeed 3.12 is not compatible, I selected
python 3.11 and compilation begins... fails now in
Hi Joshua,
Joshua Root wrote:
>
> First install the macports.sqlext port. Then run this command (all one
> line):
>
> sqlite3 /opt/local/var/macports/registry/registry.db ".load
> /opt/local/lib/sqlite3/macports.sqlext" "PRAGMA integrity_check"
>
Hi,
I would like to try to build SeaMonkey on 10.9 Mavericks. A decent browser and
a good email client. Officially not supported on 10.9, but it works on 10.11,
so I have some hope it can be convinced to run. Maybe some of you want to help?
Biggest issue is getting it to run. Latest version req
> depends is what needs the specified port to build or run.
>
> I'm not getting anything back for dependentof. But depof (or rdepof) is what
> the specified port needs to build or run.
>
> examples:
>
> port echo depends:vim
>
> (what directly depends on vim to build or run)
>
> The rdepend
> 1. Re: Doubly Active PHP (bernard.rema...@icloud.com)
> 2. Re: Doubly Active PHP (Bill Cole)
> 3. Re: Doubly Active PHP (Joshua Root)
> 4. Re: Doubly Active PHP (Chris Jones)
> 5. Dependencies/Dependents (bernard.rema...@icloud.com)
> 6. Re: Dependencies/Dependents (Richard L. Hamil
About dependents/dependencies:
What is the meaning of ‘rdepends’? (The manual page on port(1) is a little
difficult to understand): I understand ‘r’ is the prefix for recursive.
What is the difference between ‘rdepends’ and ‘rdependentof’?
— bernard
Is the above list to be expected?
Why do I have 2 php8* ports?
Should I do anything at all?
There are really only two reasons a port is installed:
1. Someone ran 'port install' to install that specific port, or
2. Some other port depends on it.
You can check whether any other installed po
Good day Jim,
> Only two PHP8* ports? That's nothing! I have 8 Python* ports installed!
>
> Seriously, it is common in macports to have distinct ports or subports
> for different versions of software where users might want to keep
> multiple versions on hand for easy use.
&
When I type ‘port installed’, I notice I have 2 php8* ports (php82 @8.2.23_0
and php83 @8.3.11_0) and both are active.
Here is the list of php ports I have:
php82 @8.2.23_0+libedit (active)
php82-gd @8.2.23_0 (active)
php82-mbstring @8.2.23_0 (active)
php82-mcrypt @1.0.7_0 (active)
php82
7; db rows
are affected. Try running this: sqlite3
/opt/local/var/macports/registry/registry.db "select * from ports
where id=726"
sqlite3 /opt/local/var/macports/registry/registry.db "select * from
ports where id=726"
726|xmlcatmgr|435d94eb7431bfb474662c034bffac8cbde64759424e
On 04/09/2024 10:50 pm, Dave Horsfall wrote:
13" mid-2010 MacBook Pro, running High Sierra 10.13.6.
Did a graphics library change recently, and broke something? Both XV and
GV are now hanging on startup, with no output; I don't know where to start
with this.
Hmmm... GIMP is also hanging?
Sounds like you have an issue with your X11 server, as these
applications are perhaps hanging at the point they are waiting for it to
start up.
1. Does it automatically start if you run a very basic X11 application,
like xeyes ?
> sudo port install xeyes
> xeyes
If that does not trigge
Hi!
on my MacBook (64bit) after upgrading to macports 2.10.1, "port
selfupdate" yields:
---> Checking for newer releases of MacPorts
MacPorts base version 2.10.1 installed,
MacPorts base version 2.10.1 available.
---> MacPorts base is already the latest version
--->
Hi,
I have several python versions installed an dused as dependencies my
macports itself. Fine.
To build ArcticFox browser, I need python2 and on 10.9 this is no issue,
I guess the system python is getting used.
Now I want to try do build current SeaMonkey since no binary is provided
anymore
foo/py-foo ports, and be
> happy with whatever is currently present. That aspect already works
> with perl5 (but I haven't tested it by making a newer perl version use
> packages/pods installed for a previous version).
>
> R.
I assume that you're referring to perl modules
And I suppose one follow up, if that is the case: how are upgrades
handled by MacPorts when someone has originally installed a package from
source vs binary?
Take this scenario:
– Install package X from source;
– Install package Y from binary;
– Later, both packages are upgraded in the ports
Hello, all. I have struggled to find relevant documentation for this,
and I hope I haven't just missed something obvious. I have installed
some packages using the binaries available online, but I have also
installed a number using the `-s` flag to ensure that they are installed
from source.
I
Hi, one minor thing I've been noticing with the new MacPorts 2.10
release: it seems that there's been a change to sort ordering with
this release? i.e., when I do a command like `port outdated`, it'll do
the python ports like so:
py310-*
py311-*
py312-*
py37-*
py38-*
py39-*
...whe
?
Ciao
Franco
> On 15 Aug 2024, at 10:05, Raoul MEGELAS wrote:
>
> Hello,
>
> A little bit more.
> I Created a new administrator user account.
> Macports works fine on it.
> This means than I have an error in my own account., and only that.
> Please how to narrow t
Franco
> On 14 Aug 2024, at 09:30, Raoul MEGELAS wrote:
>
> Hello Franco,
>
> Here is exactly what I did:
> sudo port -fp uninstall installed
> # remove user and group
> # sudo dscl . -delete /Users/macports
> # sudo dscl . -delete /Groups/macports
>
Hi Raoul,
just to be sure, did you remove MacPorts following the steps described in
<https://guide.macports.org/#installing.macports.uninstalling>
Ciao
Franco
> On 14 Aug 2024, at 08:13, Raoul MEGELAS wrote:
>
> Hello macports,
>
> Still the same error:
> As the s
me or Apple. It is not a MacPorts bug.
Feel free to post this reply of mine to the MacPorts list to let them know.
I semi-recently got a MBP, so I will test and fix, if necessary. However, macOS
likes to pull old versions, so even if I fix it, I don't know when the fix will
land in macOS p
Hi Bill and Richard,
> On 13 Aug 2024, at 14:00, macports-users-requ...@lists.macports.org wrote:
>
>
> Date: Mon, 12 Aug 2024 14:14:54 +0200
> From: Bas Jansen
> To: macports-users@lists.macports.org
> Subject: Strange warning/file when doing a selfupdate
> Message
found.
---> No broken ports found.
Emphasis mine, of course. There is no file “g[“ in /opt/local/bin/. I ran this
using macports 2.10.0, macOS Sonoma 14.6.1 on an Intel MacBook Pro, late 2019.
Anyone know what this means?
Kind regards,
Bas
There is a recent source snapshot cached by Macports here:
https://distfiles.macports.org/just-fast/
If you value this code, perhaps stash a copy for yourself. I believe that
Macports will continue to use the cached copy for future install requests,
until something tells it to change.
Maybe
On Sat, Jul 13, 2024 at 1:58 AM Richard L. Hamilton wrote:
>
>
>
> > On Jul 13, 2024, at 01:46, Daniel J. Luke wrote:
> >
> > On Jul 12, 2024, at 4:54 PM, David Gilman wrote:
> >> Is there any opposition to dropping all unsupported PostgreSQL
> >&
Hi,
on a 10.11 system for which binary packages are provided, an upgrade of
gtk3 +quartz fails.
The old libepoxy was "neutral" now it pulls in a +x11 version
automatically in binary form.
I uninstalled / deactivated libepoxy, but again I find myself libepoxy +x11
If I remove it and manually
Hi,Apple canceled the 64 bit version of it's Carbon API when it was almost
complete.Sorry if this is off-topic and ancient news. I was just wondering if
there are any old Apple employees/programmers who have a comment on this, or if
anyone has a good link about the fact It was a sore point w
:
>
> I'm sure macports is amazing, but for a few reasons I don't have the
> enthusiasm to do new packaging, more than linking in a few dlls, which
> doesn't seem feasible.
If you mention the URL of your project, someone else could work on creating a
MacPorts port of it.
On Wednesday 26 June 2024 at 06:32:50 pm AEST, Riccardo Mottola
wrote:
> if your App is open source and of general interest, a port in MacPortswould
> be a good way to distribute things - so that different versions ofMacs are
> handled better.
I'm sure macports i
Hi Steven,
Steven via macports-users wrote:
Ok, thanks, but I am not inclined/too busy to learn macports. My app
is cross platform, and supporting Mac is way too time consuming and
hard already. (I already have three macs with 4 different OSX on them!).
if your App is open source and of
Ok, thanks, but I am not inclined/too busy to learn macports. My app is cross
platform, and supporting Mac is way too time consuming and hard already. (I
already have three macs with 4 different OSX on them!).
My normal 32bit build system is actually using gcc from the command line on El
02 PM Richard L. Hamilton wrote:
>>
>> netpbm port contains pnmtopng, a command line tool.
>>
>>
>>> On Jun 20, 2024, at 21:44, Kenneth Wolcott wrote:
>>>
>>> Hi;
>>>
>>> is there a MacPorts port that converts ppm files to p
Hi Guys,I was wondering if anyone has a c++-11 dylib tarball/dmg for me to
include with my 32bit app so it will run on older Mac OSX ? I'm not super
technical about Mac stuff, but I should be able to install_name_tool my exe to
use it... Any other instructions?Thanks Steven Atkinson
https://sci
I am having a problem with the jupyter-notebook port (both 3.11 and 3.12) under
MacOS 14.5 (Sonoma) on an M1 13” MacBook Pro. More specifically,
jupyter-notebook launches and allows me to navigate my hard disk. However, when
I click on a notebook to try to edit/run it a new tab is opened in Safa
t to grep for a specific path like bin/
>
>> On Jun 23, 2024, at 07:49, Christoph Kukulies via macports-users
>> wrote:
>>
>> 7zip
signature.asc
Description: Message signed with OpenPGP
I can't the heck not figure out what the name of the binary is, once you did a
`sudo port install 7zip` under macOS?
$ p7zip
-bash: p7zip: command not found
$ 7zip
-bash: 7zip: command not found
$ pzip
-bash: pzip: command not found
$ p7zip
-bash: p7zip: command not found
$ 7z
-bash: 7z: command
MacBook Pro with M1 processor, macOS Sonoma 14.5, Xcode 15.4 and
its CLT’s.
So, all in all, a very positive experience.
Thanks to the MacPorts team!
Ciao
Franco
> On 12 Jun 2024, at 09:46, Franco Vaccari via macports-users
> wrote:
>
> Dear Josh,
>
> since your mail caugh
Dear Josh,
since your mail caught me a few minutes after updating from Ventura to Sonoma,
and a few seconds before I started to play with MacPorts migration, I felt
obliged to give the migrate command a shot…
Currently computing dependency order. Will let you know the outcome…
Ciao
Franco
Hello Ryan and Joshua,
Thank you very much for yor help with my Macports trac ticket (70090) regarding
the recalcitrant “missing” #include line in goaewsclient.c,
greatly appreciated.
Not knowing enough about the inner workings of the ‘port’ build process, I kept
running up against a rev
I must add that the behaviour is infact:
$ mail
Illegal use of "message list"
No mail for kuku
$
> Am 09.06.2024 um 11:20 schrieb Christoph Kukulies via macports-users
> :
>
> It seems that the installation of the mailutils port screwed up the
> functioning of th
It seems that the installation of the mailutils port screwed up the functioning
of the `mail` commandline tool for sending mails.
I'm pretty sure that I was able to forge the From field of an email I sent with
the "mail" command from the command line by editing
~/.mailrc with the line "from m...@
i just find out exactly how are you guys stealing all my financial accounts
dont you thought that some day i was going to find it out??
Mateo Flores Sanchez
Cameron Karhut
Camilo Palacios
Joana Aguilar
Talina Ramirez
Marta Hernandez "aka" Angelica Xajil
have been working with your tools and takin
Eric Gallager wrote:
I think that the `certsync` port (alternative to curl-ca-bundle) is
supposed to help with this...
I have curl-ca-bundle installed.
Should I remove it?
I read the description
Export x509 CAs from the Mac OS X Keychain.
The package implements exporting of x509 CAs from th
1 - 100 of 1056 matches
Mail list logo
