Re: Problems with not finding Framework header files on Mojave 10.14.6

Greg Earle wrote: > I have Xcode 10.3 installed on it (to ensure it installed the 10.14.6 > SDK). Xcode 11 should also be OK as long as you have the Command Line Tools installed, which will provide the 10.14 SDK. > Warning: The macOS 10.14 SDK does not appear to be installed. Ports may > not bu

Re: Problems with not finding Framework header files on Mojave 10.14.6

On 22 Feb 2020, at 0:46, Joshua Root wrote: Greg Earle wrote: I have Xcode 10.3 installed on it (to ensure it installed the 10.14.6 SDK). Xcode 11 should also be OK as long as you have the Command Line Tools installed, which will provide the 10.14 SDK. Warning: The macOS 10.14 SDK does not

Dovecot port changes

port dovecot is now installing dovecot 2 port dovecot2 is now installing dovecot 1 The change breaks ‘port update outdated’ as the existence of a dovecot2 install will prevent the installation of dovecot which now has become a dependency for other ports instead of dovecot2. dovecot2-sive is like

Why are my por definitions still out of date after this?

I have my own fork of the macports-ports repository on GitHub so I can do maintenance. I have a local clone of that fork When I want to update ports I do not maintain, do the following. First I make sure my clone is up to date with the upstream original, then I push the clone back to my GitHub

Re: Dovecot port changes

Follow-up suggestion: Clone port dovecot2 to a new port dovecot1 now Whenever dovecot major release 3 appears: Clone the existing dovecot to new port dovecot2 Update dovecot port to dovecot 3 Is there a mechanism in MacPorts to block automatic update activations when new versions of software r

Re: Why are my por definitions still out of date after this?

Have you told macports to use your git clone ? i.e. > cat /opt/local/etc/macports/sources.conf #rsync://rsync.macports.org/macports/release/tarballs/ports.tar [default] file:///Users/chris/Projects/MacPorts/ports [default] where for me /Users/chris/Projects/MacPorts/ports is my local git clon

catalena

Hi All After 6 years my macbook battery is really past it’s use-by. The keyboard has become a sea of won’t-push-this-week-and-hard-to-get-a-keypush so I decided to get a new laptop, but of course it comes with catalena. I’ve been using high sierra and all my ports are good. Is catalena now stable

Re: Dovecot port changes

Just do: port uninstall dovecot2 dovecot2-sieve port clean --all dovecot2 dovecot2-sieve port install dovecot +solr +… port install dovecot-sieve A strong downvote to anything named “dovecot3” when and if version 3 ever appears. At that time dovecot version 2 will be obsolete, which is how we go

Re: Dovecot port changes

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. dovecot2 is a port that has been marked as replaced_by dovecot. As the epoch was increased, it will be considered m

Re: Why are my por definitions still out of date after this?

> On 22 Feb 2020, at 13:32, Christopher Jones wrote: > > Have you told macports to use your git clone ? > > i.e. > > > cat /opt/local/etc/macports/sources.conf > > #rsync://rsync.macports.org/macports/release/tarballs/ports.tar > [default] > file:///Users/chris/Projects/MacPorts/ports >

Re: catalena

Generally speaking mac OS 10.15 works just as well as any other, and as with other OSes there are some known issues. Like 32 bit support (not possible on 10.15). Only you know which ports you use, and without this it is impossible to be any more specific. note though, if you new machine was rel

Re: Dovecot port changes

> 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. > > dovecot2 is a port that has been marked as repla

Re: Why are my por definitions still out of date after this?

> On 22 Feb 2020, at 1:39 pm, Gerben Wierda wrote: > > > >> On 22 Feb 2020, at 13:32, Christopher Jones > > wrote: >> >> Have you told macports to use your git clone ? >> >> i.e. >> >> > cat /opt/local/etc/macports/sources.conf >> >> #rsync://rsync.macpo

Re: Why are my por definitions still out of date after this?

> On 22 Feb 2020, at 14:43, Christopher Jones wrote: > > > >> On 22 Feb 2020, at 1:39 pm, Gerben Wierda > > wrote: >> >> >> >>> On 22 Feb 2020, at 13:32, Christopher Jones >> > wrote: >>> >>> Have you told macports to use your

Re: Dovecot port changes

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. >>

Re: Problems with not finding Framework header files on Mojave 10.14.6

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 -

Re: Problems with not finding Framework header files on Mojave 10.14.6

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 t