#4386: dbus-1.12.12
--------------------+-----------------------
 Reporter:  bdubbs  |       Owner:  lfs-book
     Type:  task    |      Status:  new
 Priority:  normal  |   Milestone:  8.4
Component:  Book    |     Version:  SVN
 Severity:  normal  |  Resolution:
 Keywords:          |
--------------------+-----------------------

Comment (by bdubbs):

 dbus 1.12.12 (2018-12-04)

 dbus version control is now hosted on freedesktop.org's Gitlab
 installation, and bug reports and feature requests have switched from
 Bugzilla bugs (indicated by "fd.o #nnn") to Gitlab issues ("dbus#nnn")
 and merge requests ("dbus!nnn").

 Enhancements:

 * Reference the freedesktop.org Code of Conduct

 Fixes:

 * Stop the dbus-daemon leaking memory (an error message) if delivering
   the message that triggered auto-activation is forbidden. This is
   technically a denial of service because the dbus-daemon will
   run out of memory eventually, but it's a very slow and noisy one,
   because all the rejected messages are also very likely to have
   been logged to the system log, and its scope is typically limited by
   the finite number of activatable services available.

 * Remove __attribute__((__malloc__)) attribute on dbus_realloc(),
   which does not meet the criteria for that attribute in gcc 4.7+,
   potentially leading to miscompilation

 * Fix some small O(1) memory leaks

 * Fix printf formats for pointer-sized integers on 64-bit Windows

 * Always use select()-based poll() emulation on Darwin-based OSs
   (macOS, etc.) and on Interix, similar to what libcurl does

 * Extend a test timeout to avoid spurious failures in CI

 Tests and CI:

 * Add Travis-CI builds for 64-bit Windows using mingw-w64
 * Add Gitlab-CI integration

--
Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/4386#comment:1>
LFS Trac <http://wiki.linuxfromscratch.org/lfs/>
Linux From Scratch: Your Distro, Your Rules.
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to