Garbage at end of bz2

[GoogleCodeExporter]

This is a problem with the project's web site or the release process, not 
necessarily with the software itself.

What steps will reproduce the problem?
1. Download apktool1.5.2.tar.bz2 from 
https://code.google.com/p/android-apktool/downloads/detail?name=apktool1.5.2.tar
.bz2&can=2&q=
2. tar tf apktool1.5.2.tar.bz2

What is the expected output? What do you see instead?

The file decompresses correctly, but then bzip2 prints:
bzip2: (stdin): trailing garbage after EOF ignored

What version of the product are you using? On what operating system?

This happens to all apktool*.bz2 on the project's Downloads page starting with 
version 1.4.5.  1.4.3 does not have this problem.

Please provide any additional information below.

The file was correctly downloaded.  I checked the SHA1.
There is a few kb of zeros appended to the file for no apparent reason.
It looks like the file is being padded to some size.

Original issue reported on code.google.com by circuit...@gmail.com on 26 Nov 2013 at 6:09

[GoogleCodeExporter]

Yep, but it won't harm anything. 

Original comment by connor.tumbleson on 26 Nov 2013 at 6:16

• Changed state: Idle

[GoogleCodeExporter]

It makes the file appear to be corrupted when it isn't.  Why is it happening?
Producing spurious warnings is not a good thing.

Original comment by circuit...@gmail.com on 26 Nov 2013 at 6:19

[GoogleCodeExporter]

Yeah, I can create the archives with -j and the warnings will probably go away, 
but those archives have been up there for 2 years and it doesn't cause a 
problem. I'm not going to go back and change all those archives when this 
doesn't affect the binary at all.

At 500,000 downloads no one has reported any problem so it doesn't appear to 
break anything. I've made a note regardless to use -j when creating future 
archives.

Original comment by connor.tumbleson on 26 Nov 2013 at 6:24