Bug#687969: ftp.debian.org: ftp.kr.debian.org began to develop Hash Sum errors.

2012-10-04 Thread Jaeho Shin
2012 at 05:50:33PM -0700, Jaeho Shin wrote: > > On Tue, Oct 2, 2012 at 3:24 PM, Simon Paillard > wrote: > > > On Mon, Oct 01, 2012 at 01:54:10AM -0700, Jaeho Shin wrote: > > > No successful update occurred since 20th Sept ? > > > http://ftp.kr.debian.org/

Bug#687969: ftp.debian.org: ftp.kr.debian.org began to develop Hash Sum errors.

2012-10-02 Thread Jaeho Shin
etwork policy became very strict a while ago and most of the known service ports have been closed. Is it possible to receive ssh triggers on a non-standard port BTW? ~Jaeho On Tue, Oct 2, 2012 at 3:24 PM, Simon Paillard wrote: > Hi, > > On Mon, Oct 01, 2012 at 01:54:10AM -0700, Jaeho

Bug#687969: ftp.debian.org: ftp.kr.debian.org began to develop Hash Sum errors.

2012-10-01 Thread Jaeho Shin
Hi Simon, Sorry for the delay. A few days ago, we have upgraded our ftpsync to a recent one, but forgot to respond. This bug can be closed now, and we'll keep a better eye on the mailing list in the future. ~Jaeho On Tue, Sep 18, 2012 at 3:07 AM, Simon Paillard wrote: > Hello Kaist admins, >

Bug#596348: mirror listing update for ftp.kr.debian.org

2010-09-11 Thread Jaeho Shin
Hi, Thanks for processing our issue so fast. 2010-09-11, 03:57, Simon Paillard 작성: > Hi, > > On Fri, Sep 10, 2010 at 03:52:43PM +, KAIST File Archive Operators wrote: >> Package: mirrors >> Severity: minor >> >> Submission-Type: update >> Site: ftp.kr.debian.org >> Aliases: ftp.kaist.ac.k

Bug#421333: mirror submission for ftp.kr.debian.org

2007-05-02 Thread Jaeho Shin
[...] Yes, we are using a similar script tailored to our system. It is using those two options with the two stage rsyncs. After having a look at anonftpsync, I decided to merge some new tweaks, e.g. sync'ing only pool/ for the first phase. Thanks for pointing out those changes again.

Bug#358313: ftp.debian.org: Korean mirror unstable

2006-10-12 Thread Jaeho Shin
Simon Paillard wrote: [...] > To ftp.kr.d.o (aka ftp.kaist.ac.kr) admins: > Could you investigate this issue ? Is there a limit concerning the > number of clients or something else ? I believe such errors were due to our poor machine at that moment. We switched to a much more powerful and stable h