Date: Fri, 9 Oct 2020 22:31:05 +0200
From: Christoph Berg <myon@debian.org>
To: Eddy Garcia <egarcia2506@gmail.com>
Cc: pgsql-pkg-debian@postgresql.org
Subject: Re: About Repository
Message-ID: <20201009203105.GB601234@msg.df7cb.de>
Mail-Followup-To: Christoph Berg <myon@debian.org>,
	Eddy Garcia <egarcia2506@gmail.com>,
	pgsql-pkg-debian@postgresql.org
References: 
 <CA+5yWrTuWCp2ofJs2igZ3R0JX_NQpE4eX9e=Pykk1BGjt7S3sw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CA+5yWrTuWCp2ofJs2igZ3R0JX_NQpE4eX9e=Pykk1BGjt7S3sw@mail.gmail.com>
Precedence: bulk

Re: Eddy Garcia
> package lists... DoneE: Failed to fetch
> http://apt.postgresql.org/pub/repos/apt/dists/buster-pgdg/main/binary-amd64/Packages.bz2
> <http://apt.postgresql.org/pub/repos/apt/dists/buster-pgdg/main/binary-amd64/Packages.bz2>
>  File has unexpected size (203163 != 203575). Mirror sync in progress? [IP:
> 72.32.157.246 80]   Hashes of expected file:    - Filesize:203575 [weak]
> - SHA256:65a862a3af4340330573e703e86f703a08dfacc242c9028a0eebe8caf070fc06
>   - SHA1:0702c6348b93a86180cba9cb20c33f2181ee05ac [weak]    -
> MD5Sum:a15e64edf54cdd09518b92bb369d9ce4 [weak]   Release file created at:
> Thu, 08 Oct 2020 22:04:36 +0000E: Some index files failed to download. They
> have been ignored, or old ones used instead.*
> 
> I need to know if the problem is in my network or the repo itself is faulty,

Hi Ed,

I don't know if it was wrong yesterday, but now everything looks fine:

HEAD http://apt.postgresql.org/pub/repos/apt/dists/buster-pgdg/main/binary-amd64/Packages.bz2
Content-Length: 203575

curl --head --header 'Host: apt.postgresql.org' http://72.32.157.246/pub/repos/apt/dists/buster-pgdg/main/binary-amd64/Packages.bz2
Content-Length: 203575

/srv/apt/repo master $ l dists/buster-pgdg/main/binary-amd64/Packages.bz2
-rw-r--r-- 1 aptuser aptadmin 203575 Oct  9 00:04 dists/buster-pgdg/main/binary-amd64/Packages.bz2

The file is now 22h old, so if you have been getting errors today,
that would be very suspicious of a local problem at your end. Is there
any proxy involved?

Christoph