[apt-proxy-users] apt-proxy on sparc broken after sarge -> etch upgrade

[Chris Halls]

On Wednesday 16 May 2007 20:10, andy bezella wrote:
> i noticed a set of resolved bug similar to what i was experiencing
> (#274679, #382078, #322242, #397399, #397403, #398217) and built a new
> deb from svn:
> ii  apt-proxy      1.9.36~svn     Debian archive proxy and partial
> mirror buil

Thanks for testing the svn version!

[...]
> Err http://dvaws3078 sarge/volatile-sloppy/main Packages
>   Connection failed
>
> i have attached my /etc/apt-proxy/apt-proxy-v2.conf file and the
> apt-proxy.log (with debug = all:9 db:0).  please let me know if you
> require any additional information.

The logfile shows:

	  File "/usr/lib/python2.4/site-packages/apt_proxy/packages.py", line 68, in 
open
	    self.packages = shelve.open(self.packagedb_dir+'/packages.db')
	  File "shelve.py", line 234, in open
	    return DbfilenameShelf(filename, flag, protocol, writeback, binary)
	  File "shelve.py", line 215, in __init__
	    Shelf.__init__(self, anydbm.open(filename, flag), protocol, writeback, 
binary)
	  File "anydbm.py", line 80, in open
	    raise error, "db type could not be determined"
	anydbm.error: db type could not be determined

So a packages database file is corrupted. Try 
deleting /var/cache/apt-proxy/.apt-proxy/backends/volatile/packages.db

This looks like a problem that will be present in almost all apt-proxy 
versions. If that solves it I'll see if I can make sure this can't happen 
again.

Chris