<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to bugs</title><link href="https://sourceforge.net/p/tarlimit/bugs/" rel="alternate"/><link href="https://sourceforge.net/p/tarlimit/bugs/feed.atom" rel="self"/><id>https://sourceforge.net/p/tarlimit/bugs/</id><updated>2007-08-19T01:11:53Z</updated><subtitle>Recent changes to bugs</subtitle><entry><title>archives exceeding max limit</title><link href="https://sourceforge.net/p/tarlimit/bugs/3/" rel="alternate"/><published>2007-08-19T01:11:53Z</published><updated>2007-08-19T01:11:53Z</updated><author><name>Adam Zajac</name><uri>https://sourceforge.net/u/strider1551/</uri></author><id>https://sourceforge.neta4198f6e4b57ab47a7818bcd873e50d8109b990c</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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?&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>long verbose switch does not function</title><link href="https://sourceforge.net/p/tarlimit/bugs/2/" rel="alternate"/><published>2007-07-24T00:05:05Z</published><updated>2007-07-24T00:05:05Z</updated><author><name>Adam Zajac</name><uri>https://sourceforge.net/u/strider1551/</uri></author><id>https://sourceforge.net177ac6f3d82113e95ad367ed8651f1f96ee5b595</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;--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.&lt;/p&gt;
&lt;p&gt;For example, instead of "--verbose=2" use "-v 2"&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>failure at size 4.0 GB</title><link href="https://sourceforge.net/p/tarlimit/bugs/1/" rel="alternate"/><published>2007-07-02T07:04:13Z</published><updated>2007-07-02T07:04:13Z</updated><author><name>bren</name><uri>https://sourceforge.net/u/brenubuntu/</uri></author><id>https://sourceforge.net1998557c4ea628e4bb931c36589a07c170b1d67e</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;hi strider&lt;/p&gt;
&lt;p&gt;i used tarlimit on my /home directory &lt;br /&gt;
which successfully resulted in a 338MB tar.bz2&lt;/p&gt;
&lt;p&gt;i then set it work on /media/hda1 (windows partition)&lt;br /&gt;
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&lt;/p&gt;
&lt;p&gt;see attached&lt;/p&gt;
&lt;p&gt;regards&lt;/p&gt;
&lt;p&gt;bren&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>