What is your question?
When I update specific packages in my conan lockfiles, some (but not all) packages also seem to get a different timestamp. I'm not really sure what's the reason for that but the timestamp doesn't seem to have a direct effect on the selection of the packages. I can revert this change and it seems to work just the same.
The problem is that it makes the conan.lock commit/diff really confusing because you can't easily see which packages have been updated because like half the lines are shown as changed.
My question is, if I break something when I revert lines with only timestamp changes and commit only "real" changes? Also, would it be possible to let conan handle that, i.e. not produce these changes if they are not necessary?
I always update dependencies by removing a line from the conan.lock and then use `conan install --lockfile-partial --lockfile-out conan.lock" to fill the missing/updated dependencies. It leads to diffs like this:
diff --git a/conan.lock b/conan.lock
index e69ae8ab7f..ee2f6446ed 100644
--- a/conan.lock
+++ b/conan.lock
@@ -3,71 +3,71 @@
"requires": [
"zstd/1.5.5#93372fe14bb7883bd4de82914e0a1841%1689249462.349",
"zlib/1.3.1#af8f2ef3d8e0fddf1975281d7fe43bf6%1708591455.162",
- "tinyxml2/10.0.0#832c7f8038cef53f6427577d6e66a7a8%1731400416.0090604",
+ "tinyxml2/10.0.0#832c7f8038cef53f6427577d6e66a7a8%1733216584.3397188",
"thrift/0.18.1#bf0953976473103d5b9d8f3e34af81a5%1698137826.215",
"spdlog/1.12.0#0e390a2f5c3e96671d0857bc734e4731%1699279648.352",
- "scope-lite/0.2.0#3d661c43163ac4ebc53ec5e3f9e77490%1703754203.507",
+ "scope-lite/0.2.0#3d661c43163ac4ebc53ec5e3f9e77490%1733216578.6441724",
"lz4/1.9.4#bce1f314775b83c195dffc8e177ff368%1689249470.919",
- "libxcrypt/4.4.36#4b4e8f20794f1997dd59eeed0b7cdcfb%1707731916.225",
+ "libxcrypt/4.4.36#4b4e8f20794f1997dd59eeed0b7cdcfb%1733216574.2219849",
"libsystemd/255.2#69a26bf0a9c934a711e771594f662233%1712156724.283",
"libmount/2.39.2#86fe3f4eeda8a3d5a0752c8d54210a57%1707731904.662",
- "attribute-processing-person/2.3.0@trs/stable#96f617b3ed1cfbe11019b76ef53e7361%1723018424.66",
+ "attribute-processing-person/2.3.1@trs/stable#ec664ef387b6e0208c108dfd586efa17%1730278356.44",
]Have you read the CONTRIBUTING guide?
What is your question?
When I update specific packages in my conan lockfiles, some (but not all) packages also seem to get a different timestamp. I'm not really sure what's the reason for that but the timestamp doesn't seem to have a direct effect on the selection of the packages. I can revert this change and it seems to work just the same.
The problem is that it makes the conan.lock commit/diff really confusing because you can't easily see which packages have been updated because like half the lines are shown as changed.
My question is, if I break something when I revert lines with only timestamp changes and commit only "real" changes? Also, would it be possible to let conan handle that, i.e. not produce these changes if they are not necessary?
I always update dependencies by removing a line from the conan.lock and then use `conan install --lockfile-partial --lockfile-out conan.lock" to fill the missing/updated dependencies. It leads to diffs like this:
Have you read the CONTRIBUTING guide?