Hi,
Speaking only for myself, I generally suggest *not* using the
restore_ports.tcl script. When I migrate to a new OS I generate the list
of installed ports *and* requested ones, and follow the instructions as
far as wi[ping out my old ports prior to the update.
However, when restoring the
I tried the latest build again. Although there are some things that it baulks
at, it seems to be doing the main things that I require – essentially, keeping
track of crypto purchases.
I’ll hope for the best and press on.
Thanks.
—
Peter West
p...@ehealth.id.au
…the whole multitude of his disci
I switched from using the macOS-supplied curl to MacPorts curl recently, and
one of my download scripts which uses curl immediately stopped working. The
error message from curl was:
curl: (35) error:0A000152:SSL routines::unsafe legacy renegotiation disabled
From some googling it sounds like t
Hi,
On Tue, Apr 12, 2022 at 09:17:03AM -0700, James Secan wrote:
> I switched from using the macOS-supplied curl to MacPorts curl
> recently, and one of my download scripts which uses curl immediately
> stopped working. The error message from curl was:
>
> curl: (35) error:0A000152:SSL routines:
It’s a US Gov’t site (NASA): cddis.nasa.gov. I’m accessing data on their Space
Geodesy Data archive, pulling files from directory archive/gnss/products/ionex.
I filed an initial complaint with them yesterday before I knew in detail what
was going on and had a response asking for more info this
On Apr 11, 2022, at 21:10, Jim DeLaHunt wrote:
> Might the presence of "archs='x86_64'" cause the restore_ports.tcl script to
> ask for +universal variants on the new computer?
>
> Should I perhaps null out the value "x86_64" from the archs entries in my
> installed ports list? i.e. turn
On Apr 11, 2022, at 17:02, Dave Horsfall wrote:
> On Mon, 11 Apr 2022, Ryan Schmidt wrote:
>
>> Run "sudo port selfupdate" to get the most recent ports.tar. Do you
>> still see the problem then?
>
> I did run that first; apologies for not mentioning it (there were no
> issues).
I think you di
On Tue, 12 Apr 2022, Ryan Schmidt wrote:
> > I did run that first; apologies for not mentioning it (there were no
> > issues).
>
> I think you did mention it. I was suggesting you run it again, in case
> somehow the server files were in a weird state the last time you
> selfupdated. There was
On 2022-04-13 at 00:34:02 UTC-0400 (Tue, 12 Apr 2022 23:34:02 -0500)
Ryan Schmidt
is rumored to have said:
> On Apr 11, 2022, at 17:02, Dave Horsfall wrote:
>
>> On Mon, 11 Apr 2022, Ryan Schmidt wrote:
>>
>>> Run "sudo port selfupdate" to get the most recent ports.tar. Do you
>>> still see the p
Bill Cole wrote:
Theory: it's a problem related to running the reclaim from the prompt at the
tail end of a selfupdate. Incomplete 'portindex' run perhaps?
Good theory. It's likely that when the periodic reclaim run at exit was
added, it wasn't considered that it might be running after code
10 matches
Mail list logo
