#1025877 ftp.kr.debian.org: rsync fails due to unexpected file

#1025877#5
Date:
2022-12-11 03:22:08 UTC
From:
To:
Dear Maintainer,

Rsyncing from ftp.kr.debian.org:

It got:

rsync: send_files failed to open "pool-alpha/main/b/bustle/.bustle_0.4.8-1_alpha.deb.xRxejE" (in debian-ports): Permission denied (13)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1819) [generator=3.2.3]

So this is one issue when rsyncing from ftp.kr.debian.org.

I try add ftp.kr.debian.org to sources.list, and it reports:
```
Get:1 http://ftp.kr.debian.org/debian-ports sid InRelease [69.6 kB]
Ign:2 http://ftp.kr.debian.org/debian-ports sid/main riscv64 Packages
Get:2 http://ftp.kr.debian.org/debian-ports sid/main riscv64 Packages [24.1 MB]
Err:2 http://ftp.kr.debian.org/debian-ports sid/main riscv64 Packages
  File has unexpected size (24210424 != 24093532). Mirror sync in progress? [IP: 103.22.220.133 80]
  Hashes of expected file:
   - Filesize:24093532 [weak]
   - SHA256:cec887a13152edc30954348f6b59bcfb2f3e8550fec7341c034ea65163725f05
   - MD5Sum:e6e9ac71056693e77022a0c0a9516918 [weak]
  Release file created at: Sat, 10 Dec 2022 07:35:29 +0000
Fetched 69.6 kB in 3s (21.8 kB/s)
Reading package lists... Done
E: Failed to fetch http://ftp.kr.debian.org/debian-ports/dists/sid/main/binary-riscv64/Packages.xz  File has unexpected size (24210424 != 24093532). Mirror sync in progress? [IP: 103.22.220.133 80]
   Hashes of expected file:
    - Filesize:24093532 [weak]
    - SHA256:cec887a13152edc30954348f6b59bcfb2f3e8550fec7341c034ea65163725f05
    - MD5Sum:e6e9ac71056693e77022a0c0a9516918 [weak]
   Release file created at: Sat, 10 Dec 2022 07:35:29 +0000
E: Some index files failed to download. They have been ignored, or old ones used instead.
```

So I guess this problem may have existed for some time.
Could you have a look?  thanks.

#1025877#12
Date:
2023-12-16 01:00:53 UTC
From:
To:
Hello, this is KAIST SPARCS MIRROR manager roul.

We checked that we have few trash files that are from rsync,
and that files become no-permission for rsync daemon account.

We haven't properly identified the cause yet,
so we will check and reply again.

For now on, we will delete no-permission files to solve immediately.

Regards,
Roul