Recent changes to bugs

apt-proxy creates empty package directory

Gerry Reno — Mon, 24 May 2010 17:17:57 -0000

On a failed download, apt-proxy will create an empty package directory under /var/cache/apt-proxy/ubuntu/pool/main/ and this in turn will cause failures in debootstrap like:
2010-05-24 12:58:26,642 DEBUG : I: Retrieving console-setup
2010-05-24 12:58:26,899 DEBUG : W: Couldn\'t download package console-setup
2010-05-24 12:58:26,908 DEBUG : I: Retrieving console-terminus
2010-05-24 12:58:27,185 DEBUG : I: Validating console-terminus
2010-05-24 12:58:27,203 DEBUG : I: Retrieving coreutils
2010-05-24 12:58:27,470 DEBUG : W: Couldn\'t download package coreutils

which ultimately breaks the image.

apt-proxy hangs on concurrent connections from clients

Frank Schubert — Wed, 26 Sep 2007 08:35:59 -0000

Hi,

I did test the following:
SRV1: for i in `seq 1 50`; do apt-get update; done
SRV2: for i in `seq 1 50`; do apt-get update; done

When both servers (etch) try to get Release/Release.gpg
apt-proxy hangs.

apt-proxy works fine when only one server is connecting.

apt-proxy version Debian etch 1.9.35-0.3
(I also tried the version in Debian testing (1.9.36) with the same problem.)

The log (debug = all:9 db:0) shows no errors or warnings.

apt-proxy-v2.conf is attached.

Thank you in advance.
Frank

Please update web page to new links (cvs changed)

screenager — Tue, 25 Sep 2007 07:03:11 -0000

Please update the main web page. URLs with "cvs." don't work anymore, therefore it's harder to get README and stuff.

apt-proxy-import fails to read Packages.bz2 files

Lee Begg — Mon, 19 Sep 2005 07:23:33 -0000

From the log:
2005/09/19 18:08 NZST [-] [apt_pkg] No Packages files
available for debian-amd64 backend

From the filesystem:
sleep:/home/aptproxy/debian-amd64/dists/sid/main/binary-amd64#
ls
Packages.bz2

Background:
Recent (sid) apt-get's fetch Packages.bz2 instead of
Packages.gz

Apt-proxy needs to read the Packages.bz2 files. When it
doesn't, apt-proxy-import fails to find any package file
and can not import existing debs.

apt-proxy-import: no suitable backend

Anonymous — Sat, 18 Jun 2005 17:21:15 -0000

Upon updating to Sarge I wanted to minimize mirror
traffic so I attempted
to install and initialize apt-proxy version 2.

Attempting to run apt-proxy-import -i
/var/cachce/apt/archives gave a permissions error. I
changed the shell in /etc/passwd for aptproxy to be
bash, did: su - aptproxy, and attempted to re-run the
above command.

At this point, I was told that every package was being
skipped due to the inability to find a suitable backend.

After searching the bug data base, it appears that this
problem was reported, then reported fixed more than ten
days ago, but it appears to still be in the apt-proxy
package I installed on 2005 Jun 18.

apt-proxy-import chokes on importing a large number of debs

Anonymous — Thu, 11 Nov 2004 21:19:57 -0000

apt-proxy-import chokes on importing a large number of
debs with a /bin/sh: "Argument list too long"

version: apt-proxy-import,v 1.10 2002/04/04 10:49:39
haggai

One solution I tried (which sems to proceed) is to use:
for file in "$directory"/*.deb; do
$DPKG_NAME -k -s
"$APT_PROXY_CACHE/dpkg-name.links" "$file" \ | line_feedback
done

instead of the current:

$DPKG_NAME -k -s "$APT_PROXY_CACHE/dpkg-name.links"
"$directory"/*.deb \ | line_feedback

So this uses one DPKG call per file, instead of the
more efficient but apparently breakable way of doign it
all on one line.

I'm not much of a shell user, so maybe someone else
might have a better solution or point to errors in this
apporach.

(There are other issues that come up using the program
(like it skips a lot of files) but I am not sure if
these are related to this change.

--Paul Fernhout (pdfernhout at kurtz-fernhout.com)

apt-proxy v2 works very bad!!

Anonymous — Mon, 27 Sep 2004 00:03:52 -0000

I'm running Sid on several machines on my network and
I've been using apt-proxy for a long time.
Unfortunateely, since I'm using v2 I've been
experiencing nothing but problems; the latest one is
that, when I try to update the packages from a computer
in the lan, if the package has been already downloaded
before from another computer (so it's in the apt-proxy
cache), then the download is extremely slow (much
slower than downloading the package again from the
internet).

Anyone had experience this behaviour before?

Toshiro.

PS: I'm using version 1.9.18

python2.3 transition breaks apt-proxy v2

Sven Hartge — Wed, 13 Aug 2003 08:21:56 -0000

The recent python2.3 transition breaks apt-proxy v2, it
cannot find apt_pkg any more, since it moved from the
2.2 packages dir to the one from 2.3.

The attached patch makes apt-proxy use python2.3.

failure with "main"

Anonymous — Tue, 29 Apr 2003 18:02:08 -0000

When apt-proxy want's to download the "Packeges.gz" from "Main"
sarge, I get an "set: illegal option -C"
failure in the apt-proxy.log
wget load's the file correct down, but it leaf in the
"Packeges.gz.partial"

download fails with small /tmp

Anonymous — Wed, 26 Feb 2003 02:25:01 -0000

When a package to be downloaded is larger than the available free space on /tmp the download will hang after all free space is filled up. This space is then not freed until apt-proxy-v2 is quit manually.

Example: I apt-get installed openoffice.org via an apt-proxy-v2 machine with a 32Mb tmpfs mount. Didn't fit. lsof /tmp then showed /usr/bin/twistd2.2 having a whole bunch of deleted files open on /tmp. Only killing apt-proxy-v2 would free this up.