Re: Selfupdate problem

2020-09-07 Thread dan d.
Trying to execute: /bin/mv Bombed. I copyed a backup of mv to /bin and the selfupdate was successful. Thanks much. On Mon, 7 Sep 2020, Ryan Schmidt wrote: > > > On Sep 7, 2020, at 09:25, dan d. wrote: > > > Idid the sudo port -d selfupdate as suggested. > > > > At the end of some 784 lines, t

Re: Selfupdate problem

2020-09-07 Thread Ryan Schmidt
On Sep 7, 2020, at 09:25, dan d. wrote: > Idid the sudo port -d selfupdate as suggested. > > At the end of some 784 lines, this > > checking for existence of > /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/base/vendor/tcl/unix/tclConfig.sh... > file not found >

Re: Selfupdate problem

2020-09-07 Thread dan d.
Idid the sudo port -d selfupdate as suggested. At the end of some 784 lines, this checking for existence of /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/base/vendor/tcl/unix/tclConfig.sh... file not found checking how to build libraries... shared checking that any

Re: Selfupdate problem

2020-09-06 Thread Ryan Schmidt
On Sep 6, 2020, at 17:18, dan d. wrote: > Each time I run it it reports base 2.6.2 installed and updateing to base > 2.6.3. > > However, running it again later produces the same result. > > Doing port -v produces the 2.6.2 version installed. > > There are no error messages. > > Any ideas?

Selfupdate problem

2020-09-06 Thread dan d.
Each time I run it it reports base 2.6.2 installed and updateing to base 2.6.3. However, running it again later produces the same result. Doing port -v produces the 2.6.2 version installed. There are no error messages. Any ideas? Thanks. -- XR