On Tue, May 7, 2013 at 11:22 AM, Randy Melton <[email protected]> wrote:

> I'm even more convinced that this is a bug.
>
> If I edit one of the binary files as follows:
> echo " " >> tclkit-8.5.2-win64.exe.exe
>
> fossil will see the binary as modified.
>
> Is it possible that fossil compresses binaries, and that it doesn't see
> the difference between a compressed binary, and an uncompressed copy if you
> were to uncompress it in place?
>
> thanks,
> randy
>
>
> On Mon, May 6, 2013 at 6:33 PM, Randy Melton <[email protected]> wrote:
>
>> (I apologize if this comes across twice.  I sent it the first time before
>> I had approved the mailinglist menbership.  Since I didn't see it in the
>> archives I'll try this one last time)
>>
>> This seems like a bug, but I assumed I was just doing something wrong...
>> (I googled but couldn't find anything relevant)
>>
>> -----------------(ticket info b391405a01a6e2fa5a15b8c9dc74c69721d9e99f)
>> I started a repository on a win7 box, and added/committed 5 executable
>> files.
>> I got the "... contains binary data..." message and I answered commit
>> anyhow? "a" for all.
>>
>> I cloned the repository on a linux box only to find that the binary
>> executables were gzipped (without the extension).  I unzipped them and can
>> see that they are bigger, but when i try to commit in fossil I get "fossil:
>> nothing has changed".
>>
>> I see that they are bigger, but I can't convince fossil to commit the
>> files?
>> ---------------
>>
>> --------------- (update)
>> I decided to ignore the binary files, and started working in another
>> directory.  I added the new (text) files and got this error when i tried to
>> commit it:
>> Autosync:  https://[email protected]/user/seadevil/repository/frusta
>>                 Bytes      Cards  Artifacts     Deltas
>> Sent:             130          1          0          0
>> Received:         400          8          0          0
>> Total network traffic: 349 bytes sent, 0 bytes received
>> New_Version: dc5f5d61a3aa327d790e7e078782858f7a73d30f
>> ERROR: [kits/tclkit-8.5.1-darwin-univ-aqua] is 3828076 bytes on disk but
>> 2482275 in the repository
>> ERROR: [kits/tclkit-8.5.1-linux-x86] is 2180434 bytes on disk but 1472785
>> in the repository
>> ERROR: [kits/tclkit-8.5.2-linux-arm] is 2177577 bytes on disk but 1470298
>> in the repository
>> fossil: working checkout does not match what would have ended up in the
>> repository:  f27a586a65392d98b48b00721ec8894c versus
>> c028939fcae635a6cb1e55fbe1a22ac4
>> ---------------
>>
>>

I don't know for the case of your " tclkit-8.5.2-win64.exe.exe" file, but
for your gzipped files I might have an explanation.

Gzip keep original time stamp of the file (when compressing and
uncompressing), Depending on your fossil settings, fossil check
modification time to know if the file as change. In your case, the gzipped
and non-gzipped file have the same name and the same modification time, so
if fossil rely on the modification time, it doesn't know that it change.

If you want to be sure fossil really check if the content change, before to
commit you can do:
   fossil status --sha1sum

or to enable checksum permenently (but can be slower on big repository) do
   fossil set repo-cksum on

-- 
Martin G.
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to