Hi,
At Wed, 13 Jul 2011 22:10:47 -0400,
Eric Cooper wrote:
Related question this raises is that whether approx should be caching
such content.
Approx currently spawns an external curl process to download files
from remote repositories. I suspect that the server's network
connection
I found it from here:
/var/cache/approx/volatile/dists/lenny/volatile/main/source/Sources:/HTML
This is a auth request web page from Yahoo BB WiFi service.
OK, if you haven't already done so, just remove that file from your
approx cache.
If you have a lot of source packages in your cache
Hi,
At Wed, 13 Jul 2011 11:25:20 -0400,
Eric Cooper wrote:
I found it from here:
/var/cache/approx/volatile/dists/lenny/volatile/main/source/Sources:/HTML
This is a auth request web page from Yahoo BB WiFi service.
OK, if you haven't already done so, just remove that file from
Related question this raises is that whether approx should be caching
such content.
Approx currently spawns an external curl process to download files
from remote repositories. I suspect that the server's network
connection was via some WiFi portal, and that curl returned the WiFi
Package: approx
Version: 4.5-1+squeeze1
Severity: normal
/etc/cron.weekly/approx:
Failure: malformed line: /html
run-parts: /etc/cron.weekly/approx exited with return code 1
-- System Information:
Debian Release: 6.0.2
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
package approx
found 632978
severity 632978 wishlist
merge 632978 632926
thanks
As I mentioned in private email, this exception is raised when
approx-gc encounters an invalid index file (Packages or Sources
typically) that doesn't conform to the RFC822 format.
I agree that it isn't very
6 matches
Mail list logo
