OK Sergey, by doing some more tests, I have finally confirmed it that these tar commands are removing milliseconds from the archive.
By testing I mean that I have added in here https://git.yoctoproject.org/poky/tree/meta/classes-global/sstate.bbclass#n847 stupid check: echo "ble ble ble ${SSTATE_PKG} ${SSTATE_BUILDDIR}" >> /media/plobacz/9582beb9-8774-4d4d-976f-63a6f1c87c13/poky-contrib/sstate_pkg.log ls -R --full-time "${SSTATE_BUILDDIR}" >> /media/plobacz/9582beb9-8774-4d4d-976f-63a6f1c87c13/poky-contrib/sstate_pkg.log which produced me the needed output for verification and it looks prety huge but I have found the needed part regarding the acpid packge which is failing and it looks e.g. like this: ble ble ble /media/plobacz/9582beb9-8774-4d4d-976f-63a6f1c87c13/poky-contrib/build/sstate-cache/81/96/sstate:acpid:core2-64-poky-linux:2.0.34:r0:core2-64:11:8196f1f3e3094158d888b6ead4b56624c52fa363d1133c447bfc88398e5f7fc6_package.tar.zst /media/plobacz/9582beb9-8774-4d4d-976f-63a6f1c87c13/poky-contrib/build-st/reproducibleA/tmp/work/core2-64-poky-linux/acpid/2.0.34-r0/sstate-build-package/ ... /media/plobacz/9582beb9-8774-4d4d-976f-63a6f1c87c13/poky-contrib/build-st/reproducibleA/tmp/work/core2-64-poky-linux/acpid/2.0.34-r0/sstate-build-package/packages-split/acpid-src/usr/src/debug/acpid/2.0.34-r0: total 192 -rw-r--r-- 3 root root 10934 2019-07-31 12:21:00.861236271 +0000 acpid.c -rw-r--r-- 3 root root 1670 2018-04-10 23:51:39.467499913 +0000 acpid.h -rw-r--r-- 3 root root 878 2009-04-29 14:37:13.000000000 +0000 acpi_genetlink.h -rw-r--r-- 3 root root 7339 2012-02-16 20:24:42.515701450 +0000 acpi_ids.c -rw-r--r-- 3 root root 1118 2012-02-16 20:24:42.544701444 +0000 acpi_ids.h -rw-r--r-- 3 root root 5264 2015-07-28 22:32:35.499948465 +0000 acpi_listen.c -rw-r--r-- 3 root root 4583 2013-08-15 22:49:18.764134072 +0000 connection_list.c -rw-r--r-- 3 root root 2725 2013-08-15 20:24:07.562169686 +0000 connection_list.h -rw-r--r-- 3 root root 17402 2018-03-29 15:07:23.716843024 +0000 event.c -rw-r--r-- 3 root root 1288 2013-12-19 02:42:46.529591162 +0000 event.h -rw-r--r-- 3 root root 1656 2009-04-29 14:37:13.000000000 +0000 genetlink.h -rw-r--r-- 3 root root 4943 2021-08-29 16:46:00.558827438 +0000 inotify_handler.c -rw-r--r-- 3 root root 1094 2009-11-09 22:03:27.000000000 +0000 inotify_handler.h -rw-r--r-- 3 root root 18544 2022-08-15 14:38:03.122942190 +0000 input_layer.c -rw-r--r-- 3 root root 1257 2009-11-09 23:16:59.000000000 +0000 input_layer.h drwxr-xr-x 2 root root 4096 2022-09-16 01:24:42.000000000 +0000 kacpimon -rw-r--r-- 3 root root 13746 2021-09-20 01:31:56.196781952 +0000 libnetlink.c -rw-r--r-- 3 root root 3028 2021-09-20 01:30:25.930632950 +0000 libnetlink.h -rw-r--r-- 3 root root 1401 2018-03-29 15:08:05.842574608 +0000 log.c -rw-r--r-- 3 root root 1269 2018-03-29 15:08:02.566518016 +0000 log.h -rw-r--r-- 3 root root 6155 2021-09-20 01:32:03.418793923 +0000 netlink.c -rw-r--r-- 3 root root 1066 2009-04-29 14:37:13.000000000 +0000 netlink.h -rw-r--r-- 3 root root 4876 2015-07-28 22:32:35.453948235 +0000 proc.c -rw-r--r-- 3 root root 1066 2012-02-16 20:25:02.924701352 +0000 proc.h -rw-r--r-- 3 root root 5018 2022-09-16 01:24:42.000000000 +0000 sock.c -rw-r--r-- 3 root root 1198 2012-02-16 20:25:02.925701357 +0000 sock.h -rw-r--r-- 3 root root 3007 2016-01-27 16:13:18.836936981 +0000 ud_socket.c -rw-r--r-- 3 root root 352 2012-03-20 23:54:18.929518037 +0000 ud_socket.h Afterwards I have unpacked the /media/plobacz/9582beb9-8774-4d4d-976f-63a6f1c87c13/poky-contrib/build/sstate-cache/81/96/sstate:acpid:core2-64-poky-linux:2.0.34:r0:core2-64:11:8196f1f3e3094158d888b6ead4b56624c52fa363d1133c447bfc88398e5f7fc6_package.tar.zst and it occurs that it has these timestamps removed e.g.: ./package/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 So, we finally have the place were is it happening but question is why? After all, tar fires the posix format by default, so what is happening in here? 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: wtorek, 1 sierpnia 2023 18:19 Do: Sergey Poznyakoff <g...@gnu.org.ua> DW: Paul Eggert <egg...@cs.ucla.edu>; bug-tar@gnu.org <bug-tar@gnu.org> Temat: ODP: posix atime/ctime changes despite mtime being set Hi Sergey again, do these tar commands in here https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.yoctoproject.org%2Fpoky%2Ftree%2Fmeta%2Fclasses-global%2Fsstate.bbclass%23n859&data=05%7C01%7Cp.lobacz%40welotec.com%7C1071886f8ac14985113c08db92ab3859%7C25111a7f1d5a4c51a4ca7f8e44011b39%7C0%7C0%7C638265036321137034%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=TvQVsVnv5d0vYbkQDy3ZVZogZHSzYOw5aHofi0DjfnM%3D&reserved=0<https://git.yoctoproject.org/poky/tree/meta/classes-global/sstate.bbclass#n859> may somehow be removing timestamps? 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: wtorek, 1 sierpnia 2023 16:17 Do: Sergey Poznyakoff <g...@gnu.org.ua> DW: Paul Eggert <egg...@cs.ucla.edu>; bug-tar@gnu.org <bug-tar@gnu.org> Temat: ODP: posix atime/ctime changes despite mtime being set Hi Sergey, I do not know yet how is it happening is this sstate_cache created from previous builds or it uses another archiver, but what I do know is that tar which is in there already got wrong timestamps. I need to investigate it. BR Piotr Od: Sergey Poznyakoff <g...@gnu.org.ua> Wysłane: wtorek, 1 sierpnia 2023 15:39 Do: Piotr Łobacz <p.lob...@welotec.com> DW: Paul Eggert <egg...@cs.ucla.edu>; bug-tar@gnu.org <bug-tar@gnu.org> Temat: Re: posix atime/ctime changes despite mtime being set Hi Piotr, > And this is happening because yocto is using this sstate-cache which > is packing the data into archive with another command, Sorry, I didn't quite get it: do you mean that it uses another archiver, or just gives another set of options to tar? Regards, Sergey
