On Mon, Jun 29, 2009 at 4:32 PM, Loui Chang<louipc.ist@gmail.com> wrote:
On Mon 29 Jun 2009 16:09 -0500, Aaron Griffin wrote:
On Mon, Jun 29, 2009 at 3:51 PM, Evangelos Foutras<foutrelis@gmail.com> wrote:
Pierre Schmitz wrote:
On Monday 29 June 2009 18:03:50 Aaron Griffin wrote:
On Sun, Jun 28, 2009 at 11:52 PM, Abhishek Dasgupta<abhidg@gmail.com> wrote:
>From the ftp://archlinux.org/community/os/i686 page
community.db.tar.gz. . . . . . . Jun 27 18:01 so it hasn't been updated at all since the AUR move. If the new [community] repo is at the new server, then what's the link to access the repofiles, or does gerolde sync the packages back to itself? Since the mirrors all sync from archlinux.org they'll be getting the old community.db.tar.gz only.
Actually, this wasn't setup it seems - gerolde should be rsyncing the repo back to itself.
I'll get to this today
Btw: The new website is prety slow for me. Is there some configuration issue with mysql or php? Maybe forgot to isntall apc or mysql cache to small?
I've noticed this as well, as have several other Devs/TUs and also a user[1]. It looks like a networking issue (i.e. the load on the server is not excessive).
@Aaron (or whoever has contact with the host): Is it possible to have the company providing the server look into this?
It's weird that it seems to work fine for me: $ ping aur.archlinux.org ... --- aur.archlinux.org ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 8996ms rtt min/avg/max/mdev = 12.244/12.402/12.666/0.184 ms
Is anyone from North America having issues? Is it a continental thing?
I've noticed the connection issues. It seems to be an off and on thing. We should definitely investigate if it continues.
Maybe related, just got this email from SevenL: ----- In our ongoing effort to improve the service experience, we will be performing network maintenance on Tuesday June 30th at 6:30PM EDT. This procedure will enhance the stability of our network and increase the overall speed of our network. You may experience a period of service inaccessibility while our Network Administrators perform the maintenance. Downtime should be limited to no more than 5 minutes throughout the scheduled maintenance period. We apologize for any inconvenience this may cause. Procedure: Maintenance on Customer-Side Switches Duration: 30 minutes Start Time: 6:30PM EDT Completion Time: 7:00PM EDT Downtime: Loss of network connection lasting up to 5 minutes over a 30-minute span -----