Re: Strange error with sarge tree: server returned error 400: HTTP/1.1 400 Bad Request

To: Martin Michlmayr <tbm@cyrius.com>
Cc: debian-boot@lists.debian.org
Subject: Re: Strange error with sarge tree: server returned error 400: HTTP/1.1 400 Bad Request
From: Joey Hess <joeyh@debian.org>
Date: Sun, 19 Dec 2004 17:30:22 -0500
Message-id: <[🔎] 20041219223022.GB20777@kitenet.net>
Mail-followup-to: Martin Michlmayr <tbm@cyrius.com>, debian-boot@lists.debian.org
In-reply-to: <[🔎] 20041219214146.GA9313@deprecation.cyrius.com>
References: <[🔎] 20041219214146.GA9313@deprecation.cyrius.com>

Martin Michlmayr wrote:
> I updated my mipsel dailys today and thought I'd switch from trunk to
> sarge.  Unfortunately, this didn't work very well.  When I boot the
> sarge daily image on mipsel/cobalt, I get errors when it tries to
> download .udebs.  syslog shows:
> 
> Jan  1 00:01:10 anna[791]: wget:
> Jan  1 00:01:10 anna[791]: server returned error 400: HTTP/1.1 400 Bad Request^$
> Jan  1 00:01:10 anna[791]:
> Jan  1 00:01:16 anna[791]: WARNING **: bad d-i Packages file

This is probably due to the bug in net-retriever (1.02), fixed in 1.03.

-- 
see shy jo

Attachment: signature.asc
Description: Digital signature

Reply to:

Follow-Ups:
- Re: Strange error with sarge tree: server returned error 400: HTTP/1.1 400 Bad Request
  - From: Martin Michlmayr <tbm@cyrius.com>

References:
- Strange error with sarge tree: server returned error 400: HTTP/1.1 400 Bad Request
  - From: Martin Michlmayr <tbm@cyrius.com>

Prev by Date: Strange error with sarge tree: server returned error 400: HTTP/1.1 400 Bad Request
Next by Date: Re: trying to create a custom sarge isntaller
Previous by thread: Strange error with sarge tree: server returned error 400: HTTP/1.1 400 Bad Request
Next by thread: Re: Strange error with sarge tree: server returned error 400: HTTP/1.1 400 Bad Request
Index(es):
- Date
- Thread