🎁 On ne peut vraiment pas faire mieux, pas de TVA. pour 'Black Friday' 🎁

Black Friday est également très intéressant pour votre entreprise, il suffit de regarder! Consultez la version en ligne Aujourd'hui et jusqu'au lundi

Processed (with 1 error): forcibly merging 936371 942941

Processing commands for cont...@bugs.debian.org: > forcemerge 936371 942941 Bug #936371 [src:dbus-python] dbus-python: Python2 removal in sid/bullseye Bug #936371 [src:dbus-python] dbus-python: Python2 removal in sid/bullseye Marked as found in versions dbus-python/1.2.12-1. Bug #942941 [src:dbus-

Bug#945797: Package is missing pkg-config metadata file

Package: libmilter-dev Version: 8.15.2-15 The libmilter-dev package does not include a pkg-config metadata file, and so cannot be used out of the box with pkg-config. $ pkg-config --libs milter Package milter was not found in the pkg-config search path. ... Often (usually?) library development f

Bug#945773: [PATCH] Log mi_stop flag on debug level when closing socket

On 28/11/2019 14:00, Andreas Beckmann wrote: > On 28/11/2019 13.39, David Bürgin wrote: >> Given all this, I want to propose changing the log level of this message >> to debug (SMI_LOG_DEBUG), guarded by ‘if (dbg > 0)’ as elsewhere. > > Your reasoning sounds plausible. Can you provide a patch? Su

Bug#945773: Unnecessary debug message logged at info level on shutdown

On 28/11/2019 13.39, David Bürgin wrote: > Given all this, I want to propose changing the log level of this message > to debug (SMI_LOG_DEBUG), guarded by ‘if (dbg > 0)’ as elsewhere. Your reasoning sounds plausible. Can you provide a patch? Andreas

Bug#945773: Unnecessary debug message logged at info level on shutdown

Package: libmilter-dev Version: 8.15.2-15 Every time a milter exits a log message like the following appears in syslog: Nov 26 11:35:22 buster my_milter[13781]: my_milter: mi_stop=1 This message is logged at info level, but it looks like a debug message: it refers to the internal function name ‘