[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#401336: marked as done (apt: Compressed file ends unexpectedly)

Your message dated Fri, 16 Jan 2009 16:46:22 +0200
with message-id <49709DBE.9030106@gmail.com>
and subject line closing #343557, #401336
has caused the Debian Bug report #343557,
regarding apt: Compressed file ends unexpectedly
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
343557: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343557
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apt
Version: 0.6.46.1
Severity: important

Hi,

I've been seeing this for some time:
Get:6 http://ftp.belnet.be sid/main Packages [4402kB]
50% [5 Packages bzip2 0] [6 Packages 11088/4402kB 0%]               298kB/s 14s
bzip2: Compressed file ends unexpectedly;
        perhaps it is corrupted?  *Possible* reason follows.
bzip2: Inappropriate ioctl for device
        Input file = (stdin), output file = (stdout)

It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.

You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.

Err http://ftp.belnet.be sid/main Packages
  Sub-process bzip2 returned an error code (2)
[...]
91% [7 Sources bzip2 0] [8 Sources 322408/1279kB 25%]            12.3kB/s 1m18s
bzip2: Compressed file ends unexpectedly;
        perhaps it is corrupted?  *Possible* reason follows.
bzip2: Inappropriate ioctl for device
        Input file = (stdin), output file = (stdout)

It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.

You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.

Err http://ftp.belnet.be sid/main Sources
  Sub-process bzip2 returned an error code (2)
Fetched 11.4MB in 3m11s (59.7kB/s)
Failed to fetch http://ftp.belnet.be/debian/dists/sid/main/binary-amd64/Packages.bz2  Sub-process bzip2 returned an error code (2)
Failed to fetch http://ftp.belnet.be/debian/dists/sid/main/source/Sources.bz2  Sub-process bzip2 returned an error code (2)
Reading package lists... Done
W: There are no public key available for the following key IDs:
A70DAF536070D3A1
W: You may want to run apt-get update to correct these problems
E: Some index files failed to download, they have been ignored, or old ones used instead.

But everything seems to be fine.  Running apt-get update again I then get:
# apt-get update
Get:1 http://ftp.belnet.be sid Release.gpg [378B]
Hit http://ftp.belnet.be sid Release
Hit http://ftp.belnet.be sid/main Packages/DiffIndex
Hit http://ftp.belnet.be sid/main Sources/DiffIndex
Fetched 1B in 0s (2B/s)
Reading package lists... Done
W: There are no public key available for the following key IDs:
A70DAF536070D3A1
W: You may want to run apt-get update to correct these problems

This is on an amd64, if this is relevant.


Kurt

--- End Message ---
--- Begin Message --- 
One bug reporter doesn't have this problem anymore, one email unreachable,
others haven't answered. I'm closing this. If anyone experiencing this now,
please reopen.

-- 
Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com
Ukrainian C++ Developer, Debian Maintainer, APT contributor

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: