First char of some bzip2 files are changed by apt-cacher-ng
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apt-cacher-ng (Ubuntu) |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
Binary package hint: apt-cacher-ng
When running "apt-get update" I get some errors that bzip2 exited with exit code 2.
When downloading the files myself (Sources.bz2 or Packages.bz2) and comparing with files wich are downloaded through apt-cacher-ng I noticed that the first character is changed. The first character should be a "B" (which is typical for bzip-files) but in the file downloaded throught apt-cacher-ng the first char is something like "^@" when I viewed it in vi (when catted the char is invisible). When I changed this char to a "B" I could unpack the file.
I've also noticed I don't have this problem with all files, just with 6 of them. All the files I've checked are empty files.
(why would they be empty?)
Actually, I have seen similar problems appearing out of blue in the last weeks. Right now I am adding some user-friendly debug-reporting code, hopping to be able to track this problem down RSN.
^@ in vim is IIRC a NULL char which looks weird in this context :-(