Re: Servers down?

2016-10-22 Thread Eneko Gotzon
On Sun, Oct 23, 2016 at 1:44 AM, Ryan Schmidt 
wrote:

> a change Apple made to their network configuration which had unexpected
> consequences


​Maybe it is not related but ​I have suffered serious synchronization issues
in iCloud services.

-- 
Eneko Gotzon Ares
enekogot...@gmail.com
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: Servers down?

2016-10-22 Thread Ryan Schmidt
> On Oct 22, 2016, at 16:11, Fielding, Eric J (329A) 
>  wrote:
> 
> I am guessing that the lack of access to MacPorts yesterday (Friday) may have 
> been related to the massive DDoS attack on the Dyn DNS servers. Because Dyn 
> uses their content delivery network to provide DNS, different areas were 
> affected to differing degrees from what I saw reported. The regular MacPorts 
> rsync mostly worked for me on Friday and still works today. As they say, your 
> mileage may vary.


Apple currently believes the outage was caused by a change Apple made to their 
network configuration which had unexpected consequences. 3 of the IP addresses 
used by MacPorts became inaccessible outside Apple. Other macOS forge IP 
addresses used by MacPorts and other projects were not affected. The services 
on the servers using those IP addresses have been moved to a new server outside 
of Apple. ___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: Servers down?

2016-10-22 Thread Lawrence Velázquez
> On Oct 22, 2016, at 5:11 PM, Fielding, Eric J (329A) 
>  wrote:
> 
> I am guessing that the lack of access to MacPorts yesterday (Friday)
> may have been related to the massive DDoS attack on the Dyn DNS
> servers.

This seems unlikely to me, as our unplanned downtime began (I think) on
Thursday (UTC).

> Because Dyn uses their content delivery network to provide DNS,
> different areas were affected to differing degrees from what I saw
> reported. The regular MacPorts rsync mostly worked for me on Friday
> and still works today. As they say, your mileage may vary.

The downtime affected systems that were still hosted at Mac OS Forge,
including svn.macports.org and trac.macports.org. rsync.macports.org is
now hosted at Friedrich-Alexander-Universität Erlangen-Nürnberg in
Germany and was therefore unaffected.

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


Re: Servers down?

2016-10-22 Thread Fielding, Eric J (329A)
I am guessing that the lack of access to MacPorts yesterday (Friday) may have 
been related to the massive DDoS attack on the Dyn DNS servers. Because Dyn 
uses their content delivery network to provide DNS, different areas were 
affected to differing degrees from what I saw reported. The regular MacPorts 
rsync mostly worked for me on Friday and still works today. As they say, your 
mileage may vary.

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


Re: Servers down?

2016-10-21 Thread Ryan Schmidt

> On Oct 21, 2016, at 5:45 PM, Manfred Antar  wrote:
> 
> 
>> On Oct 21, 2016, at 3:32 PM, Ryan Schmidt  wrote:
>> 
>> 
>>> On Oct 21, 2016, at 4:31 PM, Lawrence Velázquez  wrote:
>>> 
 On Oct 21, 2016, at 5:30 PM, Carlo Tambuatco  wrote:
 
 I can't even get to the migration page on macports.org...
>>> 
>>> Yes, {svn,trac}.macports.org is still down, and probably others.
>> 
>> The only other server that appears to have been affected was the one serving 
>> the web site and guide. We already moved this to new hosting, but have not 
>> yet set up the ports database on the new server, which is why that section 
>> of the web site is currently unavailable.
>> 
>> Until access is restored, you can probably find some of our wiki pages in 
>> the Internet Archive, such as:
>> 
>> https://web.archive.org/web/20160513042611/http://trac.macports.org/wiki/Migration
>> 
> 
> Does this mean that svn.macports.org will no longer work for updating the 
> ports tree ?
> It’s been down for a few days.

There is an unexpected problem on the network that our servers are on; access 
to these servers was inadvertently blocked. We are trying to get access 
unblocked again, or move the servers to another location, as quickly as 
possible, hopefully by tomorrow.

> will everything switch to git?

On October 29th/30th. After that time, you can use git to update your ports 
tree, or svn if you prefer, since GitHub provides an svn compatibility mode.

> Hopefully there will be a faq on changing over.

What we have written for now is here:

https://lists.macosforge.org/pipermail/macports-users/2016-October/041819.html

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


Re: Servers down?

2016-10-21 Thread Manfred Antar

> On Oct 21, 2016, at 3:32 PM, Ryan Schmidt  wrote:
> 
> 
>> On Oct 21, 2016, at 4:31 PM, Lawrence Velázquez  wrote:
>> 
>>> On Oct 21, 2016, at 5:30 PM, Carlo Tambuatco  wrote:
>>> 
>>> I can't even get to the migration page on macports.org...
>> 
>> Yes, {svn,trac}.macports.org is still down, and probably others.
> 
> The only other server that appears to have been affected was the one serving 
> the web site and guide. We already moved this to new hosting, but have not 
> yet set up the ports database on the new server, which is why that section of 
> the web site is currently unavailable.
> 
> Until access is restored, you can probably find some of our wiki pages in the 
> Internet Archive, such as:
> 
> https://web.archive.org/web/20160513042611/http://trac.macports.org/wiki/Migration
> 

Does this mean that svn.macports.org  will no longer 
work for updating the ports tree ?
It’s been down for a few days. will everything switch to git?
Hopefully there will be a faq on changing over.
Thanks
Manfred___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: Servers down?

2016-10-21 Thread Ryan Schmidt

> On Oct 21, 2016, at 4:31 PM, Lawrence Velázquez  wrote:
> 
>> On Oct 21, 2016, at 5:30 PM, Carlo Tambuatco  wrote:
>> 
>> I can't even get to the migration page on macports.org...
> 
> Yes, {svn,trac}.macports.org is still down, and probably others.

The only other server that appears to have been affected was the one serving 
the web site and guide. We already moved this to new hosting, but have not yet 
set up the ports database on the new server, which is why that section of the 
web site is currently unavailable.

Until access is restored, you can probably find some of our wiki pages in the 
Internet Archive, such as:

https://web.archive.org/web/20160513042611/http://trac.macports.org/wiki/Migration


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


Re: Servers down?

2016-10-21 Thread Clemens Lang
Hi,

On Fri, Oct 21, 2016 at 05:33:03PM -0400, Brandon Allbery wrote:
> On Fri, Oct 21, 2016 at 5:30 PM, Carlo Tambuatco  
> wrote:
> 
> > I can't even get to the migration page on macports.org...
> 
> Reportedly, Apple horked their internal routing such that they are
> only accessible from inside Apple. As if we needed another reason to
> ditch MacOSForge.

Yes, sorry. We would have preferred an announcement at a time where we
didn't have infrastructure issues, but since the current problem doesn't
appear to be solved soon we rather wanted to bite the bullet and do it
now than delay our schedule further.

I'm working on getting the Trac data moved, so we might bring the page
back in a few days on the new setup.

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


Re: Servers down?

2016-10-21 Thread Brandon Allbery
On Fri, Oct 21, 2016 at 5:30 PM, Carlo Tambuatco 
wrote:

> I can't even get to the migration page on macports.org...


Reportedly, Apple horked their internal routing such that they are only
accessible from inside Apple. As if we needed another reason to ditch
MacOSForge.
Migration is currently in progress.

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Re: Servers down?

2016-10-21 Thread Lawrence Velázquez
> On Oct 21, 2016, at 5:30 PM, Carlo Tambuatco  wrote:
> 
> I can't even get to the migration page on macports.org...

Yes, {svn,trac}.macports.org is still down, and probably others.

vq

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


Re: servers down

2007-11-13 Thread Ryan Schmidt

On Nov 13, 2007, at 07:39, Edward Harvey wrote:


On Nov 10, 2007, at 10:12 PM, Ryan Schmidt wrote:

Ok, so the apr0 and apr-util0 ports are out of date and need to be  
updated. You should file a ticket for that in Trac. Instructions  
are here:


http://trac.macosforge.org/projects/macports/wiki/TracTicketing


I submitted a ticket there.  I suppose I could watch the bug to see  
when it's taken care of, but there's a new question...


This was the ticket:

http://trac.macports.org/projects/macports/ticket/13251


When they update this, will it be a port selfupdate situation?   
That will download new portfiles for me, and then I can build it,  
or is there some sort of Update only my portfiles procedure that  
will resolve this faster?


The update only my portfiles procedure is port sync. We usually  
recommend port selfupdate because it includes a sync and also  
makes sure your MacPorts base software is up to date.



I tried simply editing my portfiles (change the version number and  
update the md5sum).  Apr0 and apr-util0 built just fine, and apache  
with the defaults only complained of warnings (warning, this build  
violates port file structures, blah blah) but what I need to do is  
port install apache20 +openldap and this build unfortunately fails.


So I suppose it will work whenever the next stable release of port  
is released port selfupdate but who knows when that will be.


I'm wondering if there's any way to get this done sooner?


There aren't stable and unstable ports; there's just ports. Once  
a change to a port is committed to the repository, port selfupdate  
will be able to pull it down within 30 minutes.


Since you already worked out how the portfiles need to be changed,  
you could ease the maintainer's job (and thereby make the update  
happen faster) by attaching your diffs to the ticket.


Tickets don't get seen unless they're Cc'd to the maintainer of the  
port. It looks like Anthony already added Blair's email address to  
the Cc list so he should see it now. If he does not react within 72  
hours, anyone else can commit the update. Remind us in 3 days if the  
ticket has not yet been resolved.


If apr upgraded successfully but you are now having problems with a  
variant of apache20, then it sounds like there's a second problem.  
You should show us the exact error message you're getting now.



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


Re: servers down

2007-11-13 Thread Emmanuel Hainry
Citando Ryan Schmidt :

 Tickets don't get seen unless they're Cc'd to the maintainer of the port. 
 It looks like Anthony already added Blair's email address to the Cc list so 
 he should see it now. 

Is it still true? Since the migration (yesterday), I have received mails
for trac tickets I modified and for which I was not in Cc. Maybe #10672
has been resolved, no?

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


Re: servers down

2007-11-10 Thread Ryan Schmidt


On Nov 10, 2007, at 15:10, Edward Ned Harvey wrote:

I'm trying to install apache20, which has dependencies, including  
apr and

apr-util, and a bunch of other stuff.

I was able to install all the other stuff, sudo port install expat  
openssl

...
But when I sudo port install apr0 apr-util0, it attempts to fetch  
from a

bunch of servers and eventually fails.

Does this happen much, in peoples' experience here?  When it  
happens, is
there any workaround, such as trying a different rsync mirror or  
something

like that?

I'm guessing I just have to wait a day and try again.


The ports usually fetch the software from the developers' web sites.  
We don't control them, so it's possible that they'll be down from  
time to time. But it shouldn't be a problem that often. You can also  
always fetch the software yourself, if you can find it elsewhere, and  
put it in the right place (which is /opt/local/var/macports/distfiles/ 
${name}). For sites that are frequently down, we sometimes mirror the  
distfiles on our own server. You could show us the exact error  
messages you're getting so we can look into it and see what's going on.



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


Re: servers down

2007-11-10 Thread Edward Ned Harvey
The ports usually fetch the software from the developers' web sites. We 
don't control them, so it's possible that they'll be down from time to 
time. But it shouldn't be a problem that often. You can also always 
fetch the software yourself, if you can find it elsewhere, and put it in 
the right place (which is /opt/local/var/macports/distfiles/${name}). 
For sites that are frequently down, we sometimes mirror the distfiles on 
our own server. You could show us the exact error messages you're 
getting so we can look into it and see what's going on.


Now that I look closer, I see the first URL that's failing is 
www.apache.org.  In fact, their site is not down, and when I go there, 
it's easy to see what's wrong.  They have apr 0.9.16 available, but the 
one attempting to download is 0.9.13.  So simply the package that port 
is trying to download is too old.


I browsed around, and 0.9.13 is no longer available.  So I can't 
download it myself into the distfiles directory.


I tried tricking port by grepping for 0.9.13 under /opt, and editing a 
few select files to 0.9.16 instead.  This allowed the file to download, 
but the checksum failed.


Any suggestions on how to handle this situation?

Thanks again.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users


Re: servers down

2007-11-10 Thread William Davis


On Nov 10, 2007, at 9:15 PM, Edward Ned Harvey wrote:

The ports usually fetch the software from the developers' web  
sites. We don't control them, so it's possible that they'll be down  
from time to time. But it shouldn't be a problem that often. You  
can also always fetch the software yourself, if you can find it  
elsewhere, and put it in the right place (which is /opt/local/var/ 
macports/distfiles/${name}). For sites that are frequently down, we  
sometimes mirror the distfiles on our own server. You could show us  
the exact error messages you're getting so we can look into it and  
see what's going on.


Now that I look closer, I see the first URL that's failing is www.apache.org 
.  In fact, their site is not down, and when I go there, it's easy  
to see what's wrong.  They have apr 0.9.16 available, but the one  
attempting to download is 0.9.13.  So simply the package that port  
is trying to download is too old.


I browsed around, and 0.9.13 is no longer available.  So I can't  
download it myself into the distfiles directory.


I tried tricking port by grepping for 0.9.13 under /opt, and  
editing a few select files to 0.9.16 instead.  This allowed the file  
to download, but the checksum failed.


Any suggestions on how to handle this situation?

Thanks again.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users


http://geeklair.net/new_macports_guide/#development.creating-portfile  
shows you how to do new  checksum.


William Davis
frstanATbellsouthDOTnet
Mac OS X.5.0 Darwin 9.0.0
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non

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


Re: servers down

2007-11-10 Thread Ryan Schmidt

On Nov 10, 2007, at 20:15, Edward Ned Harvey wrote:

The ports usually fetch the software from the developers' web  
sites. We don't control them, so it's possible that they'll be  
down from time to time. But it shouldn't be a problem that often.  
You can also always fetch the software yourself, if you can find  
it elsewhere, and put it in the right place (which is /opt/local/ 
var/macports/distfiles/${name}). For sites that are frequently  
down, we sometimes mirror the distfiles on our own server. You  
could show us the exact error messages you're getting so we can  
look into it and see what's going on.


Now that I look closer, I see the first URL that's failing is  
www.apache.org.  In fact, their site is not down, and when I go  
there, it's easy to see what's wrong.  They have apr 0.9.16  
available, but the one attempting to download is 0.9.13.  So simply  
the package that port is trying to download is too old.


I browsed around, and 0.9.13 is no longer available.  So I can't  
download it myself into the distfiles directory.


I tried tricking port by grepping for 0.9.13 under /opt, and  
editing a few select files to 0.9.16 instead.  This allowed the  
file to download, but the checksum failed.


Any suggestions on how to handle this situation?


Ok, so the apr0 and apr-util0 ports are out of date and need to be  
updated. You should file a ticket for that in Trac. Instructions are  
here:


http://trac.macosforge.org/projects/macports/wiki/TracTicketing


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