On Mon, May 20, 2013 at 11:24 AM, Matt Domsch <m...@domsch.com> wrote:
> On Mon, May 20, 2013 at 11:17 AM, William Smith
> <w_sm...@compusmiths.com>wrote:
>
>> I assume this version for sorting out MD5SUM is going to be in the new
>> release?
>>
>> Thanks!
>>
>> On Oct 17, 2012, at 12:04 PM, matt_dom...@dell.com wrote:
>>
>> > If the file is bigger than the chunk size, you’ll need a version (e.g.
>> from my github merge branch) that stores the real MD5SUM in the metadata,
>> rather than relying on the S3 ETag, which is incorrect if using it to
>> compare the whole file – the S3 ETag only is correct for a single chunk of
>> the file.
>>
>
>
> Yes, these patches are in 1.5.0-alpha already.
>
>
Though I found a bug with them today. We weren't always looking for the
md5 value from the headers where we should - specifically the sync
recursive case without wildcards. This is fixed now in my merge branch.
https://github.com/mdomsch/s3cmd/tree/merge
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
_______________________________________________
S3tools-general mailing list
S3tools-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/s3tools-general
