Package: apt-proxy
Version: 1.9.35-0.3
Severity: normal

When running "apt-get update" I see:

Get:1 http://localhost unstable Release.gpg [189B]
Get:2 http://localhost testing Release.gpg [189B]
Get:3 http://localhost stable Release.gpg [378B]
Err http://localhost testing/updates Release.gpg
  Bad header line
Err http://localhost stable/updates Release.gpg
  Bad header line
Ign http://localhost unstable Release
Hit http://localhost testing Release
Hit http://localhost stable Release
99% [Waiting for headers]

At this point You may "waiting" for ever, while there are no tcp
connections to apt-proxy server. What it is doing? I try and get this on
different machines in different networks and different backends servers
-- the same result.

This problem may be solved by removing "debian-security" lines from
apt.sources, but this is not acceptable solution. 


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)
Shell: /bin/sh linked to /bin/bash

Versions of packages apt-proxy depends on:
ii  adduser                       3.102      Add and remove users and groups
ii  bzip2                         1.0.3-6    high-quality block-sorting file co
ii  debconf [debconf-2.0]         1.5.13     Debian configuration management sy
ii  logrotate                     3.7.1-3    Log rotation utility
ii  python                        2.4.4-4    An interactive high-level object-o
ii  python-apt                    0.6.21     Python interface to libapt-pkg
ii  python-central                0.5.13-0.1 register and build utility for Pyt
ii  python-twisted-web            0.6.0-1    An HTTP protocol implementation to

apt-proxy recommends no packages.

-- debconf information:
  apt-proxy/upgrading-v2:
  apt-proxy/upgrading-v2-result:


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to