On Sep 21, 2021, at 23:49, Ian Wadham wrote:
> I wish to download from the Web a package called CocoaPods, however it needs
> a developers’ package of Ruby to build it.
>
> I am using MacOS Catalina 10.15.7. Apple provides Ruby in this MacOSversion,
> but will not allow it to be used for buildi
On Sep 8, 2021, at 08:37, Mark Lucas wrote:
> The version of baresip on MacPorts appears to be *very* out of date (v
> 0.6.0_3) The MacPorts package info Homepage URL for baresip is dead.
> The project appears to have moved to GitHub -
> https://github.com/baresip/baresip and seems to under act
macports.org and other secure web sites that use Let's Encrypt may no longer be
accessible to you if you use older versions of macOS or older browsers or user
agents. For example, the libcurl in macOS 10.14 can't talk to many Let's
Encrypt web sites now, including distfiles.macports.org and
pac
ch
should allow them to continue to fetch packages and distfiles.
On Oct 2, 2021, at 04:14, Ryan Schmidt wrote:
> On the web servers we control, we can apparently remove the expired DST Root
> CA X3 certificate from the chain that we send. That will help those systems
> that already
On Oct 2, 2021, at 22:06, Michael wrote:
>
> So, first, I want to say "Thank you" for this bit:
>
>> • From View menu select "Show Expired Certificates"
>
> In keychain access, I could not see the expired certs, and was thinking that
> they were just deleted for being old. Once I could find the
On Oct 2, 2021, at 20:11, André-John Mas wrote:
> Given a number of projects are only available for Homebrew, or only up to
> date for Homebrew, has any looked at a process for adapting a Homebrew recipe
> to a MacPorts one? Something like ‘port brew ’? I haven’t thought of
> all the implicatio
Please write to list addresses at lists.macports.org, not at the old hostname
that we discontinued using in late 2016.
On Sep 13, 2021, at 15:40, Epstein, David wrote:
>
> MacPorts base version 2.7.1 installed
> MacOs 11.5.2
> MacBook Pro (Retina, 15-inch, Mid 2015)
>
> I get the error message
On Oct 3, 2021, at 00:08, Ian Wadham wrote:
> OK, thanks Ryan, but how about https://guide.macports.org/#installing.xcode ?
>
> It explicitly says to install Xcode first, as a dependency of MacPorts, and
> then do xcode-select —install, which is what I have been doing for 10 years
> or more as
On Oct 3, 2021, at 02:58, Ian Wadham wrote:
> On 2 Oct 2021, at 6:29 pm, Ryan Schmidt wrote:
>> On Sep 25, 2021, at 23:14, Ian Wadham wrote:
>>
>>> MacPorts contains packages of many versions of Ruby, similarly to the
>>> Python and Perl groups, but the correspo
On Oct 5, 2021, at 04:29, Frank Dean wrote:
> I've submitted a pull request [1] for a new Portfile, `mod_tile`, but the
> checks are failing because this port requires the `mapnik` port to be
> installed with a non-default variant, `+postgis`. Similarly, it requires the
> `osm2pgsql` port to have
On Oct 3, 2021, at 16:05, Artemio González López wrote:
> I then deactivated python39 and py39-jupyter, and installed py37-jupyter. It
> gave me numerous errors complaining that I had to activate by hand several
> ports (liek, e.g., sudo port -f activate py37-ipython),
You should virtually n
On Oct 4, 2021, at 08:43, Artemio González López wrote:
> 1. Should I activate python39 and decativate python37 before installing the
> 3.9 versions fo numpy, scipy and matplotlib?
It's not necessary. MacPorts handles dependencies for you. If you install e.g.
py39-numpy and python39 is not alre
On Oct 4, 2021, at 09:24, Giuseppe 'ferdy' Miceli wrote:
> I would daresay to remove everything (—force option would be handy) and then
> start over again from scratch :-)
The global force flag (-f) should be used sparingly since its use almost always
indicates that some problem has already occ
On Oct 4, 2021, at 15:57, Christopher Jones wrote:
> On 4 Oct 2021, at 9:18 pm, Artemio González López wrote:
>
>> I only experienced a very minor glitch, namely that for some reason
>> (probably a minor bug?) the /opt/local/Library/Frameworks/Versions/3.9/bin
>> directory where jupyter resides
On Oct 3, 2021, at 02:32, raf wrote:
> The instructions
> https://trac.macports.org/wiki/ProblemHotlist#letsencrypt
> include a suggestion of asking other webserver
> administrators to delete "DST Root CA X3" from their
> full chain, and use --preferred-chain "ISRG Root X1"
> when next renewing
On Sep 28, 2021, at 05:09, Michael Monschau wrote:
>
> Background:
> I recently had the need to resort to some open software to add certain PDF
> manipulation features to one of my products. The open source tool I am using
> is podofo-0.9.7. That uses various other libraries including openssl. A
On Oct 5, 2021, at 18:09, Ryan Schmidt wrote:
> By default MacPorts fetches binaries for ports when it can. Those binaries
> were built with default deployment target and SDK settings. If you are trying
> to create a MacPorts installation using different settings for those value
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 pr
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&clone from the master of the original:
>
> git checkout master # Go to branch master in my local clone
> git pull upstream master
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 setup
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 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:
> /opt/local/var/macports/build/_opt_local_var_macports_s
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 wa
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 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
> (http://www.ks.uiuc.edu/Research/vmd/plugins/doxygen/compiling.html#co
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 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 "submission\[data\]=$
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
>
> /opt/local/var/macports/build/_opt_local_var_macport
> 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
"audac
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 the name
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 do
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 control
> 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 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 457
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 use
On Nov 10, 2021, at 05:31, Gregory Dodwell wrote:
> M1 Macbook Pro (2020 model); Mac OS 12.0.1; Macports version 2.7.1
>
> Error message when executing "sudo port upgrade outdated":
> "Error: Failed to build gcc11: command execution failed"
> The build log is huge, so I won't copy/past it
On Nov 11, 2021, at 17:07, Tom wrote:
> Hi,
>
> when trying to run an X11 program, I get the following error message:
>
> (putty:8198): Gtk-WARNING **: 00:06:49.190: cannot open display: :0
>
> How can I fix that?
Assuming you are running Mac OS X 10.5 or later:
Check your .zprofile or .p
> 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 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 t
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 direc
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 w
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:
https://github.com/macports/macports-base/commit/cf42f8ab68e9ea8
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 *);
>
> I
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
> (https://trac.macports.org/wiki/XcodeVersionIn
On Nov 20, 2021, at 12:19, Chilli wrote:
>
> Hi mailing list participants.
>
> I'm going to introduce several topics. At your choice, leisure and
> convenience, a response to any is appreciated.
>
> 1) First of all, as a user, I am tremendously grateful to all the macports
> developers. MacP
On Nov 21, 2021, at 10:08, Chilli wrote:
> The reason I chose Mojave was because it is the last macOS to support running
> 32-bit applications, but obviously my research was not deep enough. Since it
> can not build 32-bit applications... looks like I'll be backing up the Mojave
> install and r
On Nov 22, 2021, at 07:14, rmgls wrote:
> mplayer install fails because liboil does not build correctly.
> as i can see it is gtkdocize related.
> any hints would be appreciated.
We will need more information from you. I see packages successfully built for
liboil on our build system on macOS 1
On Nov 23, 2021, at 06:49, Ryan Schmidt wrote:
> On Nov 22, 2021, at 07:14, rmgls wrote:
>
>> mplayer install fails because liboil does not build correctly.
>> as i can see it is gtkdocize related.
>> any hints would be appreciated.
>
> We will need more inform
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 wa
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 wit
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 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 y
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 ti
On Nov 30, 2021, at 14:47, Christopher Nielsen wrote:
> Back in May, @ryandesign mentioned that we have the option of upgrading our
> buildbot farm with more powerful CPUs. Said farm is currently hosted on
> Xserves, and since the CPUs are socketed, it’s reasonably straightforward.
The new CPU
On Nov 29, 2021, at 20:21, Uli Wienands wrote:
> Well, I wonder whether someone did something within the last day or two. I
> just tried it again, and lo-and-behold, perl5.26 installed just fine & now
> MacPorts is getting to work on the backlog of things that I could not update
> because of
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 w
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 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
> E
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 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 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 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 lightweight
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
>>> s
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 ba
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
> War
On Dec 20, 2021, at 09:12, dan d. wrote:
> Recently I have increasingly begun to get the failure to activate on installs
> and upgrades. It prompts to use the "-f activate portname"
> approach. This begins but never finishes; requiring a control-c to stop it.
You usually should not force a por
On Dec 21, 2021, at 13:17, dan d. wrote:
> Ok, I will do so the next time it happens. I don't recall seeing the
> "deactivate" prompt.
The message I thought you were referring to is:
https://github.com/macports/macports-base/blob/master/src/registry2.0/portimage.tcl#L597
Image error: $file i
On Jan 4, 2022, at 02:24, Mick wrote:
> On Tue, Jan 04, 2022 at 08:56:43AM +0700, Michael Newman via macports-users
> wrote:
>> I'm using the -f option because I copied it from some recommendation I read
>> somewhere. I'm not smart enough to figure things like this out myself so I
>> usually re
On Jan 4, 2022, at 02:52, Christopher Jones wrote:
> Personally, I also occasionally run
>
>> port list requested
>
> to see the list of ports I have actively *requested* to be installed. This
> excludes ports just installed as dependencies of others.
Note that you should use "port installed
On Jan 3, 2022, at 12:20, Riccardo Mottola wrote:
> how to react best for Let's Encrypt expiration?
https://trac.macports.org/wiki/ProblemHotlist#letsencrypt
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 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 fi
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 ha
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
> af
On Jan 15, 2022, at 10:10, dan d. wrote:
> I did a search and found nothing. Did I miss something?
Need more information. You would like to find software that allows you to send
text messages? If so, that would probably be provided by some service that you
would have to subscribe to, so you sh
On Jan 20, 2022, at 17:05, Greg Earle wrote:
> Is anyone still using/building on Sierra?
Sure. We still produce binaries for Mac OS X 10.6 and later.
> it tries to build gettext-tools-libs @0.21_0+universal and croaks.
I saw a build failure of one of the gettext subports, might've been
gettex
On Jan 20, 2022, at 22:12, Gabriel Rosenkoetter wrote:
> I didn't have the perl5 port installed on this system at all, just the
> several perl5.xx ports. So I did `sudo port install perl5`.
>
> And that's neat, but:
>
> [58] (gr@wedge:~)% which perl
> /opt/local/bin/perl
> [59] (gr@wedge:~)% ls
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 ma
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 @5.26.1_0+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 displa
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 "e
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 @5.28.3_0+perl5_3
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 no
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 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 dat
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 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 onl
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 i
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
> a
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 definit
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 w
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 3.1.2
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 interp
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 autom
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 y
901 - 1000 of 1642 matches
Mail list logo
