Repeated on different Linux distro and found I cant do pijul reset
too, I cant get back to 108832
size file.
addition for collection:
$ pijul init p1
$ cd p1
$ cp /bin/date .
$ pijul add date
$ pijul rec -am"."
$ stat date
File: date
Size: 108832 Blocks: 216 IO Block: 4096 regular file
Device: 803h/2051d Inode: 35117381 Links: 1
Access: (0755/-rwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2021-03-31 17:22:05.692018821 +0300
Modify: 2021-03-31 17:22:03.823971177 +0300
Change: 2021-03-31 17:22:03.823971177 +0300
Birth: 2021-03-31 17:21:51.977669013 +0300
$ cksum date
2801912964 108832 date
$ upx date
Ultimate Packer for eXecutables
Copyright (C) 1996 - 2020
UPX 3.96 Markus Oberhumer, Laszlo Molnar & John Reiser Jan 23rd 2020
File size Ratio Format Name
-------------------- ------ ----------- -----------
108832 -> 49364 45.36% linux/amd64 date
Packed 1 file.
$ cksum date
1679261161 49364 date
$ stat date
File: date
Size: 49364 Blocks: 104 IO Block: 4096 regular file
Device: 803h/2051d Inode: 35117375 Links: 1
Access: (0755/-rwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2021-03-31 17:23:12.176714597 +0300
Modify: 2021-03-31 17:22:03.000000000 +0300
Change: 2021-03-31 17:22:50.356158037 +0300
Birth: 2021-03-31 17:22:50.295156481 +0300
$ pijul diff --short
$
Alright, I just fixed this. Once again, thanks!
This allowed me to discover that Windows is using January 1st, 1601 as the reference time for its modification files. I guess the intent is to look like they’re centuries ahead of Unix. Didn’t do the trick for me though…
cargo, alpha.37
.I’ve invented tricky scenario, git-mercurial-darcs detected me and fired.
If remove steps “AAA-ZZZ” pijul
can
detect a file compression-replace too.