[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#596300: marked as done (unblock: libunistring/0.9.3-3)



Your message dated Mon, 20 Sep 2010 18:28:29 +0200
with message-id <4C978BAD.9070604@dogguy.org>
and subject line Re: Bug#596300: unblock: libunistring/0.9.3-3
has caused the Debian Bug report #596300,
regarding unblock: libunistring/0.9.3-3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
596300: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596300
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: freeze-exception


Please unblock package libunistring 0.9.3-3. This version, relative to
0.9.3-1, the version in unstable until recently, fixes an FTBFS (Bug
#596243) and a typo in the package description (Bug #596243).
Unfortunatly, libunistring 0.9.3-1 has not propagated to testing yet,
due to #519006, which caused the package to fail to build on mips*.
Looking at the upstream changes from 0.9.1 to 0.9.3, one can see that,
although the diff is huge, most of it consists of a buildsystem
(including gnulib) update and a large amount of indenting and
copyright header changes.  This agrees with the upstream NEWS and
ChangeLog entries.

Relevant debian/changelog entries:

libunistring (0.9.3-3) unstable; urgency=low

  * Fix description typo (closes: #596243, thanks to Paul Menzel).

 -- Andreas Rottmann <rotty@debian.org>  Thu, 09 Sep 2010 20:22:45 +0200

libunistring (0.9.3-2) unstable; urgency=low

  * Work around toolchain issue on mipsen by building with -mplt there
    (closes: #595875, thanks to Julien BLACHE).

 -- Andreas Rottmann <rotty@debian.org>  Wed, 08 Sep 2010 21:45:46 +0200

libunistring (0.9.3-1) unstable; urgency=low

  * New upstream release.
  * Switched to dpkg-source 3.0 (quilt) format.
  * Standards-Version 3.8.4 (no changes).

 -- Andreas Rottmann <rotty@debian.org>  Thu, 27 May 2010 19:37:41 +0200

Upstream NEWS:

New in 0.9.3:
* Bug fixes in unistr.h functions:
  - The functions u16_to_u32, u16_to_u8, u8_to_u32, u8_to_u16 now fail when
    the argument is not valid. Previously, they returned a converted string
    where invalid parts were each replaced with U+FFFD.
  - The function u8_mbsnlen now counts an incomplete character at the end
    of the argument string as 1 character. Previously, it could count as 2
    or 3 characters.
  - The return value of the u8_stpncpy, u16_stpncpy, u32_stpncpy functions
    was incorrect.
  - The u8_strcoll, u16_strcoll, u32_strcoll now try harder to give a non-zero
    return value.
* Portability to MacOS X 10.6 and Cygwin 1.7.

New in 0.9.2:
* The function uc_locale_language now uses the locale of the current thread,
  if a thread-specific locale has been set.

unblock libunistring/0.9.3-3

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.35-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



--- End Message ---
--- Begin Message ---
On 20/09/2010 18:23, Julien BLACHE wrote:
> Julien BLACHE <jblache@debian.org> wrote:
> 
> Hi,
> 
>> 0.9.3 is better than 0.9.1 anyway and spent quite some time in unstable
>> already; it only did not make it to Squeeze due to the broken MIPS
>> toolchain.
> 
> Anyone? jcristau told me he had the unblock on his TODO list but he
> also seems pretty busy. libunistring is ready to migrate, so can someone
> unblock it?
> 

Done.

Cheers,

-- 
Mehdi Dogguy مهدي الدڤي
http://dogguy.org/


--- End Message ---

Reply to: