port selfupdate fails

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

port selfupdate fails

j. van den hoff-3
before I start: yes, I have seen and read ticket #53414. I did not help:

I tried to to to selfupdate from 2.3.5 to 2.4.1 today (MacOS 10.11.6). it  
failed with

configure: === configuring in vendor/tcl/unix  
(/opt/local/var/macports/sources/rsync.macports.org/release/base/vendor/tcl/unix)
configure: error: no configure script found in vendor/tcl/unix
Command failed: CC=/usr/bin/cc OBJC=/usr/bin/cc ./configure  
--prefix='/opt/local' --with-install-user='root'  
--with-install-group='wheel' --with-directory-mode='0755'  
--enable-readline && make SELFUPDATING=1 && make install SELFUPDATING=1
Exit code: 1

I never touched macports.conf so it should be at its default settings (so  
rsync_dir is not set there ...). it looked like #53414 but as explained  
there seems nothing wrong with my (default) macports.conf.

I found another hint in the archive that using the pkg installer bypasses  
the problem. I found and used the one for 2.4.0 which indeed did do a  
(self?)update to 2.4.0. but even then, when issuing

port selfupdate to get fro 2.4.0 to 2.4.1 it fails the same way as  
described above.

what am I missing?

thanks,

joerg
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: port selfupdate fails

Ryan Schmidt-24
May we see your /opt/local/etc/macports/macports.conf file?

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: port selfupdate fails

Mihai Moldovan-2
In reply to this post by j. van den hoff-3
On 10.03.2017 06:32 PM, j. van den hoff wrote:
> before I start: yes, I have seen and read ticket #53414. I did not help:

Naturally not, this change has only been deployed with 2.4.1.

In order to get the selfupdate to work, either change your macports.conf (make
sure rsync_options includes the "l" flag), or sources.conf to the preferred
tarball-based rsync method (see the default file here:
https://github.com/macports/macports-base/blob/release-2.4/doc/sources.conf ) OR
use the installer package for your platform to install 2.4.1 directly.
Subsequent selfupdates shouldn't fail anymore.


Installer package:
https://github.com/macports/macports-base/releases/download/v2.4.1/MacPorts-2.4.1-10.11-ElCapitan.pkg



Mihai




signature.asc (902 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: port selfupdate fails

Tai Viinikka
In reply to this post by j. van den hoff-3
On Fri, Mar 10, 2017 at 12:32 PM, j. van den hoff <[hidden email]> wrote:
before I start: yes, I have seen and read ticket #53414. I did not help:

I tried to to to selfupdate from 2.3.5 to 2.4.1 today (MacOS 10.11.6). it failed with

configure: === configuring in vendor/tcl/unix (/opt/local/var/macports/sources/rsync.macports.org/release/base/vendor/tcl/unix)
configure: error: no configure script found in vendor/tcl/unix
Command failed: CC=/usr/bin/cc OBJC=/usr/bin/cc ./configure --prefix='/opt/local' --with-install-user='root' --with-install-group='wheel' --with-directory-mode='0755' --enable-readline && make SELFUPDATING=1 && make install SELFUPDATING=1
Exit code: 1

[...] 
 
what am I missing?

I think I have the same problem as joerg. 

Based on previous discussion here, and ticket 53414, I tried two fixes: 
1)  Revert to default macports.conf:

root@recluse:~$cd  /opt/local/etc/macports

root@recluse:~$cp macports.conf.default macports.conf

My port -v self attempt ended (as it always does now) with:
configure: === configuring in vendor/tcl/unix (/opt/local/var/macports/sources/rsync.macports.org/release/base/vendor/tcl/unix)
configure: error: no configure script found in vendor/tcl/unix
Command failed: cd /opt/local/var/macports/sources/rsync.macports.org/release/base && CC=/usr/bin/cc OBJC=/usr/bin/cc ./configure --prefix='/opt/local' --with-install-user='root' --with-install-group='wheel' --with-directory-mode='0755' --enable-readline && make SELFUPDATING=1 && make install SELFUPDATING=1
Exit code: 1
Error: Error installing new MacPorts base: command execution failed
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: /opt/local/bin/port: port selfupdate failed: Error installing new MacPorts base: command execution failed

Since this looks like a softlink problem, I followed Mihai's suggestion to "make sure rsync_options includes the "l" flag" and now I have it: 

root@recluse:~$grep options  /opt/local/etc/macports/macports.conf 
rsync_options           -rtzvl --delete-after

Failure mode was the same, as above. 

Any further thoughts or suggestions? My macports.conf is included as an attachment. (Would in-line have been better?) 

tai

PS: Many thanks for making 17855 things possible with MacPorts. :) 


--
[hidden email]   ::::   East Pole Productions

macports.conf (10K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: port selfupdate fails

Joshua Root-8
In reply to this post by j. van den hoff-3
Tai Viinikka wrote:

> Based on previous discussion here, and ticket 53414, I tried two fixes:
> 1)  Revert to default macports.conf:
>
> root at recluse:~$cd  /opt/local/etc/macports
>
> root at recluse:~$cp macports.conf.default macports.conf
>
> My port -v self attempt ended (as it always does now) with:
>
>> configure: === configuring in vendor/tcl/unix
>> (/opt/local/var/macports/sources/
>> rsync.macports.org/release/base/vendor/tcl/unix)
>> configure: error: no configure script found in vendor/tcl/unix
>> Command failed: cd /opt/local/var/macports/sources/
>> rsync.macports.org/release/base && CC=/usr/bin/cc OBJC=/usr/bin/cc
>> ./configure --prefix='/opt/local' --with-install-user='root'
>> --with-install-group='wheel' --with-directory-mode='0755' --enable-readline
>> && make SELFUPDATING=1 && make install SELFUPDATING=1
>> Exit code: 1
>> Error: Error installing new MacPorts base: command execution failed
>> To report a bug, follow the instructions in the guide:
>>     http://guide.macports.org/#project.tickets
>> Error: /opt/local/bin/port: port selfupdate failed: Error installing new
>> MacPorts base: command execution failed
>
> Since this looks like a softlink problem, I followed Mihai's suggestion to "
> make sure rsync_options includes the "l" flag" and now I have it:
>
>> root at recluse:~$grep options  /opt/local/etc/macports/macports.conf
>> rsync_options           -rtzvl --delete-after
>
> Failure mode was the same, as above.
>
> Any further thoughts or suggestions? My macports.conf is included as an
> attachment. (Would in-line have been better?)

Do you have any .conf files in ~/.macports? Or PORTSRC set in the
environment?

- Josh
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: port selfupdate fails

Tai Viinikka
On Sun, Mar 12, 2017 at 11:43 PM, Joshua Root <[hidden email]> wrote:
Tai Viinikka wrote:
Based on previous discussion here, and ticket 53414, I tried two fixes:
1)  Revert to default macports.conf:

Do you have any .conf files in ~/.macports? Or PORTSRC set in the environment?

Thanks, Josh. That's embarrassing, but ultimately satisfying because when I moved root's .macports
directory out of the way, 

Congratulations, you have successfully upgraded the MacPorts system.

That file really is old. 

# MacPorts system wide configuration file
# $Id: macports.conf.in 26177 2007-06-15 10:11:22Z [hidden email] $

I appreciated the help! Thanks again. 

tai

--
[hidden email]   ::::   East Pole Productions
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: port selfupdate fails

j. van den hoff-3
In reply to this post by Mihai Moldovan-2
On Sat, 11 Mar 2017 10:29:43 +0100, Mihai Moldovan <[hidden email]>  
wrote:

> On 10.03.2017 06:32 PM, j. van den hoff wrote:
>> before I start: yes, I have seen and read ticket #53414. I did not help:
>
> Naturally not, this change has only been deployed with 2.4.1.
>
> In order to get the selfupdate to work, either change your macports.conf  
> (make
> sure rsync_options includes the "l" flag), or sources.conf to the  
> preferred
> tarball-based rsync method (see the default file here:
> https://github.com/macports/macports-base/blob/release-2.4/doc/sources.conf 
> ) OR
> use the installer package for your platform to install 2.4.1 directly.
> Subsequent selfupdates shouldn't fail anymore.

I did the latter (use the installer package) and can confirm that the  
problem has gone away.

thanks a lot!

joerg


--
Using Opera's revolutionary email client: http://www.opera.com/mail/
Loading...