[resent because the list address in CC was wrong]
On 19/06/2021 17.02, Ken Cunningham wrote:
> I don't subscribe to any of MacPorts' email lists, or any others.
>
> So any comments come in new. Didn't realize that was troubling anyone,
> but thank for letting me know it is.
If you are not
On Jun 19, 2021, at 05:12, Christopher Jones wrote:
> Hi,
>
> I’ve been noticing recently a number of ports are failing to live check, with
> errors like
>
>> port -d live libogg
> DEBUG: Changing to port directory:
>
Please write to list addresses at lists.macports.org, not the old addresses at
the other hostname that were deprecated at the end of 2016. Some users' email
server setups have such restrictive security settings that they are not able to
read the emails if they are forwarded from the old address
Hi Ken,
To get specific/technical, if you view the raw source for the first mail I sent
in this tread, you will see it has in its headers
Message-Id:
thats the unique identifier for that mail.
Then, if you look at Joshua’s reply, it has
References:
Message-ID:
Its that Reference line
I don't subscribe to any of MacPorts' email lists, or any others.
So any comments come in new. Didn't realize that was troubling anyone, but
thank for letting me know it is.
K
On Saturday, June 19, 2021, Chris Jones wrote:
> Hi Ken,
>
> OT, but whenever you reply to a thread on these lists
Hi Ken,
OT, but whenever you reply to a thread on these lists your emailer always seems
to screw up the headers such that your reply starts a new thread. We get the
messages but it makes following the discussion harder. I don’t know what
emailer you use, but maybe you could look into it ?
Hey, maybe we will finally start bundling curl (there is a years-old ticket
about this, and someone already laid out the autotools changes to do it).
I have been building MacPorts against a custom libcurl on most systems
10.10 and older for years and years.
It's trivially simple to do, but to
port is built against system libcurl.
I actually ran into that yesterday while compiling MacPorts under FreeBSD
(unfortunately, the tcl build throws a core with a signal 11 when doing
portindex).
Marius
__
Marius Schamschula
On Jun 19, 2021, 8:12 AM -0500, Christopher Jones ,
wrote:
>
>
> >
> On 19 Jun 2021, at 1:35 pm, Joshua Root wrote:
>
> On 2021-6-19 20:12 , Christopher Jones wrote:
>> A quick web search suggests this could be an issue with an older version of
>> (lib)curl being used ? Does anyone have any insights into this ?
>
> Certainly seems OK with the MacPorts
On 2021-6-19 20:12 , Christopher Jones wrote:
A quick web search suggests this could be an issue with an older version of
(lib)curl being used ? Does anyone have any insights into this ?
Certainly seems OK with the MacPorts version but not the system version.
I don't know any specifics, but
10 matches
Mail list logo
