upstart 0.5.1 "Unexpected item in bagging area"

Update to libnih 0.2.0

Milestone information

Project:
upstart
Series:
0.5
Version:
0.5.1
Code name:
Unexpected item in bagging area
Released:
 
Registrant:
Scott James Remnant (Canonical)
Release registered:
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon upstart-0.5.1.tar.gz (md5, sig) Upstart 0.5.1 68
last downloaded 39 weeks ago
Total downloads: 68

Release notes 

        * Major rewrite of the memory allocator used by Upstart; the
          old allocator had several limitations and a few issues.
          I must stress that none of the issues were known to affect
          Upstart itself, however it pays to be prudent.

        * An issue where an object in a linked list would be freed after
          the linked list was freed was fixed. Upstart had some twisty
          code logic to work around it, which has now been dropped.

        * An issue where a string could fail to be appended in an OOM
          situation was fixed; if Upstart is affected, this could cause
          D-Bus Introspection data to be corrupted.

        * An issue where multiple socket watches being freed could lead
          to bad memory access has been fixed; Upstart 0.5.0 included a
          temporary fix for the D-Bus connection handling, this replaces
          that with a proper fix that also corrects the same problem for
          timers and other main loop watches that Upstart was not believed
          to be affected by.

        * Compiler warnings when compiling the test suite with -O1 and
          above have been fixed where found.

        * A race condition in the test cases for a process stopping with
          SIGSTOP has been fixed, this could sometimes cause this test
          to hang.

Changelog 

This release does not have a changelog.

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.