Hello Michael, > As part of the 64-bit time_t transition required to support 32-bit > architectures in 2038 and beyond > (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified > curl as a source package shipping runtime libraries whose ABI > either is affected by the change in size of time_t, or could not be > analyzed via abi-compliance-checker (and therefore to be on the safe > side we assume is affected).
Can you tell us which case it is? Is it confirmed affected or is this a guess? I know the curl project has put a lot of effort into this issue already but I don't know the specifics enough to understand whether this is a false positive or not. https://daniel.haxx.se/blog/2018/02/01/reducing-2038-problems-in-curl/ https://github.com/curl/curl/issues/2238 > Please find the patch for this NMU attached. > > If you have any concerns about this patch, please reach out ASAP. Although > this package will be uploaded to experimental immediately, there will be a > period of several days before we begin uploads to unstable; so if information > becomes available that your package should not be included in the transition, > there is time for us to amend the planned uploads. The debdiff is reversed, took me a bit to understand it. Does this mean we should hold on pushing new uploads to testing and experimental until this is done? If so, how long will it take? The curl repo is under the debian namespace on salsa, so feel free to push your commits there once the upload is done (debian/experimental branch for experimental). Regards -- Samuel Henrique <samueloph>
