Re: port selfupdate failing

[Gustavo Seabra]

Hi everyone,

Just an update on this issue, in case someone ever faces the same problema 
again:

The whole problem was because 'selfupdate' would work only over rsync, and that 
was blocked in my network. So, what I did and worked fine for me was:

1) Following Ryan Schmidt's suggestion, I installed the MacPorts base from the 
website 

2) Following Jeremy Lavergne's tip, I configured MacPorts to use svn, but just 
skipped the proxy configuration part (step 3 in 
http://trac.macports.org/wiki/howto/SyncingWithSVN).

3) back to Ryan's message: Now, I could just do a 'sudo port sync' to update 
the ports, and all works fine since.

Big thanks to Jeremy and Ryan for all the help.

Gustavo Seabra.


On Dec 4, 2013, at 8:13 PM, Ryan Schmidt  wrote:

> On Dec 4, 2013, at 15:34, Gustavo Seabra wrote:
> 
>> Steps 1 and 2 worked just fine. skipping step 3 I get the message below 
>> (basically, nothing changes.)
>> 
>> I attach my sources.conf file here, in case it helps.
>> 
>> Thanks!
>> Gustavo.
>> 
>> $ sudo port -d selfupdate
>> DEBUG: Copying /Users/seabra/Library/Preferences/com.apple.dt.Xcode.plist to 
>> /opt/local/var/macports/home/Library/Preferences
>> DEBUG: MacPorts sources location: 
>> /opt/local/var/macports/sources/rsync.macports.org/release/tarballs
>> --->  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 
>> /SourceCache/rsync/rsync-42/rsync/clientserver.c(105) [receiver=2.6.9]
>> Command failed: /usr/bin/rsync -rtzv --delete-after 
>> rsync://rsync.macports.org/release/tarballs/base.tar/opt/local/var/macports/sources/rsync.macports.org/release/tarballs
>> Exit code: 10
>> DEBUG: Error synchronizing MacPorts sources: command execution failed
>> while executing
>> "macports::selfupdate [array get global_options] base_updated"
>> Error: Error synchronizing MacPorts sources: 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 synchronizing 
>> MacPorts sources: command execution failed
>> $
> 
> The error messages tell us rsync communications are not working on your 
> network. Has this always been the case, or did selfupdate used to work? Did 
> something recently change about your network? If you have one, have you 
> spoken with your network administrator?
> 
> It's normal that editing sources.conf would not fix this because that only 
> affects "port sync", not "port selfupdate". If you cannot make rsync work on 
> your network, then you cannot use selfupdate and must use sync, and when a 
> new version on MacPorts base is released, you must install it using the 
> installer package we post on our web site. 

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: port selfupdate failing

[Gustavo Seabra]

Thanks,

I attached it to the last email, but it seems the server has stripped it.
Hre it goes inline.

Gustavo.


< Begin sources.conf >

# $Id: sources.conf 107099 2013-06-18 04:43:14Z lar...@macports.org $

# MacPorts system-wide configuration file for ports tree sources.
#
# To change how MacPorts fetches base, see rsync_server and rsync_dir in
# macports.conf.

# To add a local source, add a "file://" entry.
#
#   Example: file:///Users/landonf/misc/MacPorts/ports
#
# To prevent a source from synchronizing when `port sync` is used,
# append "[nosync]" at the end.
#
#   Example: file:///Users/landonf/misc/MacPorts/ports [nosync]
#
# Note that MacPorts parses source URLs in order; when a port appears in
# multiple sources, it installs the first occurrence. For local sources
# to shadow remote ones, "file://" URLs must come before other URLs.

# A list of rsync mirrors is available at
# https://trac.macports.org/wiki/Mirrors#Portfiles.
#
# If an "rsync://" URL points to a .tar file, a signed .rmd160 file must
# exist in the same directory on the server and will be used to verify
# its integrity.
#
# For proper functionality of various resources (port groups, mirror
# sites, etc.), the primary MacPorts source must always be tagged
# "[default]", even if switched from the default "rsync://" URL.

# EDITED TO USE SUBVERSION INSTEAD OF RSYNC,
# SINCE RSYNC DOESN'T SEEM TO WORK AT UFPE
# rsync://rsync.macports.org/release/tarballs/ports.tar [default]
file:///opt/local/var/macports/sources/svn.macports.org/trunk/dports/[default]


< End   sources.conf >


On Wed, Dec 4, 2013 at 6:36 PM, Jeremy Lavergne
wrote:

> Hmm, can you share the contents of:
> /opt/local/etc/macports/sources.conf
>
>
> Gustavo Seabra wrote:
>
>> Steps 1 and 2 worked just fine. skipping step 3 I get the message below
>> (basically, nothing changes.)
>>
>> I attach my sources.conf file here, in case it helps.
>>
>
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: port selfupdate failing

[Ryan Schmidt]

On Dec 4, 2013, at 15:34, Gustavo Seabra wrote:

> Steps 1 and 2 worked just fine. skipping step 3 I get the message below 
> (basically, nothing changes.)
> 
> I attach my sources.conf file here, in case it helps.
> 
> Thanks!
> Gustavo.
> 
> $ sudo port -d selfupdate
> DEBUG: Copying /Users/seabra/Library/Preferences/com.apple.dt.Xcode.plist to 
> /opt/local/var/macports/home/Library/Preferences
> DEBUG: MacPorts sources location: 
> /opt/local/var/macports/sources/rsync.macports.org/release/tarballs
> --->  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 
> /SourceCache/rsync/rsync-42/rsync/clientserver.c(105) [receiver=2.6.9]
> Command failed: /usr/bin/rsync -rtzv --delete-after 
> rsync://rsync.macports.org/release/tarballs/base.tar 
> /opt/local/var/macports/sources/rsync.macports.org/release/tarballs
> Exit code: 10
> DEBUG: Error synchronizing MacPorts sources: command execution failed
> while executing
> "macports::selfupdate [array get global_options] base_updated"
> Error: Error synchronizing MacPorts sources: 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 synchronizing 
> MacPorts sources: command execution failed
> $

The error messages tell us rsync communications are not working on your 
network. Has this always been the case, or did selfupdate used to work? Did 
something recently change about your network? If you have one, have you spoken 
with your network administrator?

It's normal that editing sources.conf would not fix this because that only 
affects "port sync", not "port selfupdate". If you cannot make rsync work on 
your network, then you cannot use selfupdate and must use sync, and when a new 
version on MacPorts base is released, you must install it using the installer 
package we post on our web site. 


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: port selfupdate failing

[Gustavo Seabra]

Steps 1 and 2 worked just fine. skipping step 3 I get the message below
(basically, nothing changes.)

I attach my sources.conf file here, in case it helps.

Thanks!
Gustavo.

$ sudo port -d selfupdate

DEBUG: Copying /Users/seabra/Library/Preferences/com.apple.dt.Xcode.plist
to /opt/local/var/macports/home/Library/Preferences

DEBUG: MacPorts sources location: /opt/local/var/macports/sources/
rsync.macports.org/release/tarballs

--->  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
/SourceCache/rsync/rsync-42/rsync/clientserver.c(105) [receiver=2.6.9]

Command failed: /usr/bin/rsync -rtzv --delete-after rsync://
rsync.macports.org/release/tarballs/base.tar/opt/local/var/macports/sources/
rsync.macports.org/release/tarballs

Exit code: 10

DEBUG: Error synchronizing MacPorts sources: command execution failed

while executing

"macports::selfupdate [array get global_options] base_updated"

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

$


sources.conf
Description: Binary data
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: port selfupdate failing

[Jeremy Lavergne]

Hmm, can you share the contents of:
/opt/local/etc/macports/sources.conf

Gustavo Seabra wrote:

Steps 1 and 2 worked just fine. skipping step 3 I get the message below
(basically, nothing changes.)

I attach my sources.conf file here, in case it helps.

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: port selfupdate failing

[Jeremy Lavergne]

In your case, skip step three. You won't be telling svn to go through a 
proxy.


Gustavo Seabra wrote:

Thanks. I have tried so many things I don't even remember all of them. I
have also tried the svn syncing you mention, but in "step 3" there one
needs to configure svn to work with a proxy. Since I cannot find a proxy
here, I had to stop there.

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: port selfupdate failing

[Gustavo Seabra]

Hi Jeremy,

Thanks. I have tried so many things I don't even remember all of them. I
have also tried the svn syncing you mention, but in "step 3" there one
needs to configure svn to work with a proxy. Since I cannot find a proxy
here, I had to stop there.

Gustavo Seabra 
Professor Adjunto, Departamento de Química Fundamental
Coordenador, CENAPAD-PE
Universidade Federal de Pernambuco
Fone: +55-81-2126-7450


On Wed, Dec 4, 2013 at 6:03 PM, Jeremy Lavergne
wrote:

> When you say "nothing works" did you try the answers you had discounted
> for proxies? Your ISP could be blocking ports or you're still behind a
> clever proxy.
>
> That is, have you tried syncing over svn instead?
>
> http://trac.macports.org/wiki/howto/SyncingWithSVN
>
>
> Gustavo Seabra wrote:
>
>> I am having trouble installing macports on an iMac at work running OSX
>> Mavericks. After the installation from the dmg, I try to run the port
>> self update command and get the messages below. I have already googled
>> for answers, but found nothing that works. Most of the answers relate to
>> being behind some proxy, but checking with "http://amibehindaproxy.com";
>> or "http://www.lagado.com/proxy-test"; both say I'm not behind a proxy.
>>
>> I'd really appreciate any suggestions.
>>
>
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: port selfupdate failing

[Jeremy Lavergne]

When you say "nothing works" did you try the answers you had discounted 
for proxies? Your ISP could be blocking ports or you're still behind a 
clever proxy.


That is, have you tried syncing over svn instead?

http://trac.macports.org/wiki/howto/SyncingWithSVN

Gustavo Seabra wrote:

I am having trouble installing macports on an iMac at work running OSX
Mavericks. After the installation from the dmg, I try to run the port
self update command and get the messages below. I have already googled
for answers, but found nothing that works. Most of the answers relate to
being behind some proxy, but checking with "http://amibehindaproxy.com";
or "http://www.lagado.com/proxy-test"; both say I'm not behind a proxy.

I'd really appreciate any suggestions.

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

port selfupdate failing

[Gustavo Seabra]

Hi,

I am having trouble installing macports on an iMac at work running OSX
Mavericks. After the installation from the dmg, I try to run the port self
update command and get the messages below. I have already googled for
answers, but found nothing that works. Most of the answers relate to being
behind some proxy, but checking with "http://amibehindaproxy.com"; or "
http://www.lagado.com/proxy-test"; both say I'm not behind a proxy.

I'd really appreciate any suggestions.

Thank you,
Gustavo.

$ sudo port -d selfupdate

Password:

DEBUG: Copying /Users/seabra/Library/Preferences/com.apple.dt.Xcode.plist
to /opt/local/var/macports/home/Library/Preferences

DEBUG: MacPorts sources location: /opt/local/var/macports/sources/
rsync.macports.org/release/tarballs

--->  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
/SourceCache/rsync/rsync-42/rsync/clientserver.c(105) [receiver=2.6.9]

Command failed: /usr/bin/rsync -rtzv --delete-after rsync://
rsync.macports.org/release/tarballs/base.tar/opt/local/var/macports/sources/
rsync.macports.org/release/tarballs

Exit code: 10

DEBUG: Error synchronizing MacPorts sources: command execution failed

while executing

"macports::selfupdate [array get global_options] base_updated"

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

$
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users