RE: I just wanted to upgrade my older MacPorts version

[Martin Martinez Ripoll]

Thanks a lot for your kind help!

_
Dr. Martin Martinez-Ripoll
Research Professor Emeritus
martin.m.rip...@csic.es
xmar...@iqf.csic.es
Department of Crystallography & Structural Biology
www.xtal.iqf.csic.es
www.xtal.iqf.csic.es/Cristalografia/ 
Telf.: +34 917459550
Consejo Superior de Investigaciones Científicas
Spanish National Research Council


-Mensaje original-
De: macports-users [mailto:macports-users-boun...@lists.macports.org] En
nombre de Ryan Schmidt
Enviado el: lunes, 11 de marzo de 2024 12:05
Para: Riccardo Mottola 
CC: macports-users@lists.macports.org
Asunto: Re: I just wanted to upgrade my older MacPorts version

On Mar 10, 2024, at 05:48, Riccardo Mottola wrote:
> 
> I suppose that since you got the repository in git, you just need to do a
"git pull" to upgrade it and subsequently "sudo port -v sync".

You don't need to run "git pull" manually. "sudo port sync" runs it for you.

Re: I just wanted to upgrade my older MacPorts version

[Ryan Schmidt]

On Mar 10, 2024, at 05:48, Riccardo Mottola wrote:
> 
> I suppose that since you got the repository in git, you just need to do a 
> "git pull" to upgrade it and subsequently "sudo port -v sync".

You don't need to run "git pull" manually. "sudo port sync" runs it for you. 

Re: I just wanted to upgrade my older MacPorts version

[Ryan Schmidt]

On Mar 8, 2024, at 06:58, xmartin wrote:
> 
> In fact, the the problem seems to be the restrictive corporate network. I was 
> able to run what is said in:
> https://trac.macports.org/wiki/howto/SyncingWithGit

Ok great. 


> The “sudo port upgrade outdated” is running, but the question know is, how 
> can I run in the future the equivalent to the older “sudo port selfupdate”?

Hopefully someday selfupdate can work over https:

https://github.com/macports/macports-base/pull/184

Unfortunately for now it only operates over rsync, so if you cannot use rsync 
on your network then you cannot use selfupdate. You can use "sudo port sync" to 
update the ports collection periodically and you can subscribe to the 
macports-announce mailing list to learn when new releases of MacPorts base are 
made, and then download the installer for that version from our web site. 

Re: I just wanted to upgrade my older MacPorts version

[Ryan Schmidt]

On Mar 8, 2024, at 03:18, xmartin wrote:
> 
> 1) You are right. The directory  /opt/local/var has always been part of 
> MacPorts. In fact, I had a backup of the older version and, obviously this 
> directory was still there… The only important difference is that now this 
> /var directory contains a new subdirectory (called /macports), and not 
> existing in the older MacPorts version, that contains the following 
> subdirectories:
> /build   /distfiles  /home /incoming  /logs  /registry  /sip-workaround   
> /software  /sources  
> and a file called pingtimes.  Most of those subdirectories contain a lot of 
> directories and files... 

/opt/local/var/macports has also always existed (well, at least since the 
project was renamed to MacPorts) but it is usually hidden. If you are now 
seeing it in the Finder, then I guess the hidden flag has gotten unset somehow. 
It won't affect MacPorts functionality. You can hide it again if you wish. 

> 2) After typing "sudo port version” I get the following answer:
> [iMac-de-Martin:~] xmartin% sudo port version
> Warning: port definitions are more than two weeks old, consider updating them 
> by running 'port selfupdate'.
> Version: 2.9.1

Great, so MacPorts was indeed successfully updated to 2.9.1, but the 
post-update sync failed to update your ports collection due to your rsync 
problem. 

Re: I just wanted to upgrade my older MacPorts version

[Riccardo Mottola via macports-users]

Hi,

xmar...@iqf.csic.es wrote:
The “sudo port upgrade outdated” is running, but the question know is, 
how can I run in the future the equivalent to the older “sudo port 
selfupdate”?
I suppose that since you got the repository in git, you just need to do 
a "git pull" to upgrade it and subsequently "sudo port -v sync".


Essentially Step 1 becomes a git pull, Step 2 can be skipped, Step 3 
repeated.


I too have a similar issue, at work I cannot access the web resources, a 
proxy is usually needed. At home though I can use it, so I run 
selfupdate at home or over a mobile connection.


Hope that helps, I did not test it.

Riccardo

Re: I just wanted to upgrade my older MacPorts version

[xmartin]

Sorry again. In fact, the the problem seems to be the restrictive corporate 
network. I was able to run what is said in:
https://trac.macports.org/wiki/howto/SyncingWithGit 


The “sudo port upgrade outdated” is running, but the question know is, how can 
I run in the future the equivalent to the older “sudo port selfupdate”?

Thanks again,
Martin

Dr. Martin Martinez-Ripoll
Research Professor Emeritus
xmar...@iqfr.csic.es
Dept. of Crystallography & Structural Biology
www.xtal.iqfr.csic.es
Consejo Superior de Investigaciones Científicas
Spanish National Research Council
www.csic.es






> El 8 mar 2024, a las 10:18, xmar...@iqf.csic.es escribió:
> 
> Dear Ryan, thanks a lot for your email. Answering to your questions…
> 
> 1) You are right. The directory  /opt/local/var has always been part of 
> MacPorts. In fact, I had a backup of the older version and, obviously this 
> directory was still there… The only important difference is that now this 
> /var directory contains a new subdirectory (called /macports), and not 
> existing in the older MacPorts version, that contains the following 
> subdirectories:
> /build   /distfiles  /home /incoming  /logs  /registry  /sip-workaround   
> /software  /sources  
> and a file called pingtimes.  Most of those subdirectories contain a lot of 
> directories and files... 
> 
> 
> 2) After typing "sudo port version” I get the following answer:
> [iMac-de-Martin:~] xmartin% sudo port version
> Warning: port definitions are more than two weeks old, consider updating them 
> by running 'port selfupdate'.
> Version: 2.9.1
> 
> 3) I have no antivirus at all and in order to check if the problem arises 
> from any restrictive corporate network, I have conected the iMac to my handy 
> network. The result is exactly the same 
> 
> I hope this can help you to find out the way to solve the situation . In any 
> case, thanks for your effort.
> 
> Martin
> 
> Dr. Martin Martinez-Ripoll
> Research Professor Emeritus
> xmar...@iqfr.csic.es 
> Dept. of Crystallography & Structural Biology
> www.xtal.iqfr.csic.es
> Consejo Superior de Investigaciones Científicas
> Spanish National Research Council
> www.csic.es
> 
> 
> 
> 
> 
> 
>> El 7 mar 2024, a las 21:26, Ryan Schmidt > > escribió:
>> 
>> On Mar 7, 2024, at 06:30, Martin wrote:
>> 
>>> I was running an older MacPorts version on my High Sierra and wanted to 
>>> upgrade the version just installing the newest one 
>>> (MacPorts-2.9.1-10.13-HighSierra.pkg 
>>> )
>>>  existing for my iMac. I did it and and it was made with getting no errors 
>>> or warnings. 
>> 
>> That should have successfully updated MacPorts base. 
>> 
>>> However, after this installation I only see that there appeared a new 
>>> directory called /opt/local/var/, but the existing executables are still 
>>> the old ones (the ones existing in the old  /opt/local/bin directory. 
>> 
>> /opt/local/var has always been part of MacPorts.
>> 
>> Are you saying that "port version" shows an earlier number than 2.9.1? If 
>> so, install the pkg again and note any error messages. 
>> 
>>> And when I try to run “sudo port selfupdate”  I get the following error:
>>> 
>>> --->  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 
>>> MacPorts sources: command execution failed
>>> 
>> 
>> There should be more information about why rsync failed. Probably it is a 
>> problem specific to your computer (e.g. restrictive antivirus software) or 
>> network (e.g. restrictive corporate network). If you can't fix your computer 
>> so that it can talk to rsync servers, see the section "Alternatives for 
>> syncing the ports tree without rsync:" at 
>> https://trac.macports.org/wiki/howto 
>> 
>> 
> 

Re: I just wanted to upgrade my older MacPorts version

[xmartin]

Dear Ryan, thanks a lot for your email. Answering to your questions…

1) You are right. The directory  /opt/local/var has always been part of 
MacPorts. In fact, I had a backup of the older version and, obviously this 
directory was still there… The only important difference is that now this /var 
directory contains a new subdirectory (called /macports), and not existing in 
the older MacPorts version, that contains the following subdirectories:
/build   /distfiles  /home /incoming  /logs  /registry  /sip-workaround   
/software  /sources  
and a file called pingtimes.  Most of those subdirectories contain a lot of 
directories and files... 


2) After typing "sudo port version” I get the following answer:
[iMac-de-Martin:~] xmartin% sudo port version
Warning: port definitions are more than two weeks old, consider updating them 
by running 'port selfupdate'.
Version: 2.9.1

3) I have no antivirus at all and in order to check if the problem arises from 
any restrictive corporate network, I have conected the iMac to my handy 
network. The result is exactly the same 

I hope this can help you to find out the way to solve the situation . In any 
case, thanks for your effort.

Martin

Dr. Martin Martinez-Ripoll
Research Professor Emeritus
xmar...@iqfr.csic.es
Dept. of Crystallography & Structural Biology
www.xtal.iqfr.csic.es
Consejo Superior de Investigaciones Científicas
Spanish National Research Council
www.csic.es






> El 7 mar 2024, a las 21:26, Ryan Schmidt  escribió:
> 
> On Mar 7, 2024, at 06:30, Martin wrote:
> 
>> I was running an older MacPorts version on my High Sierra and wanted to 
>> upgrade the version just installing the newest one 
>> (MacPorts-2.9.1-10.13-HighSierra.pkg 
>> )
>>  existing for my iMac. I did it and and it was made with getting no errors 
>> or warnings. 
> 
> That should have successfully updated MacPorts base. 
> 
>> However, after this installation I only see that there appeared a new 
>> directory called /opt/local/var/, but the existing executables are still the 
>> old ones (the ones existing in the old  /opt/local/bin directory. 
> 
> /opt/local/var has always been part of MacPorts.
> 
> Are you saying that "port version" shows an earlier number than 2.9.1? If so, 
> install the pkg again and note any error messages. 
> 
>> And when I try to run “sudo port selfupdate”  I get the following error:
>> 
>> --->  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 
>> MacPorts sources: command execution failed
>> 
> 
> There should be more information about why rsync failed. Probably it is a 
> problem specific to your computer (e.g. restrictive antivirus software) or 
> network (e.g. restrictive corporate network). If you can't fix your computer 
> so that it can talk to rsync servers, see the section "Alternatives for 
> syncing the ports tree without rsync:" at 
> https://trac.macports.org/wiki/howto 
> 
> 

Re: I just wanted to upgrade my older MacPorts version

[Ryan Schmidt]

On Mar 7, 2024, at 06:30, Martin wrote:

> I was running an older MacPorts version on my High Sierra and wanted to 
> upgrade the version just installing the newest one 
> (MacPorts-2.9.1-10.13-HighSierra.pkg) existing for my iMac. I did it and and 
> it was made with getting no errors or warnings. 

That should have successfully updated MacPorts base. 

> However, after this installation I only see that there appeared a new 
> directory called /opt/local/var/, but the existing executables are still the 
> old ones (the ones existing in the old  /opt/local/bin directory. 

/opt/local/var has always been part of MacPorts.

Are you saying that "port version" shows an earlier number than 2.9.1? If so, 
install the pkg again and note any error messages. 

> And when I try to run “sudo port selfupdate”  I get the following error:
> 
> --->  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 
> MacPorts sources: command execution failed
> 

There should be more information about why rsync failed. Probably it is a 
problem specific to your computer (e.g. restrictive antivirus software) or 
network (e.g. restrictive corporate network). If you can't fix your computer so 
that it can talk to rsync servers, see the section "Alternatives for syncing 
the ports tree without rsync:" at https://trac.macports.org/wiki/howto

Re: I just wanted to upgrade my older MacPorts version

[Richard L. Hamilton]

That's strange, in that /opt/local/var should have been part of the original 
MacPorts install, too. /opt/local/var/macports is workspace for MacPorts plus 
information about what's installed; all the other subdirectories of 
/opt/local/var are for the ports to use instead of using subdirectories of 
/var, esp. if they might conflict with a similar program that comes with the OS.

So something may have been wrong before you did the install of the new pkg. 
Among other things, I'm wondering if the previous version was for an earlier 
version of MacOS, in which case problems could be expected.

port -d selfupdate

(which impiles -v and also adds debugging messages) should provide more detail 
what failed.

"port" depends on some other commands, and will use the system version if you 
don't have a MacPorts version installed. Like rsync for sure (for selfupdate) 
and curl to fetch individual files when needed. And others like tar or cpio or 
gzip (and maybe additional commands) to deal with archives  and compressed 
files, openssl to check digital signatures, etc. If any of those are missing  
or not working, that will be a problem.

Other than that, I have no idea. I've never dug deep into how it all works, 
just glanced for a couple minutes at the tcl code for the "port" command and 
the macports specific components that it uses. There are people here who know 
much more, but they probably have day jobs too, so please be patient.


> On Mar 7, 2024, at 07:30, xmar...@iqf.csic.es wrote:
> 
> Sorry for such an stupid question…
> 
> I was running an older MacPorts version on my High Sierra and wanted to 
> upgrade the version just installing the newest one 
> (MacPorts-2.9.1-10.13-HighSierra.pkg 
> )
>  existing for my iMac. I did it and and it was made with getting no errors or 
> warnings. 
> 
> However, after this installation I only see that there appeared a new 
> directory called /opt/local/var/, but the existing executables are still the 
> old ones (the ones existing in the old  /opt/local/bin directory. 
> 
> And when I try to run “sudo port selfupdate”  I get the following error:
> 
> --->  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 
> MacPorts sources: command execution failed
> 
> Rerunning it with the -v option I get exactly the same error and my question 
> is:
> What can I do to have the newest MacPorts binaries being upgraded?
> 
> Any help would be kindly appreciated….
> All the best,
> Martin
> 
> Dr. Martin Martinez-Ripoll
> Research Professor Emeritus
> xmar...@iqf.csic.es 
> Dept. of Crystallography & Structural Biology
> www.xtal.iqfr.csic.es
> Consejo Superior de Investigaciones Científicas
> Spanish National Research Council
> www.csic.es
> 
> 
> 
> 
> 
> 

I just wanted to upgrade my older MacPorts version

[xmartin]

Sorry for such an stupid question…

I was running an older MacPorts version on my High Sierra and wanted to upgrade 
the version just installing the newest one (MacPorts-2.9.1-10.13-HighSierra.pkg 
)
 existing for my iMac. I did it and and it was made with getting no errors or 
warnings. 

However, after this installation I only see that there appeared a new directory 
called /opt/local/var/, but the existing executables are still the old ones 
(the ones existing in the old  /opt/local/bin directory. 

And when I try to run “sudo port selfupdate”  I get the following error:

--->  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 
MacPorts sources: command execution failed

Rerunning it with the -v option I get exactly the same error and my question is:
What can I do to have the newest MacPorts binaries being upgraded?

Any help would be kindly appreciated….
All the best,
Martin

Dr. Martin Martinez-Ripoll
Research Professor Emeritus
xmar...@iqf.csic.es
Dept. of Crystallography & Structural Biology
www.xtal.iqfr.csic.es
Consejo Superior de Investigaciones Científicas
Spanish National Research Council
www.csic.es