Josh Thanks for confirming, I think we are going to need more additional rules to be requested. Will keep you updated.
Shree On Mar 13, 2014, at 10:47 PM, Joshua Root <[email protected]> wrote: > MacPorts buildslaves are connecting to the master now, but they still > can't connect to rsync.macports.org for selfupdate. The portfiles are > synced with svn, so builds are working fine for now, but we will want > them to be able to selfupdate when we release a new version of MacPorts > base. > > - Josh > > On 2014-3-14 10:08 , Shreeraj Karulkar wrote: >> Hello All >> >> Following issues are still pending. >> >> 1. data.macports.org has been inaccessible since yesterday 03/12/2014 >> around 7.30 PM or so when Ryan Schmidt first reported failure on >> trac.macports. Apparently a change was put in yesterday while took the >> entire Macports Internal VLAN off limits. >> A ticket was opened last night and and they are supposed to fix it this >> evening around 7 PM PST. <exp2://Ticket/18428970> DC Network Internal: VLAN >> connectivity to Mac OS Forge servers >> >> 2. Build-slaves could not be moved to the new VLAN due to lack of resources >> on the Xerves and and request as been put to open ports on the old VLAN. >> The original ETA was for tomorrow 3/14/2014 but I just checked that they >> will be doing this tonight as well. <exp2://Ticket/18420429> FireWall Rules >> for Mac OS Forge (Macports Build-Slaves) >> >> If you see other issues related to the migration please reply to this email >> chain. I would appreciate if you can forward this email to people who are >> not on this list but may need to know. >> Thanks. >> >> Shree > _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
