Bug#1063077: syslog-ng: identified for time_t transition but no ABI in shlibs

2024-04-09 Thread Shengjing Zhu
On Mon, Apr 8, 2024 at 9:15 PM Attila Szalay wrote: > > Ok. I re-checked the patch and realized that I checked the only wrong > module (the only one which is arch all and not any). > > So my apologies for the fuzz and will apply the patch with the > appropriate changes. > > But here my original

Bug#1063077: syslog-ng: identified for time_t transition but no ABI in shlibs

2024-04-08 Thread Attila Szalay
Ok. I re-checked the patch and realized that I checked the only wrong module (the only one which is arch all and not any). So my apologies for the fuzz and will apply the patch with the appropriate changes. But here my original reply too: I admit that I joined late to this conversation. But my

Bug#1063077: syslog-ng: identified for time_t transition but no ABI in shlibs

2024-04-05 Thread Bernd Zeimetz
Hi Attila, On Fri, 2024-04-05 at 09:47 +0100, Attila Szalay wrote: > Based on https://wiki.debian.org/NonMaintainerUpload, the binNMU > should > be careful I think you are confusing binNMUs and NMUs. See https://wiki.debian.org/binNMU They are handled more or less automatic as soon as a rebuild

Bug#1063077: syslog-ng: identified for time_t transition but no ABI in shlibs

2024-04-05 Thread Attila Szalay
Hello Steve, I do understand your concern about the time_t structure change and I also admit that there are some room of improvement how the syslog-ng package manage the library versioned dependency, but this is not the solution. Based on https://wiki.debian.org/NonMaintainerUpload, the binNMU