Sync libbsd 0.4.2-1 (main) from Debian unstable (main)

Bug #1033122 reported by Logan Rosen
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libbsd (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Please sync libbsd 0.4.2-1 (main) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Fixed cross building - LP: #963060
As you can see in the Debian changelog, the package now "supports cross-building natively," which remedies the bug that was originally reported on Launchpad and Debian BTS without needing the debian/rules change in Ubuntu.

Changelog entries since current quantal version 0.3.0-2ubuntu1:

libbsd (0.4.2-1) unstable; urgency=low

  * New upstream release.
  * Disable silent rules, so that build logs get meaningful information.
  * Update debian/copyright file.

 -- Guillem Jover <email address hidden> Wed, 27 Jun 2012 09:41:19 +0200

libbsd (0.4.0-1) unstable; urgency=low

  * New upstream release. (Closes: #668705)
    - Autoconfiscated, supports cross-building natively. (Closes: #665997)
    - Provide endian encoding/decoding inline functions. (Closes: #635377)
    - Provide expand_number(). (Closes: #635379)
    - Ship <nlist.h> under /usr/include/bsd/. (Closes: #634955, #657772)
    - Ship <libutil.h> under /usr/include/bsd/. (Closes: #640895)
    - Fix header protections when using the overlay. (Closes: #630907)
    - Fix .so symlinks to be relative even when the .so.N shared library
      is on a different directory. (Closes: #580372)
    - Remove all deprecated headers and inclusions.
  * Avoid leaving the system w/o an <nlist.h> previously owned by either
    libelfg0-dev or libelf-dev when upgrading from old libsd-dev versions
    which used to Replace them, by restoring <nlist.h> from <bsd/nlist.h>.

 -- Guillem Jover <email address hidden> Tue, 29 May 2012 08:11:13 +0200

Revision history for this message
Benjamin Drung (bdrung) wrote :

libbsd 0.4.2-1 was synced yesterday.

Changed in libbsd (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.