On Nov 14, 2021, at 04:53, Gerben Wierda wrote:
> I was just curious: why does the libsdl2 port which is at version 2.0.16
> install 2.0.0 libraries? How does that happen? Just learning.
There is no reason why the version of a port needs to have any relationship
whatsoever with the version of
On Nov 27, 2021, at 19:58, Ken Cunningham wrote:
>> Ok... the significance of this is...??
> Well in your case, the significance of appears overwhelming — in that it is
> an excellent clue as to the cause of your problem, I believe.
>
> ie - there is nothing wrong on your system, it is nothing
On Nov 27, 2021, at 02:22, Pieter van Oostrum wrote:
> chilli.names...@gmail.com writes:
>
>> To uninstall macports entirely, I use the three commands below in a script
>> (which I assume I got
>> from the manual, but it's been awhile, I do not recall), but they work just
>> as well one at a
On Nov 27, 2021, at 17:45, Tom wrote:
> gcc10 does not build. How can I fix that?
File a bug report and attach your main.log file, assuming a ticket covering
this problem has not already been filed.
On Nov 26, 2021, at 07:16, Masoud Ghaderi wrote:
> Hello,
> I am following the steps from
> https://guide.macports.org/chunked/installing.macports.uninstalling.html to
> remove mac ports from my machine (it is currently functioning but I want to
> migrate to homebrew and I've heard they do not
On Nov 26, 2021, at 19:45, Uli Wienands wrote:
> A number of ports apparently want to install perl5.26. In this specific case
> it is fricas. For reasons I cannot fathom prl5.26 fails during the destroot
> phase on my system (SL, 10.6.8).
>
> So I try installing perl5.26 by itself; it fails
On Nov 18, 2021, at 08:47, Eric Gallager wrote:
> Didn't MacPorts start doing `chflags hidden` on
> /opt/local/var/macports at some point to stop Spotlight from indexing
> it?
You appear to be correct, based on this commit message:
On Nov 18, 2021, at 13:15, James Secan wrote:
> I’m moving to a Big Sur system, and since I don’t use Xcode for anything I
> manually download and install the CLI tools by themsleves. I installed
> v12.5.1 as per the info on the MacPorts wiki
>
On Nov 19, 2021, at 00:01, Masha Vecherkovskaya wrote:
> Could someone please have a look, I can’t figure out this one myself. I’m
> trying to build a program and make fails with
> error: conflicting declaration of 'char* ctermid(char*)' with 'C' linkage
> 222 | char*ctermid(char *);
>
>
MacPorts base doesn't do anything with Spotlight. It doesn't depend on it
existing, nor does it tell Spotlight to index or not to index anything.
MacPorts predates the existence of Spotlight.
As far as I know, ports don't depend on Spotlight having indexed the MacPorts
prefix or the build
On Nov 15, 2021, at 15:11, Tom wrote:
> On 12. Nov 2021, at 21:17, Chris Jones wrote:
>>
>> Impossible to say without more data.
>>
>> Do you have any crash logs in Console ? Any other messages ?
>>
>> What application are you running ? Try install a simple one like xclock and
>> see if that
> On Nov 11, 2021, at 23:20, raf wrote:
>
> or using
> the curl binary in the path
Never going to happen. We don't want to maintain two code paths for the same
purpose.
On Nov 25, 2021, at 18:20, Gerben Wierda wrote:
> I’ve just received a new Mac and it is the first one with M1 hardware. And of
> course it comes with macOS 12.
Congrats! I hope you like it.
> So, as sort of a first step, I downloaded the MacPorts Monterey package. When
> I ran that, macOS
On Oct 11, 2021, at 15:54, Sriranga Veeraraghavan wrote:
> I am by no means a macports expert, but based on my experience, I think you
> can ignore the warnings. AFAIK, the warnings are telling you the following:
>
> 1. The first message you received regarding ffmpeg indicates that ffmpeg
On Oct 27, 2021, at 13:23, William Parducci wrote:
> I’m tried to install nmap on a clean install of macports in Big Sur. When it
> got to configuring clang it is threw this error:
>
>
> configure:2838: /usr/bin/clang -qversion >&5
> clang: error: unknown argument '-qversion', did you mean
On Oct 27, 2021, at 11:11, dan d. wrote:
> If I had to guess the install routine is not fetching the youtube-dl
> distribution files to install.
>
> I get this error message
>
> Error: Failed to install youtube-dl: no destroot found at:
>
On Oct 23, 2021, at 05:43, Gerben Wierda wrote:
> The way I can update my ports tree using git is:
>
> # Updating the master of my fork from the master of the original:
>
> git checkout master # Go to branch master in my local clone
> git pull upstream master #
On Oct 16, 2021, at 07:02, rmgls wrote:
> wavpack installed in macports need to be updated to the last
> available version.
> wavpack emits a warning when used with tag3 for instance.
>
> i downloaded the latest version from the web site
> it builds fine, and seems to work fine with sox.
>
On Oct 20, 2021, at 22:06, Sriranga Veeraraghavan wrote:
> Is there a way to add an optional variant to the QEMU Portfile that would
> apply this patch?
Yes, it is technically possible to do that. However, we prefer not to include
and forever maintain unofficial patches. Instead, we would
On Oct 18, 2021, at 20:58, Jerry wrote:
> 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
On Nov 6, 2021, at 05:39, Gerben Wierda wrote:
> I was looking at updating nsd (for which I am maintaining and it is high time)
>
> But fetching failed on macOS Mojave (where I have my MacPorts setup).
>
> :debug:fetch Executing org.macports.fetch (nsd)
> :info:fetch ---> nsd-4.3.8.tar.gz
On Nov 8, 2021, at 09:51, dan d. wrote:
>
> This from the log on install mpv failure, help please:
>
>
> :info:build WafError.__init__(self,self.format_error())
> :info:build
> :info:build Build failed
> :info:build -> task in 'objects' failed with exit status 1:
> :info:build {task
On Nov 7, 2021, at 06:23, Christopher Jones wrote:
>
>>> it uses the libcurl support compiled into macports base, which
>>> defaults to using the system curl. To change that you need to rebuild
>>> base against an updated lib curl.
>>
>> Is that something that can be made to happen for all
On Nov 3, 2021, at 06:34, Maxim Abalenkov wrote:
> How are you? I hope all is well with you. I have a relatively simple
> question. I would like to install Tcl in order to compile the VMD code and
> its plugins from source
>
On Oct 28, 2021, at 08:05, John Wiggins wrote:
>
> It seemed to work yesterday under Xcode 13.0 and its CLT.
> Now emacs-dev seems to fail after update to Xcode 13.1 and CLT for Xcode 13.1.
>
> I am a bit of a novice, doe the following in
>
>
On Oct 31, 2021, at 04:37, raf wrote:
> On 10.14:
>
>> /opt/local/libexec/mpstats submit
> Submitting data to https://ports.macports.org/statistics/submit/ ...
> Error: Peer certificate cannot be authenticated with given CA certificates
> while executing
> "curl post
> On Nov 5, 2021, at 10:14, rmgls wrote:
>
> at launching audacity crashes.
> if attached files does not match, please tell me exactly what you expect.
The crash log would be most helpful. It should be located in /Users//Library/Logs/DiagnosticReports/ - find the most recent one with
On Nov 5, 2021, at 07:32, rmgls wrote:
> trying to build audacity displays:
>
> 7 broken files and 1 broken port
> continue Y/N?
See https://trac.macports.org/ticket/63741
> continuing build completely, but launching audacity
> fails.
In what way? Error message? Crash? (If so, show crash
On Oct 31, 2021, at 17:53, Artemio González López wrote:
> 1. Is there an easy check which ones of my previously installed ports weren’t
> installed?
You have a text file listing the ports you previously installed on macOS 11.
You have the instructions for how you created that file. You can
On Nov 5, 2021, at 11:39, rmgls wrote:
> On 5 Nov 2021, at 16:54, Ryan Schmidt wrote:
>
>> The crash log would be most helpful. It should be located in /Users/> username>/Library/Logs/DiagnosticReports/ - find the most recent one with
>> "audacity" in
On Nov 7, 2021, at 00:03, Kastus Shchuka wrote:
>
> On the other hand, it's plain dumb why it works for me. As you can see below,
> org.macports.fetch does not use HTTPS, it downloads over HTTP. Certificates
> are just irrelevant for that.
>
> I am not sure what part of macports.conf
> On Nov 8, 2021, at 04:00, FritzS GMX wrote:
>
> Which users (and their groups) are created by MacPorts and how can they be
> created during a new installation so that they get a UID (also GroupID)
> previously defined by me.
> Is there possibly a script suggestion that could be used before
On Dec 12, 2021, at 19:10, Christopher Chavez wrote:
>> And shouldn’t ports that use java not depend on a java that comes with (old,
>> outdated) java’s in macOS? But install and use an open source version
>> instead? Or use the one from Oracle if available?
>
> Because JDK is not a
On Dec 11, 2021, at 23:54, fgyamauti2 fgyamauti2 wrote:
> The weird thing is that everything suspicious inside '/usr/local/etc' is a
> configuration file of stuff that is related to MacPorts. More precisely, I
> have suspicious folders named 'fonts' (from fontsconfig), 'gnutls',
> 'openldap',
On Sep 28, 2021, at 15:31, Tobias Welti wrote:
> I have trouble using port upgrade outdated since a few weeks ago. I just
> receive the following message:
> ===
> $ sudo port upgrade outdated
> Error: python39: Error executing universal: can't read "configure.sysroot":
> no such variable
>
On Dec 10, 2021, at 13:51, Langer, Stephen A. (Fed) wrote:
> Is anyone running gtk3 programs on an M1 or on Monterey? The following
> simple script crashes on an M1 Mini with Monterey, when run with python 2.7:
>
> import gi
> gi.require_version("Gtk", "3.0")
> from gi.repository import Gtk
>
On Dec 11, 2021, at 15:15, Langer, Stephen A. (Fed) wrote:
>
> On 12/11/21, 9:00 AM, Ryan Schmidt wrote:
>
>> On Dec 10, 2021, at 13:51, Langer, Stephen A. (Fed) wrote:
>>
>>> Is anyone running gtk3 programs on an M1 or on Monterey? The following
>>&
On Dec 15, 2021, at 14:25, Dave Horsfall wrote:
> On Fri, 10 Dec 2021, Ryan Schmidt wrote:
>
>> The "-arch x86_64 -arch i386" in the log does seem to indicate MacPorts
>> is doing a universal build. The ways that could happen:
>>
>> * You specified
On Dec 16, 2021, at 02:55, Greg Earle wrote:
>
> On a 2010 Mac Pro running macOS Mojave 10.14.6, I'm getting this:
>
> --
> [0:48] nightowl:/ % sudo port upgrade outdated
> Nothing to upgrade.
> ---> Scanning binaries for linking errors
> ---> Found 2 broken files, matching files to ports
>
On Dec 10, 2021, at 02:29, Chris Jones wrote:
>
> On 9 Dec 2021, at 10:49 pm, SeaQuench wrote:
>>
>>
>> After downloading and installing the latest MacPorts for Catalina, I
>> followed the instructions to migrate MacPorts:
>> https://trac.macports.org/wiki/Migration
>> Reinstalling the ports
On Dec 8, 2021, at 16:42, Dave Horsfall wrote:
> MacBook Pro (13-inch, Mid 2010), macOS High Sierra 10.13.6.
>
> I finally got around to installing Xcode 10.1 and matching CLT, then
> started to rebuild MacPorts, dutifully following the instructions in the
> Migration Guide.
>
> It karked it
On Dec 11, 2021, at 11:24, Richard L. Hamilton wrote:
> CVE-2021-44228 sounds kinda scary!
We appear to have a jakarta-log4j port but it is version 1.x, not 2.
On Dec 13, 2021, at 21:11, Richard L. Hamilton wrote:
> macOS does not have the "pwait" command that Linux and some other Unix
> versions have, which allows waiting on any process (not just a child), given
> the PID. There would definitely be uses for that, like dealing with a process
> that
On Jan 13, 2022, at 17:01, Bill Cole wrote:
> On 2022-01-13 at 16:26:01 UTC-0500 (Thu, 13 Jan 2022 15:26:01 -0600) Will
> Senn is rumored to have said:
> [...]
>>
>> My question for y'all goes like this - How long will macports continue to
>> "work" on Mojave?
>
> No one can actually give a
On Jan 13, 2022, at 18:27, Manfred Antar wrote:
> gqrx will not build on new version of gnuradio
Then please file a bug report in the issue tracker.
On Jan 13, 2022, at 22:33, chilli.namesake wrote:
>
>> Sometimes we can work around these problems, with or without the developer's
>> help, to get a port working again; other times we can't.
>
> Your explanation is accurate, and though I realize it is easier said than
> done, this shouldn't
On Jan 9, 2022, at 14:56, Sebastian Flothow wrote:
> I’m using MacPorts on OS X El Capitan 10.11.16, currently kdelibs4 and
> soprano are outdated:
>
> $ port outdated
> The following installed ports are outdated:
> kdelibs4 4.14.3_16 < 4.14.3_17
> soprano
On Mar 5, 2022, at 07:29, chilli.namesake wrote:
> On Mar 4, 2022, at 20:39, chilli.namesake wrote:
>
>> https://trac.macports.org/ is refusing to let me submit a ticket returning
>> an inscrutable "invalid parameters" complaint.
That error doesn't immediately ring a bell for me, and since
On Mar 7, 2022, at 06:14, Michele Venturi wrote:
> Web browsers are even more complicated but
> you do not need to install xcode to use safari...
But you do need to install Xcode to *compile* Safari.
In the same way, you need to install Xcode to *compile* mpv, but you do not
need Xcode to
On Feb 26, 2022, at 12:04, Haren Samarasinghe wrote:
> After reading the installation guide [1], quite a few people that I've
> introduced MacPorts to have thought that a full XCode installation is
> required. They're uncertain of doing this due to the large amount of space it
> requires.
>
On Mar 7, 2022, at 08:06, Michele Venturi wrote:
> There is no binary of MPV for OSX 10.13.6? It's too old?
I see a binary of mpv for macOS 10.13:
http://packages.macports.org/mpv/
We produce binaries for Mac OS X 10.6 and later.
Only binaries of default variants are produced. If you are
On Mar 7, 2022, at 08:34, Michele Venturi wrote:
> If I install MPV without Xcode I get an error when I launch it:
>
> dyld: Library not loaded: @rpath/libswiftAVFoundation.dylib
> Referenced from: /opt/local/bin/mpv
> Reason: image not found
>
> It's missing something,have you tried to
On Mar 7, 2022, at 06:02, Michele Venturi wrote:
> Sadly xcode is needed even for something as simple as
> a media player, for example mpv, I wonder why actually.
Media players are probably extremely complicated pieces of software. Hardly
what I would call simple.
In the case of mpv, it
(resending from correct address)
On Mar 13, 2022, at 16:34, Dave Horsfall wrote:
> Smooth as the proverbial baby's bottom on an oldish MacBook Pro, High
> Sierra 10.13.6; well done, all.
>
> I'm quite taken by the progress bar on "cmake"; it keeps changing its
> mind, just like a MacOS
On Mar 14, 2022, at 10:40, James Secan wrote:
> It is a macOS alias. I use soft links a lot, but only for items that I’m
> accessing when working in a Unix shell.
MacPorts should be able to use your Xcode wherever it is, provided that
`xcode-select -p` shows its path or the path of a symlink
On Mar 9, 2022, at 19:55, Lenore Horner wrote:
> Begin forwarded message:
>
>> From: mailer-dae...@yahoo.com
>> Subject: Failure Notice
>> Date: March 9, 2022 at 20:50:45 EST
>> To: lenorehor...@sbcglobal.net
>>
>> Sorry, we were unable to deliver your message to the following address.
>>
>> :
On Mar 9, 2022, at 17:13, James Secan wrote:
>
> when I run "port upgrade installed -u outdated”
This command doesn't make a great deal of sense. You're asking MacPorts to
upgrade the "installed" ports (which includes those those that are outdated and
those that aren't) and also the "outdated"
On Mar 10, 2022, at 07:56, Lenore Horner wrote:
>> You could run "sudo port -fv selfupdate" to force MacPorts to reinstall
>> 2.7.2 even though it thinks it already has. If you try that and it
>> experiences some error, let us know.
>
> I did that and it failed but then I remembered that
On Mar 10, 2022, at 03:18, Sriranga Veeraraghavan wrote:
> On Mar 10, 2022, at 00:34, Ryan Schmidt wrote:
>
>> On Mar 9, 2022, at 17:13, James Secan wrote:
>>>
>>> when I run "port upgrade installed -u outdated”
>>
>> This command doesn't mak
On Mar 17, 2022, at 16:22, Tom wrote:
> Hello people, how do I install a python replacement for macOS 12.3?
MacPorts offers many versions of Python. Python 2.7 (/usr/bin/python) was
removed in macOS 12.3. If you want to continue to use Python 2.7, you can
install the python27 port:
sudo port
On Mar 17, 2022, at 21:37, Bill Cole wrote:
> On 2022-03-17 at 17:22:51 UTC-0400 (Thu, 17 Mar 2022 22:22:51 +0100) Tom is
> rumored to have said:
>
>> Hello people, how do I install a python replacement for macOS 12.3?
>
> port install python310 python_select
python_select is a dependency of
On Mar 10, 2022, at 18:40, James Secan wrote:
> In working my way through my recent “phantom ports” issue I ran the command
> “port diagnose” and was more than a bit surprised by the output line:
>
> Error: currently installed version of Xcode, none, is not supported by
> MacPorts.
>
>
On Mar 11, 2022, at 02:02, Michele Venturi wrote:
> What is wrong is that a simple package manager
> requires an entire multigigabyte professional IDE;
> I have even taken the time to talk to them about it
> and file a bug about it,but they clearly don't care...
> It's surely not a new issue,it's
On Mar 10, 2022, at 19:57, Sriranga Veeraraghavan wrote:
> On Mar 10, 2022, at 05:10, Ryan Schmidt wrote:
>
>> "port reclaim --enable-reminders" enables reminders;
>> "port reclaim --disable-reminders" disables them.
>
> Thanks for letting me know ab
On Mar 12, 2022, at 21:57, Richard L. Hamilton wrote:
> Is there a way one can see by examining Portfiles (ideally something that
> could be scanned for with e.g. a perl script), or preferably, with some
> "port" command, which ports require command line tools vs Xcode vs neither
> (albeit
On Mar 12, 2022, at 22:35, Sriranga Veeraraghavan wrote:
> Thank you - I did not know about the port-* manages.
>
> I see from port-reclaim(1) that there are man pages for several other port
> commands, but I didn’t see a reference to these other man pages in the
> port(1) man page. For
I noticed copies of the Install macOS Monterey application on both the Catalina
and Big Sur MacPorts buildbot build machines. I've of course never requested
the download of these installers on those systems and they are configured not
to update automatically and not to download new updates
On Feb 19, 2022, at 01:24, rmgls wrote:
> how to bypass the 2.7 python in /system/Library and direct by default to a
> macport version or even a user path.
> details:
> port install scons 3.1.X
> port select --set …..
> invoking scons calls the system scons 2.7?
The scons port version
On Feb 20, 2022, at 11:57, Kirill A. Korinsky wrote:
> The url: https://ports.macports.org/port/gcc10-bootstrap/details/ says that
> port has been deleted.
>
> But it quite alive:
> https://github.com/macports/macports-ports/blob/master/lang/gcc10-bootstrap/Portfile
Bug reports for the ports
On Feb 13, 2022, at 02:59, Rainer Müller wrote:
>
> On 10/02/2022 13.12, Greg Bell wrote:
>> I'm trying to update yt-dlp (a youtube-dl fork with additional features and
>> fixes)
>>
>> and incurred this…
>> Error: Failed to build graphviz: command execution failed
>>
>> I'm unsure how to
On Mar 18, 2022, at 03:16, VACCARI FRANCO wrote:
> So, is it considered “safe” in MacPorts’ view to update to MacOS 12.3 and
> Xcode 13.3? I remember a warning on the list about this, due to Python 2.x
> removal from Apple
My recommendations posted last month are unchanged.
On Mar 26, 2022, at 00:48, Michele Venturi wrote:
> As usual this project too is a mess because everyone has a different idea of
> what it is,has been and will be.
If you have constructive criticism for changes that should be made, feel free
to start discussions about them. Otherwise you may
On Mar 27, 2022, at 12:48, dan d. wrote:
> Can one delete older python versions then the current python10? Do some
> ports anticipate an older version?
You can uninstall any ports you no longer need or want to have installed. If
any installed ports still declare dependencies on them, MacPorts
On Mar 27, 2022, at 13:06, Richard L. Hamilton wrote:
>
> (although I think Apple provides the servers)
Apple provided the servers from late 2006 [1] (when our first home OpenDarwin
closed its doors) until late 2016 [2] (when Apple's macOS forge service shut
down). Since then, we have used
On Apr 1, 2022, at 09:42, Peter West wrote:
> On 1 Apr 2022, at 11:53 pm, Ryan Schmidt wrote:
>
>> On Apr 1, 2022, at 04:32, Peter West wrote:
>>
>>> On 1 Apr 2022, at 7:22 pm, Peter West wrote:
>>>>
>>>> I just tried to insta
On Apr 1, 2022, at 22:26, Peter West wrote:
> I’m following dependencies which have their own dependency on qt4-mac and are
> set to universal, I presume, because I get messages like
>
> Error: Cannot install automoc for the archs 'arm64 x86_64' because
> Error: its dependency qt4-mac only
On Apr 1, 2022, at 08:52, Christoph Kukulies wrote:
> I’m in the course of installing
>
> sudo port install stlink
>
> The question came to me whether it’s possible to install a specific version
> of the software?
https://trac.macports.org/wiki/howto/InstallingOlderPort
On Apr 1, 2022, at 04:32, Peter West wrote:
> On 1 Apr 2022, at 7:22 pm, Peter West wrote:
>>
>> I just tried to install kmymoney4 on my M1 running 12.2.1. MacPorts spat the
>> dummy with
>>
>> Error: Cannot install kmymoney4 for the arch 'arm64' because
>> Error: its dependency qt4-mac only
On Apr 1, 2022, at 13:09, Artemio González López wrote:
> After executing “port diagnose” in my 2020 13” MacBook Pro running the latest
> version of the operating system (Monterrey 12.1.3, I believe) I got the
> following output:
>
> Warning: objc[10836]: Class
On Apr 1, 2022, at 13:38, Werner LEMBERG wrote:
>
> ```
> ccache /opt/local/bin/clang-mp-13 ... conftest.c >&5
> ccache: error: Failed to create temporary file for
> /run/user/507/ccache-tmp/tmp.cpp_stdout.RTVNqj: Operation not permitted
> ```
> What's the reason that `port` tries to use
On Apr 4, 2022, at 14:25, Dave Allured - NOAA Affiliate wrote:
>
> On Sun, Apr 3, 2022 at 4:23 PM Ryan Schmidt wrote:
>> On Apr 1, 2022, at 13:09, Artemio González López wrote:
>>
>> > After executing “port diagnose” in my 2020 13” MacBook Pro running the
>>
Please direct all mailing list questions to the addresses at
lists.macports.org, not the older addresses that were deprecated in late 2016.
I've fixed the address in this reply.
On Mar 26, 2022, at 04:54, Epstein, David wrote:
> I am using MacPorts base version 2.7.2 under OS 11.6.4.
> All my
On Mar 29, 2022, at 09:00, Peter Brommer wrote:
> I somehow managed to shoot myself in the foot with an ill considered forced
> deactivate. A port upgrade outdated command would abort when it tried to
> install libgcc-devel. This must have been a new dependency of one of my
> installed ports
On Mar 23, 2022, at 08:48, Michele Venturi wrote:
> If MacPorts is not a package manager we need one,
> I'd say HomeBrew could be the right tool for the job.
I'm not sure what these remarks are in regards to, but MacPorts was started in
2002 a ports collection [1] based conceptually on FreeBSD
On Jan 26, 2022, at 08:24, Arno S. Hautala wrote:
> On 25 Jan 2022, at 12:39, paul wrote:
>
>> /usr/sbin/cron
>> /opt/local/bin/bash
>> /opt/local/bin/rsnapshot
>> /opt/local/bin/rsync
>> /opt/local/bin/gcp
>> all have full disk access in system preferences.
I'm not sure if this is it, I've
On Jan 29, 2022, at 10:56, Richard L. Hamilton wrote:
>
> But looking at the dovecot Portfile, it seems the dependency on apache-solr8
> is specific to the +solr variant (which you have, to be sure). So assuming
> your installation isn't a bit confused somehow, maybe port isn't always smart
>
Heads up! For users who want MacPorts to "just work" I recommend not upgrading
to macOS 12.3 (or the beta of it that is already out) for awhile, because it
will remove /usr/bin/python, upon which many ports probably still rely. Stick
with macOS 12.2 or earlier until we've had a chance to notice
On Feb 7, 2022, at 12:52, Bill Cole wrote:
> On 2022-02-07 at 13:16:54 UTC-0500 (Mon, 7 Feb 2022 10:16:54 -0800)
> Watson Ladd is rumored to have said:
>
>> On Mon, Feb 7, 2022 at 9:59 AM Marius Schamschula wrote:
>>>
>>> Watson,
>>>
>>> Compiler?
>>
>> protoc: the thing that takes the
On Jan 28, 2022, at 15:34, Dave Horsfall wrote:
>
>mackie:~ dave$ echo $DISPLAY
>
>mackie:~ dave$
>
> Is this something I forgot to do during the upgrade? I set $DISPLAY to
> ":0" (an old Unix trick) to no effect,
Setting DISPLAY to :0 is correct on Mac OS X 10.4.x and earlier, but
On Jan 21, 2022, at 19:43, Gabriel Rosenkoetter wrote:
> I'm… also not sure it's even actually a good idea, since, in my experience,
> Perl is much more flexible about newer versions of `perl` functioning with
> "out-dated" versions of libraries *and* vice versa than, say, PHP is. (I
> think
On Jan 21, 2022, at 22:48, Kastus Shchuka wrote:
> This is for example what I have:
>
> $ port installed and perl5
port installed perl5
"installed" is the command, "perl5" is the list of ports the command will
operate on.
> The following ports are currently installed:
> perl5
On Jan 21, 2022, at 23:32, Gabriel Rosenkoetter wrote:
>
> I think the [+] label, in the output of `port info ` is a confusing
> UI/UX choice, especially in the context of the + as an argument to `port
> install +_version` to request activation of a specific Port
> version.
>
> I think
On Jan 22, 2022, at 00:28, Kastus Shchuka wrote:
>
> Please note a clash of terms as there is port action "installed" and port
> pseudo-portname "installed". That is why "port installed" is a valid syntax
> ("installed" is an action here), while "port active" is not. You have to use
> action
On Jan 22, 2022, at 01:15, Gabriel Rosenkoetter wrote:
>
> On 2022-01-22 01:28 EST, Kastus Shchuka wrote:
>> $ port echo installed and perl5
>> perl5 @5.26.1_0+perl5_28
>> perl5 @5.28.3_0+perl5_28
>> perl5
On Jan 22, 2022, at 09:36, Richard L. Hamilton wrote:
> I have no idea of the difficulty of such a change, but it would be
> interesting if Portfiles contained a release date, and the database of
> installed ports had both a copy of that for any given installed version, and
> perhaps the
On Jan 22, 2022, at 09:22, Gabriel Rosenkoetter wrote:
>> If we stick with multiple perl versions, and the perl5 port to create the
>> symlinks, then maybe it would indeed help reduce some confusion to change
>> the perl5 port's version to 1.0, or a MMDD date, or anything else that
>> is
On Jan 22, 2022, at 09:06, Gabriel Rosenkoetter wrote:
>
> On 2022-01-22 09:10 EST, Ryan Schmidt wrote:
>> The use of the "+" character is intentional.
>> "+" means a variant is enabled. "-" means a variant is disabled.
>> "[ ]"
On Jan 22, 2022, at 10:21, Richard L. Hamilton wrote:
> On Jan 22, 2022, at 11:13, Ryan Schmidt wrote:
>
>> Or are you referring to the date when an update of a portfile was committed
>> to GitHub? If so, why would that be useful to you?
>
> The latter, since the former
On Jan 16, 2022, at 13:28, phle...@cantab.net wrote:
> Thanks for your brilliantly helpful response.
> Yes.. the pings are indirectly to blame!!
> No, I am not running a third party firewall.
> But I read the notes and noticed the comments about
> changing the max_hosts_to_ping: I had noticed
>
On Apr 5, 2022, at 13:04, Stanton Sanderson wrote:
> Wondering if anyone else has found problems with the latest update of
> Lilypond-devel (to v 2.23.7) on Big Sur (11.6.5) and Frescobaldi (3.1.3)… Had
> to revert to Lilypond-devel 2.23.6.
Would you care to specify what those problems were?
1201 - 1300 of 1456 matches
Mail list logo
