Re: rsync server out of date?

[Ryan Schmidt]

On Jul 22, 2017, at 09:48, Marcus Calhoun-Lopez wrote:

> I just ran `port sync`, but the ports are several days behind the GitHub 
> repository.
> Is anyone else having this problem?

I've reset it again (third time this month) and it should sync up again in a 
couple hours.

Re: rsync server out of date?

[Clemens Lang]

Hi,

On Sat, Jul 22, 2017 at 07:48:59AM -0700, Marcus Calhoun-Lopez wrote:
> I just ran `port sync`, but the ports are several days behind the
> GitHub repository. Is anyone else having this problem?

We're aware of the problem and are in contact with GitHub support to
resolve the issue.

If you want to help out, we'd welcome a pull requests that makes
  https://github.com/macports/macports-infrastructure/blob/master/jobs/mprsyncup
use Git instead of SVN.

-- 
Clemens

rsync server out of date?

[Marcus Calhoun-Lopez]

I just ran `port sync`, but the ports are several days behind the GitHub 
repository.
Is anyone else having this problem?

-Marcus

Re: rsync server out of date?

[Ryan Schmidt]

On Dec 31, 2016, at 14:08, Ryan Schmidt wrote:

> I think we can work around the problem by checking out a fresh working copy 
> of macports-ports on the server for mprsyncup to use.

Done.

Re: rsync server out of date?

[Ryan Schmidt]

On Dec 31, 2016, at 13:31, Ryan Schmidt wrote:

> Starting on 12/28, mprsyncup is unable to update the Subversion working copy 
> of the macports-ports git repository:
> 
> 
> 2016-12-28T11:28:40-0600 + PORTS_OLD_REV=131029
> 2016-12-28T11:28:40-0600 + /opt/local/bin/svn --non-interactive -q update 
> /var/tmp/mprsyncup/release/ports
> 2016-12-28T11:30:49-0600 svn: E175002: Unexpected HTTP status 502 'Bad 
> Gateway' on '/macports/macports-ports.git/!svn/vcc/default'
> 
> 
> 2016-12-28T12:01:02-0600 + PORTS_OLD_REV=131029
> 2016-12-28T12:01:02-0600 + /opt/local/bin/svn --non-interactive -q update 
> /var/tmp/mprsyncup/release/ports
> 2016-12-28T12:03:18-0600 svn: E175002: Unexpected HTTP status 504 'Gateway 
> Timeout' on '/macports/macports-ports.git/!svn/vcc/default'


r131038 is the revision in which $Id$ lines were removed from all remaining 
9292 ports. Seems like the GitHub git-to-svn gateway is not able to handle a 
change that large. I have reported that problem to the GitHub support team.

I think we can work around the problem by checking out a fresh working copy of 
macports-ports on the server for mprsyncup to use.

I imagine we can avoid the problem in the future by not modifying that many 
files at once.

Re: rsync server out of date?

[Ryan Schmidt]

> On Dec 31, 2016, at 06:45, Clemens Lang  wrote:
> 
> Hi,
> 
> On Fri, Dec 30, 2016 at 11:13:21PM -0700, Marcus Calhoun-Lopez wrote:
>> I just ran `port sync`, but the ports are several days behind the
>> GitHub repository. I have never encountered this before and am at a
>> bit of a loss as to how to proceed. Is anyone else having this
>> problem?
> 
> Can confirm, my cronjob has been telling me for two days now. The last
> update to ports.tar was at 2016-12-28 17:57:54.0 +0100.
> 
> Ryan, can you check what's wrong?

Starting on 12/28, mprsyncup is unable to update the Subversion working copy of 
the macports-ports git repository:


2016-12-28T11:28:40-0600 + PORTS_OLD_REV=131029
2016-12-28T11:28:40-0600 + /opt/local/bin/svn --non-interactive -q update 
/var/tmp/mprsyncup/release/ports
2016-12-28T11:30:49-0600 svn: E175002: Unexpected HTTP status 502 'Bad Gateway' 
on '/macports/macports-ports.git/!svn/vcc/default'


2016-12-28T12:01:02-0600 + PORTS_OLD_REV=131029
2016-12-28T12:01:02-0600 + /opt/local/bin/svn --non-interactive -q update 
/var/tmp/mprsyncup/release/ports
2016-12-28T12:03:18-0600 svn: E175002: Unexpected HTTP status 504 'Gateway 
Timeout' on '/macports/macports-ports.git/!svn/vcc/default'

Re: rsync server out of date?

[Clemens Lang]

Hi,

On Fri, Dec 30, 2016 at 11:13:21PM -0700, Marcus Calhoun-Lopez wrote:
> I just ran `port sync`, but the ports are several days behind the
> GitHub repository. I have never encountered this before and am at a
> bit of a loss as to how to proceed. Is anyone else having this
> problem?

Can confirm, my cronjob has been telling me for two days now. The last
update to ports.tar was at 2016-12-28 17:57:54.0 +0100.

Ryan, can you check what's wrong?

-- 
Clemens