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

Re: Debian update 出错了



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

li sh 写道:
> 下面是升级的信息:
>
> DecLish:~# aptitude update
> 读取:1 http://mirrors.geekbone.org testing Release.gpg [378B]
> 命中 http://mirrors.geekbone.org testing Release
> 读取:2 http://mirrors.geekbone.org testing/main Packages [4311kB]
> 99% [2 Packages bzip2 7254016]
>
>    102kB/s 0s
> bzip2: Data integrity error when decompressing.
>        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.
>
> 错误 http://mirrors.geekbone.org testing/main Packages
>  子进程 bzip2 返回了一个错误号 (2)
> 已下载 4311kB,耗时 41s (104kB/s)
> 正在读取软件包列表... 完成
> W: 无法获取源软件包列表 http://mirrors.geekbone.org testing/main
> Packages
> (/var/lib/apt/lists/mirrors.geekbone.org_debian_dists_testing_main_binary-i386_Packages)
>
> 的状态 - stat (2 没有那个文件或目录)
> W: 您可能需要运行 apt-get update 来解决这些问题
>
> 这儿是我的源,并且很精简:
>
> DecLish:~# grep -v ^# /etc/apt/sources.list
> deb http://mirrors.geekbone.org/debian/ testing main
>
> 我搜索了一下未果,linuxsir 上也有遇到这种情况,大家遇到过吗,怎么解
> 决呢?
>
    按照我的推断,一个服务器上所有debian的包会做一个列表,然后用bzip2
压缩,再用gnupg签名。我们更新包的时候会先删除本地缓存的列表,然后下载
服务器上最新的列表,再计算有哪些包已经升级或者新出现。然后再根据包列表
中指明的URL来升级包。
    这样的话就有两个问题,bzip2压缩和gnupg签名。我这里也用了
mirrors.geekbone.org的源,也出现了同样问题。不过由于指定了多个镜像,所
以虽然提示出错,但是还能正常使用更新。
deb ftp://debian.cn99.com/debian/ testing main contrib non-free
deb ftp://ftp.linuxforum.net/debian/ testing main contrib non-free
deb ftp://mirrors.geekbone.org/debian/ testing main contrib non-free
    由此看来的话,可能是mirrors.geekbone.org的包列表文件出现了异常。暂
时别用好了。

- --
与其相濡以沫,不如相忘于江湖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFoH2JOhzb4WnHl2oRAi1CAKCh74Ab6OPbnnbOrQbJxNsEdv8PvACfXvDP
y4U1RVcox906ZrLPH7yKpFQ=
=y1Gg
-----END PGP SIGNATURE-----



Reply to: