#include
* M. Vefa Bicakci [Mon, Jul 05 2010, 09:21:25PM]:
> HTTP/1.1 206 Partial Response
>
> Content-Length: 64360088989315
>
> Content-Range: bytes
> 17496580076480779--5224466291009740840/-5314247457217970159
Yeah, that's the thing that apt-get should have displayed from the start
instead
On 04/07/10 07:02 PM, Eduard Bloch wrote:
> #include
> * M. Vefa Bicakci [Sun, Jul 04 2010, 03:15:21PM]:
Hello!
>
>> [snip]
>> Here are a few sample lines from apt-cacher.err:
>>
>> ===
>> Sun Jul 4 15:03:40
>> 2010|/var/cache/apt-cacher-ng/debrep/dists/unstable/Release storage error
>> [503
#include
* M. Vefa Bicakci [Sun, Jul 04 2010, 03:15:21PM]:
> After upgrading apt-cacher-ng from 0.4.7-1 to 0.4.8-1, I noticed that
> apt-cacher-ng started to report a lot of 503 errors in
> /var/log/apt-cacher-ng/apt-cacher.err, and apt-get stopped working
> properly with apt-cacher-ng. After I
Package: apt-cacher-ng
Version: 0.4.8-1
Severity: grave
Justification: Package is unusable for its main purpose.
Hello,
After upgrading apt-cacher-ng from 0.4.7-1 to 0.4.8-1, I noticed that
apt-cacher-ng started to report a lot of 503 errors in
/var/log/apt-cacher-ng/apt-cacher.err, and apt-get
4 matches
Mail list logo