Hi Sergey, Paul, I have been discussing this issue with Richard from yocto and we now know what is happening.
As I said before, the timestamps are wrong even before creation of packages, meaning: plobacz@latitude:/media/plobacz/9582beb9-8774-4d4d-976f-63a6f1c87c13/poky-contrib$ ls --full-time /media/plobacz/9582beb9-8774-4d4d-976f-63a6f1c87c13/poky-contrib/build-st/reproducibleA/tmp/work/core2-64-poky-linux/acpid/2.0.34-r0/packages-split/acpid-src/usr/src/debug/acpid/2.0.34-r0/ razem 192 -rw-r--r-- 2 plobacz plobacz 10934 2019-07-31 14:21:00.000000000 +0200 acpid.c -rw-r--r-- 2 plobacz plobacz 1670 2018-04-11 01:51:39.000000000 +0200 acpid.h -rw-r--r-- 2 plobacz plobacz 878 2009-04-29 16:37:13.000000000 +0200 acpi_genetlink.h -rw-r--r-- 2 plobacz plobacz 7339 2012-02-16 21:24:42.000000000 +0100 acpi_ids.c -rw-r--r-- 2 plobacz plobacz 1118 2012-02-16 21:24:42.000000000 +0100 acpi_ids.h -rw-r--r-- 2 plobacz plobacz 5264 2015-07-29 00:32:35.000000000 +0200 acpi_listen.c -rw-r--r-- 2 plobacz plobacz 4583 2013-08-16 00:49:18.000000000 +0200 connection_list.c -rw-r--r-- 2 plobacz plobacz 2725 2013-08-15 22:24:07.000000000 +0200 connection_list.h -rw-r--r-- 2 plobacz plobacz 17402 2018-03-29 17:07:23.000000000 +0200 event.c -rw-r--r-- 2 plobacz plobacz 1288 2013-12-19 03:42:46.000000000 +0100 event.h -rw-r--r-- 2 plobacz plobacz 1656 2009-04-29 16:37:13.000000000 +0200 genetlink.h -rw-r--r-- 2 plobacz plobacz 4943 2021-08-29 18:46:00.000000000 +0200 inotify_handler.c -rw-r--r-- 2 plobacz plobacz 1094 2009-11-09 23:03:27.000000000 +0100 inotify_handler.h -rw-r--r-- 2 plobacz plobacz 18544 2022-08-15 16:38:03.000000000 +0200 input_layer.c -rw-r--r-- 2 plobacz plobacz 1257 2009-11-10 00:16:59.000000000 +0100 input_layer.h drwxr-xr-x 2 plobacz plobacz 4096 2022-09-16 03:24:42.000000000 +0200 kacpimon -rw-r--r-- 2 plobacz plobacz 13746 2021-09-20 03:31:56.000000000 +0200 libnetlink.c -rw-r--r-- 2 plobacz plobacz 3028 2021-09-20 03:30:25.000000000 +0200 libnetlink.h -rw-r--r-- 2 plobacz plobacz 1401 2018-03-29 17:08:05.000000000 +0200 log.c -rw-r--r-- 2 plobacz plobacz 1269 2018-03-29 17:08:02.000000000 +0200 log.h -rw-r--r-- 2 plobacz plobacz 6155 2021-09-20 03:32:03.000000000 +0200 netlink.c -rw-r--r-- 2 plobacz plobacz 1066 2009-04-29 16:37:13.000000000 +0200 netlink.h -rw-r--r-- 2 plobacz plobacz 4876 2015-07-29 00:32:35.000000000 +0200 proc.c -rw-r--r-- 2 plobacz plobacz 1066 2012-02-16 21:25:02.000000000 +0100 proc.h -rw-r--r-- 2 plobacz plobacz 5018 2022-09-16 03:24:42.000000000 +0200 sock.c -rw-r--r-- 2 plobacz plobacz 1198 2012-02-16 21:25:02.000000000 +0100 sock.h -rw-r--r-- 2 plobacz plobacz 3007 2016-01-27 17:13:18.000000000 +0100 ud_socket.c -rw-r--r-- 2 plobacz plobacz 352 2012-03-21 00:54:18.000000000 +0100 ud_socket.h plobacz@latitude:/media/plobacz/9582beb9-8774-4d4d-976f-63a6f1c87c13/poky-contrib$ ls --full-time /media/plobacz/9582beb9-8774-4d4d-976f-63a6f1c87c13/poky-contrib/build-st/reproducibleB/tmp/work/core2-64-poky-linux/acpid/2.0.34-r0/packages-split/acpid-src/usr/src/debug/acpid/2.0.34-r0/ razem 192 -rw-r--r-- 3 plobacz plobacz 10934 2019-07-31 14:21:00.861236271 +0200 acpid.c -rw-r--r-- 3 plobacz plobacz 1670 2018-04-11 01:51:39.467499913 +0200 acpid.h -rw-r--r-- 3 plobacz plobacz 878 2009-04-29 16:37:13.000000000 +0200 acpi_genetlink.h -rw-r--r-- 3 plobacz plobacz 7339 2012-02-16 21:24:42.515701450 +0100 acpi_ids.c -rw-r--r-- 3 plobacz plobacz 1118 2012-02-16 21:24:42.544701444 +0100 acpi_ids.h -rw-r--r-- 3 plobacz plobacz 5264 2015-07-29 00:32:35.499948465 +0200 acpi_listen.c -rw-r--r-- 3 plobacz plobacz 4583 2013-08-16 00:49:18.764134072 +0200 connection_list.c -rw-r--r-- 3 plobacz plobacz 2725 2013-08-15 22:24:07.562169686 +0200 connection_list.h -rw-r--r-- 3 plobacz plobacz 17402 2018-03-29 17:07:23.716843024 +0200 event.c -rw-r--r-- 3 plobacz plobacz 1288 2013-12-19 03:42:46.529591162 +0100 event.h -rw-r--r-- 3 plobacz plobacz 1656 2009-04-29 16:37:13.000000000 +0200 genetlink.h -rw-r--r-- 3 plobacz plobacz 4943 2021-08-29 18:46:00.558827438 +0200 inotify_handler.c -rw-r--r-- 3 plobacz plobacz 1094 2009-11-09 23:03:27.000000000 +0100 inotify_handler.h -rw-r--r-- 3 plobacz plobacz 18544 2022-08-15 16:38:03.122942190 +0200 input_layer.c -rw-r--r-- 3 plobacz plobacz 1257 2009-11-10 00:16:59.000000000 +0100 input_layer.h drwxr-xr-x 2 plobacz plobacz 4096 2022-09-16 03:24:42.000000000 +0200 kacpimon -rw-r--r-- 3 plobacz plobacz 13746 2021-09-20 03:31:56.196781952 +0200 libnetlink.c -rw-r--r-- 3 plobacz plobacz 3028 2021-09-20 03:30:25.930632950 +0200 libnetlink.h -rw-r--r-- 3 plobacz plobacz 1401 2018-03-29 17:08:05.842574608 +0200 log.c -rw-r--r-- 3 plobacz plobacz 1269 2018-03-29 17:08:02.566518016 +0200 log.h -rw-r--r-- 3 plobacz plobacz 6155 2021-09-20 03:32:03.418793923 +0200 netlink.c -rw-r--r-- 3 plobacz plobacz 1066 2009-04-29 16:37:13.000000000 +0200 netlink.h -rw-r--r-- 3 plobacz plobacz 4876 2015-07-29 00:32:35.453948235 +0200 proc.c -rw-r--r-- 3 plobacz plobacz 1066 2012-02-16 21:25:02.924701352 +0100 proc.h -rw-r--r-- 3 plobacz plobacz 5018 2022-09-16 03:24:42.000000000 +0200 sock.c -rw-r--r-- 3 plobacz plobacz 1198 2012-02-16 21:25:02.925701357 +0100 sock.h -rw-r--r-- 3 plobacz plobacz 3007 2016-01-27 17:13:18.836936981 +0100 ud_socket.c -rw-r--r-- 3 plobacz plobacz 352 2012-03-21 00:54:18.929518037 +0100 ud_socket.h plobacz@latitude:/media/plobacz/9582beb9-8774-4d4d-976f-63a6f1c87c13/poky-contrib$ And this is happening because yocto is using this sstate-cache which is packing the data into archive with another command, but what we have thought is that it might be useful to have an option in tar for reproducibility test, as Paul already mentioned, to get rid of milliseconds even in posix format. What do you think about that? BR Piotr Od: bug-tar-bounces+p.lobacz=welotec....@gnu.org <bug-tar-bounces+p.lobacz=welotec....@gnu.org> w imieniu użytkownika Piotr Łobacz <p.lob...@welotec.com> Wysłane: poniedziałek, 31 lipca 2023 20:42 Do: Sergey Poznyakoff <g...@gnu.org.ua>; Paul Eggert <egg...@cs.ucla.edu> DW: bug-tar@gnu.org <bug-tar@gnu.org> Temat: Re: posix atime/ctime changes despite mtime being set Ooooo jesus i have discovered it finally. I have verified two different directories which are suppoused to be packed, for this packages in reproducibleA and reproducibleB and to my supprise the difference lies in there from the beginning, even before the creation of this packages with tar command in opkg-build script... Now, I need to investigate it. BR Piotr Wysyłane z aplikacji Outlook dla systemu iOS Od: bug-tar-bounces+p.lobacz=welotec....@gnu.org <bug-tar-bounces+p.lobacz=welotec....@gnu.org> w imieniu użytkownika Piotr Łobacz <p.lob...@welotec.com> Wysłane: Monday, July 31, 2023 8:28:22 PM Do: Sergey Poznyakoff <g...@gnu.org.ua>; Paul Eggert <egg...@cs.ucla.edu> DW: bug-tar@gnu.org <bug-tar@gnu.org> Temat: Re: posix atime/ctime changes despite mtime being set OK, so for the acpid-src package builds has been done and to my suprise the $build_date variable is equal 1663291482 and it is exactly the same for both builds. I am more and more inclined towards Sergey's suggestion that the gormat changes in some magical way, but how? Or maybe some additional parameter is being added which we don't see? Regarda, Piotr Wysyłane z aplikacji Outlook dla systemu iOS Od: bug-tar-bounces+p.lobacz=welotec....@gnu.org <bug-tar-bounces+p.lobacz=welotec....@gnu.org> w imieniu użytkownika Piotr Łobacz <p.lob...@welotec.com> Wysłane: Monday, July 31, 2023 7:47:25 PM Do: Sergey Poznyakoff <g...@gnu.org.ua>; Paul Eggert <egg...@cs.ucla.edu> DW: bug-tar@gnu.org <bug-tar@gnu.org> Temat: Re: posix atime/ctime changes despite mtime being set > Piotr, does that seeseem plausible? No, because it uses hosttools which are on my local machine, but I can add in further tests a print to file with tarformat variable. P.S. Sorry for my long responses but currently the build is running and it takes 10h to reproduce it and during that time my pc is not usable at all, that is why I'm responding from my mobile... BR Piotr
