On Mar 15, 2020, at 09:13, Ken Cunningham wrote:
> on macports you pin a package using a personal repository.
>
> I explained it a few answers above. It's a very simple, 30 second, procedure.
But that is not what we want users to need to do. When a user encounters a
problem, we do not want
On Mar 15, 2020, at 18:50, j...@tigger.ws wrote:
> Can I download a port build, 'maintain it' build and install on my system?
I don't think I understand your question.
You can install a port by running "sudo port install thePortName". In what way
is what you are asking different from that?
On Mar 14, 2020, at 00:39, Jeffrey Walton wrote:
> My old PowerMac G5 cannot build the CMake being supplied with
> MacPorts. I know CMake now requires C+11 or C++14, and the antique
> tools on the Mac do not meet the requirements. I want to pin CMake to
> an older version for the Mac. For
I am dropping macports-dev from Cc because the question is not about developing
MacPorts.
On Feb 7, 2020, at 18:42, Ruben Di Battista wrote:
> Hello,
> I’m experiencing a problem (https://github.com/davidhalter/jedi/issues/1375).
>
> Running this on a Python installed with Macports:
> ```
>
On Feb 26, 2020, at 04:46, Franco Vaccari wrote:
> sudo port install cctools +xcode
>
> properly installed cctools. Is this expected,
Yes, that is expected. The +xcode variant of this port means "Don't actually
build this port; just install symlinks to the versions of the programs that
On Mar 11, 2020, at 19:14, Dave Horsfall wrote:
> As an aside, my own MacPorts is semi-trashed due to Migration Assistant
> refusing to bring MacPorts from the old MacBook to a newer Pro, so I
> stupidly(?) decided to do it by hand instead of starting from scratch;
I'm not sure what issue
On Mar 11, 2020, at 18:22, Angus Denton wrote:
> Thanks for your response. I updated Macports with the installer and for the
> hell of it I ran the selfupdate command. I got the same error, no such
> directory which I then created with a mkdir.
> Run the selfupdate again and got the no
On Mar 4, 2020, at 14:46, Ken Cunningham wrote:
> just a heads-up -- the meson build system does not handle building +universal
> very well, as we know. So far I've had to add the muniversal PortGroup to
>
> at-spi2-atk and gdk-pixbuf2
>
> to allow them to build universal, and I would not
On Mar 9, 2020, at 18:49, K Hindall wrote:
> On 3/9/20 7:01 PM, g5pw wrote:
>
>> You can use the inkscape-app port:
>>
>> $ port info inkscape-app
>> inkscape-app @0.92_1 (aqua, graphics)
>
> It looks like that port only works on macOS 10.15, and I'm on 10.13.6
What makes you say that?
It is
On Mar 10, 2020, at 13:37, dan d. wrote:
> Is it possible to install Macports using a symbolic link to an external drive
> via /opt/local?
As far as I know, we do not make any guarantees about whether that will work. I
think the topic has come up several times before over the years. It may
On Mar 9, 2020, at 14:47, ggrubb...@web.de wrote:
> I'm not sure, if I should simply wait for macports 2.6.3, or whenever the
> patches are updated
Updates to MacPorts base are infrequent. MacPorts 2.6.3, whenever we get around
to releasing that, would contain bug fixes for MacPorts base, but
On Mar 9, 2020, at 21:14, Angus Denton wrote:
> I have encountered two issues when attempting to update Macports it self
> before being able to update my ports.
> sudo self update produces an error
> error renaming
>
On Feb 24, 2020, at 08:45, joerg van den hoff wrote:
> after today's `selfupdate' and `upgrade outdated' hg errors out with
>
> abort: No module named repo!
>
> the proximal cause seems `hgsubversion'. if I avoid loading that extension in
> my .hgrc, hg is back to normal. any ideas? new ticket
On Feb 23, 2020, at 16:07, Dave Horsfall wrote:
> I tried to install "factor" (required by some other package), and got the
> following with "port upgrade outdated":
>
>---> Cleaning factor
>---> Scanning binaries for linking errors
>Warning: Error parsing file
>
On Feb 22, 2020, at 03:29, Greg Earle wrote:
> --
> Force re-install the header files:
>
> $ sudo installer -pkg
> /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg
> -target /
> --
>
> Neither my work dev system or my work desktop system (both Mojave) had
On Feb 21, 2020, at 15:59, Greg Earle wrote:
> --
> mojavemac:/ root# port install mercurial
> Warning: The macOS 10.14 SDK does not appear to be installed. Ports may not
> build correctly.
> Warning: You can install it as part of the Xcode Command Line Tools package
> by running `xcode-select
On Feb 22, 2020, at 07:43, Gerben Wierda wrote:
> On 22 Feb 2020, at 14:31, Rainer Müller wrote:
>
>> On 22.02.20 12:41, Gerben Wierda wrote:
>>> port dovecot is now installing dovecot 2
>>> port dovecot2 is now installing dovecot 1
>>
>> No, there is no Dovecot 1.x i the ports tree any more.
On Feb 17, 2020, at 13:32, Artemio González López wrote:
> After changing the sshd port from 22 to a non-standard (high) number, I’ve
> noticed that my system.log is flooded with error messages like the following,
> coming from MacPort’s rsync daemon:
>
> Feb 17 20:11:05 my-compuer-name
On Feb 15, 2020, at 00:22, Jeff Greenberg wrote:
>
>
>
> Hi. After restarting my mac, localhost is refusing connections, and
> attempting to restart apachectl results in this error message:
>
> httpd: Syntax error on line 168 of /opt/local/etc/apache2/httpd.conf: Cannot
> load
n the python
> PortGroup [1].
> My own rule has been: use the same version as the.PortGroup.
>
> [1]
> https://github.com/macports/macports-ports/blob/cc950d4f42c4bc65d8152b2465394cfef8a654b4/_resources/port1.0/group/python-1.0.tcl#L73
>
>> On Feb 5, 2020, at 11:35 AM, Ryan Sch
On Feb 13, 2020, at 08:40, Werner LEMBERG wrote:
>>> on my Lion box, calling
>>>
>>> LANG= bison ...
>>>
>>> I suddenly get *German* output! Ditto for other programs like
>>> 'info', 'ggrep', etc., that come with '.po' files. Is this normal?
>>> Is this a new gettext feature?
>
>> On a
On Feb 11, 2020, at 22:04, Dave Horsfall wrote:
>
> OK, I've finally replaced my ancient MacBook with an oldish Pro when the
> graphics card failed (can't afford anything better) and I see that only
> Sierra is recommended for it (although High Sierra may run; I'll try it once
> the dust has
On Feb 5, 2020, at 12:34, Christopher Jones wrote:
> On 5 Feb 2020, at 6:19 pm, Ryan Schmidt wrote:
>
>> On Feb 5, 2020, at 11:48, Vincent Habchi wrote:
>>
>>> this time, I have another interesting quandary. When I try to install LyX,
>>> I get this mes
On Feb 5, 2020, at 11:48, Vincent Habchi wrote:
> this time, I have another interesting quandary. When I try to install LyX, I
> get this message:
>
> —
> Air > sudo port install LyX +python38
> ---> Computing dependencies for LyX
> The following dependencies will be installed:
> […]
>
On Jan 28, 2020, at 10:20, Gerben Wierda wrote:
> When I work with a cone from my own macports-ports fork, port commands
> complain about
>
> Warning: port definitions are more than two weeks old, consider updating them
> by running 'port selfupdate'.
>
> Even if I have just reset my fork
On Jan 28, 2020, at 10:25, Gerben Wierda wrote:
> Tried this:
>
> On 28 Jan 2020, at 02:17, Ryan Schmidt wrote:
>
>> Look on this page:
>>
>> https://github.com/minio/minio/releases
>>
>> Find the release you are interested in. Usually we want
On Jan 27, 2020, at 15:09, Gerben Wierda wrote:
> What I like to know (I can of course file a ticket, but that gives me no way
> of knowing when it happens, so I prefer to do the update myself, test it and
> then produce a pull request)
>
> The Portfile contains:
>
>> # UPDATE THESE IN SYNC!
On Jan 25, 2020, at 08:34, Gerben Wierda wrote:
> How do I update the MinIo Portfile so it fetches and compiles
> RELEASE.2020-01-25T02-50-51Z?
>
> This is different from source .tar.gz downloads and such and I cannot find
> instructions on how to do this.
Not sure what you mean. The MinIO
Fixing an "ordered comparison between pointer and zero" is trivially easy,
someone just has to do it. As the ticket says, maybe the developers have
already done it; if so, we just need to update to the fixed version. If we
cannot update to the fixed version, we could backport their patch. If
On Jan 26, 2020, at 09:12, Jeff Greenberg wrote:
> On Jan 26, 2020, at 9:36 AM, Yves de Champlain wrote:
>>
>> Le 26 janv. 2020 à 08:53, Jeff Greenberg a écrit :
>>
>>> dyld: Library not loaded: /opt/local/lib/libicui18n.58.dylib
>>> Referenced from: /opt/local/bin/php
>>> Reason: image not
On Jan 21, 2020, at 17:11, Artemio González López wrote:
> Bitdefender has flagged two files from the db48 MacPorts port installed in my
> Mac, namely
>
> /opt/local/lib/db48/libdb_cxx-4.8.dylib
> /opt/local/var/macports/software/db48/db48-4.8.30_4.darwin_17.x86_64.tbz2
On Jan 21, 2020, at 03:54, Chris Jones wrote:
> On 21/01/2020 1:28 am, Dave Horsfall wrote:
>
>> I don't have web access right now, hence the list...
>> My ancient Sierra MacBook failed (graphics board which is no longer
>> available) but I have been offered a more recent second-hand one for
On Jan 19, 2020, at 17:47, Dave Allured wrote:
> Is there an easy way to get macports to go through the motions of "port
> install -s" for a single port, using macports infrastructure, and taking port
> dependencies from /opt/local, but writing only inside a user directory? This
> would
On Jan 18, 2020, at 17:20, Uli Wienands wrote:
> This is on OS-X 10.6.8, Macports 2.6.1.
Please "sudo port selfupdate" to get MacPorts 2.6.2.
> I am trying to get py37-numpy installed. One dependency is OpenBLAS which
> fails to build. It looks like I am running into the same error Ken
On Jan 14, 2020, at 15:42, Raphael Cohn wrote:
> When I uninstall the ports the archives are still present in
> var/macports/software.
Hmm. You've modified MacPorts base so that it does not delete the archives upon
uninstallation?
> An overlay is an archive that can be extracted over an
On Jan 14, 2020, at 14:43, Raphael Cohn wrote:
> What I'd like to do is run my own local archive in my own machine without
> running a webserver.
>
> I'd like to compile my ports from source and install them. I'd like to
> uninstall them. The next time I install I'd like to use the
On Jan 14, 2020, at 03:52, Raphael Cohn wrote:
> I'm trying to get macports to use a local (file://) repository for a macports
> installed in a non-standard prefix (in this case, a project local macports,
> ie per user, per project) with a mixture of private and public port files. I
> want
On Jan 14, 2020, at 03:35, joerg van den hoff wrote:
> 1.
> would you consider to alter the naming/description of the current `ksh'
> package to reflect that it is actually _not_ ksh93 any more (in terms of
> stability, performance etc)?
I already did change the name of the port from ksh93 to
On Jan 13, 2020, at 03:52, joerg van den hoff wrote:
> hi there,
>
> not that long ago I asked for updating the ksh package and ryan thankfully
> did that and interacted a bit with the ast/ksh project ("ksh2020") at github
> in the process.
>
> in the intervening months I had to learn,
On Nov 23, 2019, at 12:17, Ryan Schmidt wrote:
> On Nov 23, 2019, at 04:02, Richard L. Hamilton wrote:
>
>> from a 15" 2017 MacBook Pro:
>>
>> sh-3.2$ sudo arping echo-dot-lr
>> arping: libnet_init(LIBNET_LINK, ):
>> sh-3.2$ sudo arping cra
On Jan 11, 2020, at 12:32, Steven Smith wrote:
> First, as Gerben points out, macOS‘s postfix launch daemon is in
> /System/Library, so you’d have to disable SIP to unload it, which at best is
> a major PITA, and realistically a non-option.
Are you certain? Certainly modifying anything in
On Jan 10, 2020, at 11:37, Gerben Wierda wrote:
> Given that postfix writes a pid file in
> /opt/local/var/spool/postfix/pid/master.pid would it be possible to use a
> startupitem.pidfile entry that triggers daemondo to try to relaunch when this
> happens?
That seems reasonable. I filed:
On Jan 10, 2020, at 03:34, Gerben Wierda wrote:
> If I produce a pull request and I’m rebuffed because of an error I make, I
> need to go back to testate of the official repository before proceeding again.
I think you should reexamine how you are using git, because "reset" is not a
git
> On 09/01/2020 1:50 pm, joerg van den hoff wrote:
>> I had to upgrade to 10.15 (wanted to postpone this further but ...) and
>> recall that there were many reports over the last months of problems with
>> subsequent macports upgrade, recommendations to use previous xcode releases
>> with
On Jan 1, 2020, at 21:38, Uli Wienands wrote:
> The log indicates that you do not have cmake installed, which is used to
> generate the Makefile during the configuration phase. You should be able to
> install that from MacPorts. Here is the error msg. that shows this:
>
> :info:configure
On Dec 31, 2019, at 09:37, Daniel J. Luke wrote:
> On Dec 31, 2019, at 10:34 AM, Ken Cunningham wrote:
>> On 2019-12-31, at 7:26 AM, Daniel J. Luke wrote:
Except that would get the rdeps of openal-soft with its default variants,
rather than with the +gui and +tests variants.
On Dec 30, 2019, at 21:31, Daniel J. Luke wrote:
> On Dec 30, 2019, at 4:41 PM, Ken Cunningham wrote:
>
>> So — I guess there is no way around this automatically?
Not that I'm aware of.
> you could probably do something like port install rdepof:openal-soft && port
> install openal-soft
On Dec 22, 2019, at 15:41, Michael Newman wrote:
> On Dec 22, 2019, at 22:04, Ryan Schmidt wrote:
>
>> Since reclaim prints a list of the ports it will remove, it seems like it's
>> up to you to verify that there isn't anything on the list that you want to
>>
On Dec 22, 2019, at 04:13, Michael Newman wrote:
> When I got up this morning I found that a couple of scripts that I run
> overnight had failed with error 127. It seems that the scripts couldn’t find
> curl. So I checked, and sure enough, curl was missing. No worries, I can
> reinstall it.
On Dec 20, 2019, at 22:25, Bill Cole wrote:
> This by itself may fix your problewm:
>
> rm /usr/local/bin/lynx
And more generally, remove anything you have in /usr/local.
https://trac.macports.org/wiki/FAQ#usrlocal
On Dec 8, 2019, at 18:32, Werner LEMBERG wrote:
>
> On my Mac Lion box running an up-to-date MacPorts, for experimentation
> reasons I try to build the current git version of lilypond directly
> from the repository – this is, I use the MacPorts infrastructure for
> compilation with a recent clang
On Nov 29, 2019, at 20:14, yiming roberts-lo wrote:
> I went to install Inkscape and got the following message:
>
> py27-cython has the following notes:
> To make the Python 2.7 version of Cython the one that is run when you
> execute the commands without a version suffix, e.g.
On Nov 29, 2019, at 10:01, Dave Allured wrote:
> I have the longer user home prefix because my institutional network policy
> prevents all write access to /opt/anything.
I still think the suggestion I made in
https://trac.macports.org/ticket/59510#comment:2 is worth a try. If you can't
put
Please remember to write to our new mailing list addresses at
lists.macports.org, not the old address you used which was deprecated at the
end of 2016.
The error in the log you attached is:
:info:build dyld: Library not loaded: /opt/local/lib/libcrypto.1.0.0.dylib
:info:build Referenced
On Nov 28, 2019, at 06:23, joerg van den hoff wrote:
> On 28.11.19 12:44 , Ryan Schmidt wrote:
>> On Nov 28, 2019, at 04:48, joerg van den hoff wrote:
>>> I ran `port upgrade outdated' today. after end of sucessfull completion
>>>
>>> `port outdated' st
On Nov 27, 2019, at 14:50, Dave Allured - NOAA Affiliate wrote:
> I am trying to solve "Argument list too long" when building gdal@3.0.1_3 from
> source under macports. The command that fails is "libtool clang++", used
> here to combine a large number of objects into a single library
On Nov 28, 2019, at 04:48, joerg van den hoff wrote:
> I ran `port upgrade outdated' today. after end of sucessfull completion
>
> `port outdated' still reported
>
>ghostscript9.27_1 < 9.50_0
>
>
> rerunning the `upgrade' did not change anything. on further
On Nov 20, 2019, at 14:55, Ken Cunningham wrote:
> On 2019-11-20, at 12:48 PM, Ryan Schmidt wrote:
>
>> There were also a fair number of issues caused by ports that do not properly
>> propagate the -stdlib flag to the build system.
>>
>
> Ah -- I had hoped to
There were also a fair number of issues caused by ports that do not properly
propagate the -stdlib flag to the build system.
On Nov 18, 2019, at 15:36, Ces VLC wrote:
> Just issued a "sudo port install mingw-w64" on 10.6.8. Most needed
> dependencies are downloaded prebuilt, except for gcc 9.2.0, which needs to be
> built from source.
It is interesting that you were able to build i686-w64-mingw32-gcc-bootstrap
On Nov 16, 2019, at 06:49, joerg van den hoff wrote:
> thanks a lot for all these clarifications. I really was not aware that
> package update is so dependent on manual intervention the macports package
> maintainers. which makes your work even more impressive.
>
> and I am completely aware
On Nov 9, 2019, at 19:49, Al Varnell wrote:
> On Nov 9, 2019, at 08:45, Ryan Schmidt wrote:
>>>> Have you tried installing the CLT ? That should provide a 10.14 SDK that
>>>> the latest MacPorts release will use.
>>>
>>> I thought CLT was install
On Nov 9, 2019, at 11:04, Werner LEMBERG wrote:
> I've installed perl's `PAR` module, needed for TeXLive's (self-compiled)
> `biber` binary, with
>
> sudo cpan-5.26 install PAR
>
> on my up-to-date Lion box (using MacPorts from git). However,
> executing `biber --help` fails with
>
>
On Nov 9, 2019, at 08:48, Hans Goedbloed wrote:
>
> (Since there are numerous complaints on Xcode 11.2 and Catalina, I downloaded
> Xcode 10.0.)
It's true that using Xcode 11.x on Mojave with MacPorts can be problematic
right now and we recommend using Xcode 10.x on Mojave. But you should use
On Nov 9, 2019, at 10:35, Henning Hraban Ramm wrote:
> Am 2019-11-09 um 15:07 schrieb Chris Jones:
>
>> On 9 Nov 2019, at 1:50 pm, Henning Hraban Ramm wrote:
>>
>>> Since I didn’t find a way to install a 10.14 SDK, I just made a symlink to
>>> the 10.15 SDK under the name of MacOSX10.14.sdk,
On Nov 8, 2019, at 20:31, Chris Jones wrote:
> On 9 Nov 2019, at 1:39 am, Ryan Schmidt wrote:
>
>> If you ran `sudo port install clamav`, and it was not already installed,
>> MacPorts should have marked it as requested. If clamav was automatically
>> installed as a
On Nov 8, 2019, at 16:06, Michael Newman wrote:
> On Nov 7, 2019, at 06:34, Ryan Schmidt wrote:
>
>> If `port installed requested` shows things that you don't actually want,
>> tell MacPorts by marking them as not requested:
>>
>> sudo port unse
On Nov 6, 2019, at 05:54, joerg van den hoff wrote:
> On 05.11.19 20:41 , Ryan Schmidt wrote:
>> On Nov 5, 2019, at 10:20, joerg van den hoff wrote:
>>> this is on OSX 10.14.6 and with current macports 2.6.2.
>>>
>>> it does not find it
On Nov 8, 2019, at 02:36, Werner LEMBERG wrote:
> On Mac Lion, installing a fresh MacPorts from scratch, then calling
>
> port -N mpkg lilypond-devel +mactex +perl5_28 +python37
>
> always causes a (harmless) abort. The reason is that
> `libunwind-headers' gets installed as part of the
> On Nov 8, 2019, at 02:39, Werner LEMBERG wrote:
>
>>> I've noticed that in `main.log` files there is no information what
>>> version and variants have been requested – for example,
>>>
>>> ImageMagick @6.9.9-40_7+x11
>>>
>>> Wouldn't it make sense to make `port` add this information to the
On Nov 7, 2019, at 21:23, Stan Sanderson wrote:
> OS X 10.14, all installed ports up-to-date.
> Re: kmymoney4-devel
>
> Since the recent problem with kdepimlibs4 was solved (thanks!), port upgrade
> outdated consistently ends with
> ---> Scanning binaries for linking errors
> ---> Found 2
On Nov 7, 2019, at 09:42, posita wrote:
> I have been wracking my brains trying to understand this, but have come up
> short.
>
> Every time I do a `sudo port -c -u selfupdate`, many files in
> `/var/macports/sources/rsync.macports.org/macports/release/tarballs`
> end up with GID 505.
On Nov 6, 2019, at 02:34, Michael Newman wrote:
> I have no idea why I have postgreSQL:
>
> MrMuscle:~ mnewman$ sudo port dependents postgresql84
> postgresql84-server depends on postgresql84
> MrMuscle:~ mnewman$ sudo port dependents postgresql84-server
> postgresql84-server has no
On Nov 5, 2019, at 19:10, raf wrote:
> I only tried "port clean ncurses" like it suggested but that didn't help.
> Then I remembered that I had an environment variable:
>
> ARCHFLAGS='-arch i386 -arch x86_64'
>
> Which probably stopped it working. I got rid of that, and port cleaned
>
On Nov 5, 2019, at 19:39, Michael Newman wrote:
> Maybe I’m just not smart enough to play with MacPorts….
Normally things work pretty well. Sometimes you'll encounter errors.
Unfortunately we'll have to deal with them on a case by case basis!
> This on an iMac still running Mojave.
>
>
Please write to our list addresses at lists.macports.org, not the old hostname
you used which was deprecated in 2016.
On Nov 5, 2019, at 10:20, joerg van den hoff wrote:
> this is on OSX 10.14.6 and with current macports 2.6.2.
>
> it does not find it seems. I don't find anything related to
On Nov 4, 2019, at 14:25, Michael A. Leonetti wrote:
> My qt5 installation keeps complaining about missing linking files so I am
> trying to reinstall and qt5-q3d complains about missing system-assimp.
>
> Is there a variant I'm missing that I can disable?
>
>> :debug:configure
>>
On Nov 4, 2019, at 10:12, Hans Goedbloed wrote:
> [/Users/hansgoedbloed]$sudo port install gcc9
> Password:
> ---> Computing dependencies for gcc9
> ---> Cleaning gcc9
First things first: this shows that gcc9 was already successfully installed
before you ran this command.
> ---> Updating
On Nov 3, 2019, at 04:19, Michael Newman wrote:
> Locate did not find this plist on the boot volume. It did find it in a Carbon
> Copy Cloner SafetyNet directory on a backup drive.
>
> MrMuscle:home mnewman$ locate org.macports.postgresql83-server.plist
> /Volumes/Clorox2/_CCC
On Nov 3, 2019, at 02:10, Michael Newman wrote:
> Periodically DetectX generates the following message:
>
> =
> Items: org.macports.postgresql83-server.plist
> Some background launch items have just been changed on your mac which can
> affect its security
> =
>
> I had previously
On Nov 2, 2019, at 01:31, raf wrote:
> at first, i changed my macports.conf to put i386 back into the universal_archs
> variable but later found out that xcode (i guess) no longer supports compiling
> for i386 so i changed it back to the default.
>
> restore_ports.tcl had trouble processing
On Oct 28, 2019, at 22:28, Al Varnell wrote:
> Maybe I’m missing something obvious here, but why isn’t the list configured
> IAW RFC 2369 instead?
What specifically are you proposing we change?
On Oct 12, 2019, at 12:14, Andrew Hartung wrote:
> On Oct 12, 2019, at 10:10 AM, Ryan Schmidt wrote:
>> Clang 11 goes with Xcode 11 but you said you have Xcode 10. You should
>> either upgrade to Xcode 11 to match your clang version (I don't recommend
>> this due to th
On Oct 12, 2019, at 21:50, Al Varnell wrote:
> I feel certain that could be configured to be the default setting for this
> list. It is the only one of over a dozen that I subscribe to where it’s not.
>
> Could that be checked into?
No. Munging the Reply-To header would contravene the
On Oct 26, 2019, at 18:28, Darwin O'Connor wrote:
> I'm trying to install p5.26-dbd-mysql which is needed to update mythtv.28,
> which needs to use mariadb.
>
> It is generating this error:
>
> :info:configure 'perldoc DBD::mysql::INSTALL'.
> :info:configure Checking if libs are available
On Oct 22, 2019, at 10:30, Christoph Kukulies wrote:
> My macOS wants to update (Mojave->Catalina 10.15).
>
> I’ve heard wine emulator based programs will cease working.
>
> Has anyone heard there will be an escape for this situation?
This is the latest information I have:
On Oct 22, 2019, at 12:38, Riccardo Mottola wrote:
> my MacPorts
> broke in a very strange way. I was upgrading selectively some ports (because
> certain are hard failures currently on 10.7) ehen upgrade of python36 broke
> (strangely, it worked on 10.6!).
>
> I cannot even list outdated
Remember to Reply All so the conversation stays on the list.
On Oct 22, 2019, at 02:39, Michael Newman wrote:
> On Oct 22, 2019, at 13:51, Ryan Schmidt wrote:
>
>> Ok, so there were two versions of postgresql83 installed. You told MacPorts
>> to uninstall them both,
On Oct 22, 2019, at 01:48, Michael Newman wrote:
>> PostgreSQL is a database server. If you don't think you need it (or any
>> port), try uninstalling it. ("sudo port uninstall postgresql83"). MacPorts
>> will either let you uninstall it, or it will tell that uninstalling it will
>> break
On Oct 22, 2019, at 00:50, Michael Newman wrote:
>> On Oct 22, 2019, at 12:26, Wahlstedt Jyrki wrote:
>>
>>> Michael Newman kirjoitti 22.10.2019 kello 7.19:
>>>
>>> I have no idea. I don’t even know what it is. It must have been installed
>>> by some other port that I requested.
>>
>> Hi,
On Oct 20, 2019, at 17:41, Al Varnell wrote:
> I got 2.6.1 just now. Guess I need to wait for all the mirrors to be fully
> updated and try again later.
You can safely run `sudo port selfupdate` anytime. If the mirror you're using
has already received the 2.6.2 update, you'll get it. If
On Oct 20, 2019, at 19:42, Christopher Burns wrote:
> It may be coming, but I was trying to install osxfuse on 10.15, and it is
> failing. When I dig into the logs it appears it just doesn’t have the 10.15
> SDK in the /lib/defaults.sh - so if I add
> DEFAULT_SDK_10_15_ARCHITECURES/COMPILE
On Oct 15, 2019, at 12:36, Chris Jones wrote:
> On 15 Oct 2019, at 8:43 am, Guillaume Houzeaux @ BSC wrote:
>
>> there is no way I can update to xcode11.1 (I always get an error from apple
>> store at the end: could not be installed).
>
> Thats very fishy definitely you should be
On Oct 12, 2019, at 12:30, Andrew Hartung wrote:
> I found the problem. Somehow xcode got updated to 11 automatically two days
> ago. I just upgraded to Mojave a couple of weeks ago and missed a setting in
> the app store to turn off automatic upgrades. Downgrading now, sorry to waste
>
Remember to Reply All so the conversation stays on the list.
On Oct 11, 2019, at 23:11, Andrew Hartung wrote:
> On Oct 11, 2019, at 9:39 PM, Ryan Schmidt wrote:
>> On Oct 10, 2019, at 22:58, Andrew Hartung wrote:
>>
>>>
>>> Warning: All compilers are
On Oct 12, 2019, at 03:36, Chris Jones wrote:
> On 12 Oct 2019, at 3:28 am, Ryan Schmidt wrote:
>
>> On Oct 11, 2019, at 09:57, Joshua Root wrote:
>>
>>> Xcode itself only contains a 10.15 SDK, but the Command Line Tools have
>>> a 10.14 one. You shoul
On Oct 11, 2019, at 21:39, Steven Esser wrote:
> The bsdtar command seems to work fine outside of the scripts. This is a fresh
> installation of Catalina and MacPorts, so there are extraneous installs of
> bsdtar or libarchive etc
I assume you are the only person experiencing this problem,
On Oct 10, 2019, at 22:58, Andrew Hartung wrote:
> What does this mean?
>
> Warning: All compilers are either blacklisted or unavailable; defaulting to
> first fallback option
>
> 10.14.6 with xcode 10.
>
> Showed up after the latest port update I ran after here:
>
> Adding subport
On Oct 11, 2019, at 09:57, Joshua Root wrote:
> Xcode itself only contains a 10.15 SDK, but the Command Line Tools have
> a 10.14 one. You should be mostly fine with them installed, though there
> are some exceptions. Our installation instructions have always said to
> install both Xcode and the
On Oct 11, 2019, at 10:49, Steven Esser wrote:
> On a fresh Catalina (10.15) install with Xcode 11.1 and the latest CLI tools
> I cannot seem to activate any ports. Most seem to configure and build
> correctly, but fail when they reach the activation step. Attached is the log
> for an
701 - 800 of 1456 matches
Mail list logo
