On Sep 24, 2018, at 19:02, Eitan Adler wrote:
> On Mon, 24 Sep 2018 at 16:58, Ryan Schmidt wrote:
>>> Nothing seemed to go wrong, but it is noisy and might spark additional
>>> questions. This email is mostly an FYI.
>>
>> Just to make sure: your complaint is that the rsync server's
>> message-o
> On 25 Sep 2018, at 12:58 am, Ryan Schmidt wrote:
>
>
>
>> On Sep 24, 2018, at 18:54, Eitan Adler wrote:
>>
>> When i ran "sudo port selfupdate" for the first time on a new (from
>> source) install I see this
>>
>> ---
>> ∴sudo port -v selfupdate
>> Password:
>> ---> Updating MacPorts ba
On Mon, 24 Sep 2018 at 16:58, Ryan Schmidt wrote:
> > Nothing seemed to go wrong, but it is noisy and might spark additional
> > questions. This email is mostly an FYI.
>
> Just to make sure: your complaint is that the rsync server's
> message-of-the-day is printed in the output? We could suppres
On Sep 24, 2018, at 18:54, Eitan Adler wrote:
> When i ran "sudo port selfupdate" for the first time on a new (from
> source) install I see this
>
> ---
> ∴sudo port -v selfupdate
> Password:
> ---> Updating MacPorts base sources using rsync
>
> Willkommen auf dem RSYNC-server auf ftp.fau.de
When i ran "sudo port selfupdate" for the first time on a new (from
source) install I see this
---
∴sudo port -v selfupdate
Password:
---> Updating MacPorts base sources using rsync
Willkommen auf dem RSYNC-server auf ftp.fau.de.
Nicht all unsere Mirror sind per rsync verfuegbar.
Welcome to the
On Sep 24, 2018, at 11:06, Frank Schima wrote:
> On Sep 24, 2018, at 1:48 AM, Joshua Root wrote:
>
>> Currently, portconfigure::configure_get_sdkroot will return an error if
>> there is no SDK for the current OS version, and /usr/include also is not
>> present [1]. A recent change stopped warn
Hi Josh,
> On Sep 24, 2018, at 1:48 AM, Joshua Root wrote:
>
> Currently, portconfigure::configure_get_sdkroot will return an error if
> there is no SDK for the current OS version, and /usr/include also is not
> present [1]. A recent change stopped warning about the lack of
> /usr/include when u
Hi Ryan,
> On Sep 24, 2018, at 2:22 AM, Ryan Schmidt wrote:
>
> The release of macOS Mojave is imminent and I want to make sure we do the
> right thing for the first release of MacPorts on Mojave. Let me know if you
> have any thoughts about the below.
>
> Ideally I would like to keep the ab
On Sun, Sep 23, 2018 at 12:17:50AM +, MacPorts wrote:
> Is this still an issue (a few versions have been updated in the
> meantime)? If yes, it might be nice to ask upstream.
We've long since snipped it from production. Apologies for not having
updated the ticket to say so.
--
Dr Martin
The release of macOS Mojave is imminent and I want to make sure we do the right
thing for the first release of MacPorts on Mojave. Let me know if you have any
thoughts about the below.
Ideally I would like to keep the ability to build 32-bit ports in MacPorts on
Mojave, mainly because I don't w
Currently, portconfigure::configure_get_sdkroot will return an error if
there is no SDK for the current OS version, and /usr/include also is not
present [1]. A recent change stopped warning about the lack of
/usr/include when using recent Xcode versions [2].
This leaves us in a situation where a u
11 matches
Mail list logo