Well. This problem somehow disappered. But thanks for making known about 
"debug" option

Now I have found another Problem. When I try to install base system:
debootstrap wheezy /media/disk http://localhost:9999/debian

I get:
Jul 15 14:20:56 localhost kernel: [  225.232030] eth55: no IPv6 routers present
Jul 15 14:21:22 localhost approx[1604]: Connection from 127.0.0.1 port 59311
Jul 15 14:21:22 localhost approx[1604]: Request: GET 
/debian/dists/wheezy/Release
Jul 15 14:21:22 localhost approx[1604]:   User-Agent: Wget/1.12 (linux-gnu)
Jul 15 14:21:22 localhost approx[1604]:   Accept: */*
Jul 15 14:21:22 localhost approx[1604]:   Host: localhost:9999
Jul 15 14:21:22 localhost approx[1604]:   Connection: Keep-Alive
Jul 15 14:21:22 localhost approx[1604]:   cached "file not found"
Jul 15 14:21:22 localhost approx[1604]:   last modified: Fri, 15 Jul 2011 
13:50:14 GMT
Jul 15 14:21:22 localhost approx[1604]:   last verified: Fri, 15 Jul 2011 
13:50:14 GMT
Jul 15 14:21:22 localhost approx[1604]:   => not found (cached)
Jul 15 14:21:22 localhost approx[1604]: Nethttpd: Broken pipe

Or should be this bugreport opened against "debootstrap" package? 

On Thu, 7 Jul 2011 09:52:43 -0400
Eric Cooper <[email protected]> wrote:

> On Thu, Jul 07, 2011 at 02:01:01PM +0200, Marek Straka wrote:
> > Package: approx
> > 
> > --- Please enter the report below this line. ---
> > 
> > I have the same problem. By update is System looking for 
> > /var/cache/approx/debian/dists/wheezy/main/binary-amd64/Packages
> > which is not on my system and I get the error 404.
> > But there is another package:
> > /var/cache/approx/debian/dists/wheezy/main/binary-amd64/Packages.gz
> > 
> > --- System information. ---
> > Architecture: i386
> > Kernel:       Linux 2.6.39-2-686-pae
> 
> Please enable debugging on the approx server ($debug true in
> /etc/approx/approx.conf) and send the relevant part of the server's
> log when this problem occurs.  Thanks.



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

Reply via email to