> On 10 Dec 2021, at 8:07 pm, SeaQuench wrote:
>
> Output of selfupdate as requested:
>
> $ sudo port selfupdate
> ---> Updating MacPorts base sources using rsync
> Error: Error synchronizing MacPorts sources: command execution failed
> Please run `port -v selfupdate' for details.
> Error:
Output of selfupdate as requested:
$ sudo port selfupdate
---> Updating MacPorts base sources using rsync
Error: Error synchronizing MacPorts sources: command execution failed
Please run `port -v selfupdate' for details.
Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing
Hi,
Yes, the error is expected. What i am asking is if you get any indication or
not that there was an issue when you run without the verbose flag. If not, then
i think thats a bug we should address.
Chris
> On 10 Dec 2021, at 7:18 pm, SeaQuench wrote:
>
> I am behind a firewall, so this
I am behind a firewall, so this is the following is predictable:
$ sudo port -v selfupdate
---> Updating MacPorts base sources using rsync
rsync: failed to connect to rsync.macports.org: Operation timed out (60)
rsync error: error in socket IO (code 10) at
Just to be clear, are you saying running
> sudo port selfupdate
ran without warnings or error, but did not actually update ? If thats the case
we should file a bug against base as if the rsync fails it should indicate this
to the user ?
cheers Chris
> On 10 Dec 2021, at 3:13 pm, SeaQuench
Ryan is correct; I had been sync'ing my port index successfully, but MacPorts
itself grew stale due to my being unable to run selfupdate. The MacPorts
Migration Guide suggested a manual update (i.e. reinstall) which I believe got
me going again. Thanks guys! ~SeaQuench
‐‐‐ Original Message
On Dec 10, 2021, at 02:29, Chris Jones wrote:
>
> On 9 Dec 2021, at 10:49 pm, SeaQuench wrote:
>>
>>
>> After downloading and installing the latest MacPorts for Catalina, I
>> followed the instructions to migrate MacPorts:
>> https://trac.macports.org/wiki/Migration
>> Reinstalling the ports
Hi,
Please always remember to reply to the list.
We need to see why you are not finding the openssl3 port, as that has been
available for some time.
Please run
sudo port -d sync
And post what you get back to the list
Chris
> On 9 Dec 2021, at 10:49 pm, SeaQuench wrote:
>
>
> After
SeaQuench wrote:
After applying an update to MacOS last August, the python ports are reporting a
dependency on either openssl11 or openssl3, neither of which are to be found in
the (local?) index for MacPorts, according to the error I have received, copied
below. While I am prompted to
Did you follow the migration guide when moving to a new major os version ?
https://trac.macports.org/wiki/Migration
If not, follow it now, to wipe out your ports and reinstall them correctly for
the new os.
If you did, your ports tree seems to be very out of date. Then try,
> sudo port
After applying an update to MacOS last August, the python ports are reporting a
dependency on either openssl11 or openssl3, neither of which are to be found in
the (local?) index for MacPorts, according to the error I have received, copied
below. While I am prompted to report a bug, I presume I
11 matches
Mail list logo