Recent changes to bugs

archives exceeding max limit

Adam Zajac — Sun, 19 Aug 2007 01:11:53 -0000

While testing out the final feature yet to be released, I noticed that archives were being created that were slightly larger than the max size allowed. i.e. This bug entirely defeats the purpose of the program.

I need feedback from people using tarlimit. My tests run on a small number of files with size limits less than 10M. Is this bug occurring when the size limit is in the range of Gigabytes? Is this bug occurring only when files are small, or when they are large as well?

In the meantime, I'm going to be running some tests on two theories. The first is that size() isn't reporting correct numbers. The second is that tar.add() does not block, so the program goes on and reads the size before the previous item is finished being written.

long verbose switch does not function

Adam Zajac — Tue, 24 Jul 2007 00:05:05 -0000

--verbose=N presently does nothing because of an error in the code. This will be fixed with the next release. For the time being, use "-v N" instead.

For example, instead of "--verbose=2" use "-v 2"

failure at size 4.0 GB

bren — Mon, 02 Jul 2007 07:04:13 -0000

hi strider

i used tarlimit on my /home directory
which successfully resulted in a 338MB tar.bz2

i then set it work on /media/hda1 (windows partition)
it failed at exactly 4.0GB which is a bit suspicious given the 4.0 GB limit mentioned in the tar wiki ref you mentioned the other day

see attached

regards

bren