Re: [Duplicity-talk] no-compression still compresses?

[edgar . soldin]

i see.. so it can be mistaken, cause it only tries to interpret what file type 
it may be?

anyway, sigtar, difftar should be untarable with tar, right? so he could try 
that.

or, just to find out if it compresses: backup a quite big plain text/sql dump 
file.. the resulting volume will be significantly smaller if it really 
compresses although forbidden.

..ede/duply.net

On 06.03.2013 16:27, Michael Terry wrote:
> He means running "file XXX".
> 
> "file" is a standard GNU/unix command to determine what a file actually is 
> (rather than just by filename).
> 
> -mt
> 
> 
> On 6 March 2013 04:18, <address@hidden <mailto:address@hidden>> wrote:
> 
>     On 06.03.2013 03:02, Cory Coager wrote:
>     > I'm using --no-encryption and --no-compression for a backup.  I noticed 
> the files have a .difftar extension instead of .difftar.gz. However, running 
> a file against these shows that they are still gzip'd with max compression.  
> Why is this happening?  Am I missing something?
>     >
>     > I'm using version 0.6.21 from Ubuntu ppa.
> 
> 
>     shouldn't be.. how do you test? what do you mean by " running a file 
> against these "?
> 
>     i wouldn't advise to use --no-compression. afaik it has a bug in 
> restoring currently.. check the launchpadpad bug tracker.
> 
>     ..ede/duply.net <http://duply.net>
> 
>     _______________________________________________
>     Duplicity-talk mailing list
>     address@hidden <mailto:address@hidden>
>     https://lists.nongnu.org/mailman/listinfo/duplicity-talk
> 
> 
> 
> 
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>