Bug#1064311: rdkit: NMU diff for 64-bit time_t transition
Hi, On Wed, 24 Apr 2024 23:57:17 +0200 Chris Hofstaedtler wrote:> An upload with t64 binaries is required as soon as possible. Given the packages have to go to binary-NEW, you must upload with binaries, and then probably follow up with a source-only upload once they are ACCEPTed. t64 binaries for rdkit got accepted to experimental. Should I upload it to unstable, or should I wait for someone else to do that? Best, Andrius
Bug#1064311: rdkit: NMU diff for 64-bit time_t transition
Hi Chris, On 2024-04-25 00:57, Chris Hofstaedtler wrote: t64 is already in unstable and making its way to testing. So you are a bit late with getting rdkit fixed for t64. An upload with t64 binaries is required as soon as possible. Given the packages have to go to binary-NEW, you must upload with binaries, and then probably follow up with a source-only upload once they are ACCEPTed. Thanks for the information. I will upload rdkit ASAP. Best, Andrius
Bug#1064311: rdkit: NMU diff for 64-bit time_t transition
On Wed, Apr 24, 2024 at 09:25:29AM +0300, Andrius Merkys wrote: > Hi, > > On Mon, 19 Feb 2024 21:35:16 + Steve Langasek > wrote:> Since turning on 64-bit time_t is being handled centrally through a > change > > to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is > > important that libraries affected by this ABI change all be uploaded close > > together in time. Therefore I have prepared a 0-day NMU for rdkit > > which will initially be uploaded to experimental if possible, then to > > unstable after packages have cleared binary NEW. > > > > Please find the patch for this NMU attached. > > It is most likely my fault this has not been resolved yet - by uploading > 202309.3-3 I trashed 202309.3-2.1~exp1. Am I right that I should reupload > rdkit with t64 binaries to experimental now? t64 is already in unstable and making its way to testing. So you are a bit late with getting rdkit fixed for t64. An upload with t64 binaries is required as soon as possible. Given the packages have to go to binary-NEW, you must upload with binaries, and then probably follow up with a source-only upload once they are ACCEPTed. Chris
Bug#1064311: rdkit: NMU diff for 64-bit time_t transition
Hi, On Mon, 19 Feb 2024 21:35:16 + Steve Langasek wrote:> Since turning on 64-bit time_t is being handled centrally through a change to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is important that libraries affected by this ABI change all be uploaded close together in time. Therefore I have prepared a 0-day NMU for rdkit which will initially be uploaded to experimental if possible, then to unstable after packages have cleared binary NEW. Please find the patch for this NMU attached. It is most likely my fault this has not been resolved yet - by uploading 202309.3-3 I trashed 202309.3-2.1~exp1. Am I right that I should reupload rdkit with t64 binaries to experimental now? Andrius