Re: rsync server out of date?

2016-12-31 Thread 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?

2016-12-31 Thread 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?

2016-12-31 Thread 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


Re: Command line switch to say yes to dependencies?

2016-12-31 Thread Joshua Root

And 'ui_interactive no' in macports.conf to make it permanent.

I'm not sure whether it would make sense to have a --yes flag like some 
other tools, which means "act as though I answered yes to all questions" 
rather than "don't ask any questions". In the case of installing 
dependencies the two are equivalent, but they might not be in other 
cases. And depending on what you're doing, the result might be quite 
destructive.


- Josh

On 2016-12-31 04:46 , m...@macports.org wrote:

The -N flag works for me.

sudo port -N install …


Cheers!
Frank


On Dec 30, 2016, at 7:49 AM, Sterling Smith > wrote:

Hi,

So it seems there is a new feature that asks if I want to install all
of the dependencies of a requested port.  Is there a command line
switch to answer yes?  If not, is there some other programmatic way to
answer yes?  (This is installing for a non-default prefix from the
master branch, so maybe there is something in master that hasn't made
it to the documentation yet...)

Thanks,
Sterling