sync RPM spec w/ upstream #1871
Conversation
note: back out gcc-15 patch, since it wouldn't apply in any event
| @@ -259,6 +263,10 @@ exit $ret | |||
|
|
|||
|
|
|||
| %changelog | |||
| * Tue Feb 18 2025 Remi Collet <[email protected]> - 1.30.0-2 | |||
There was a problem hiding this comment.
Confirming, do we want to also exclude this changelog entry since it doesn't apply? Or do we only need to apply the minimal changes necessary for CI purposes?
There was a problem hiding this comment.
Yes, we want to leave it in. If we needed to remove it, that would be done via spec.patch. The Evergreen task will download the mongo-c-driver.spec file from downstream and diff it with the one we have vendored. If there is any diff, the task fails (to alert us to the need to sync it). So, we need to have the same (bit-for-bit identical) spec file, and the changes made by spec.patch only need to be functional. The changelog entries mostly don't matter since our snapshot script creates a new changelog entry as part of the task anyways.
note: back out gcc-15 patch, since it wouldn't apply in any event
Evergreen patch build: https://spruce.mongodb.com/task/mongo_c_driver_packaging_rpm_package_build_patch_8422cadd2e9e7734503fa0e675417eea872c4a71_67b51309b6c0f70007349303_25_02_18_23_09_03/logs?execution=0