Bug 1148824 - Issues with %clamp_mtime_to_source_date_epoch
Issues with %clamp_mtime_to_source_date_epoch
Status: NEW
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Other
Other Other
: P5 - None : Normal (vote)
: ---
Assigned To: Bernhard Wiedemann
E-mail List
Depends on:
Blocks: 1133809
  Show dependency treegraph
Reported: 2019-08-29 14:42 UTC by Dominique Leuenberger
Modified: 2019-09-11 07:33 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Dominique Leuenberger 2019-08-29 14:42:28 UTC
An issue has appeared since we enabled %clamp_mtime_to_source_date_epoch for openSUSE:Factory, i.e.

The files in the FTP Tree (boot/x86_64/{common,initrd,root) are being built/packaged as part of the package installation-images. Those files frequently change their content, even without i-i changing the changelog (based on depending packages, like yast, kernel, ...)

The files are being extracted out of i-i's generated rpms and published on the FTP Tree. From OBS to download.o.o, rsync is being used to sync the files.

the files are having unmodified mtime though, which makes rsync, in the default config, ignore/skip those files from being resynced, resulting in broken FTP Trees (uninstallable using NET installer)
Comment 1 Dominique Leuenberger 2019-08-30 07:58:22 UTC
%clamp_mtime_to_source_date_epoch has been disabled in openSUSE:Factory for the time being
Comment 2 Bernhard Wiedemann 2019-09-11 07:33:44 UTC
I see some routes to solve this:

1. we could have SOURCE_DATE_EPOCH set by OBS workers for such packages to the date of the newest BuildRequires

This works, because rpm follows the spec in

2. we could adapt the extractor code to touch relevant files

3. we use %if in prjconf to exclude installation-images from %clamp_mtime_to_source_date_epoch