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

Bug#927958: marked as done ([pre-a] unblock: utf8proc/2.3.0-1)



Your message dated Sun, 28 Apr 2019 07:47:00 +0000
with message-id <562cee4c-1768-4248-4a8f-a9b90dc8386a@thykier.net>
and subject line Re: Bug#927958: [pre-a] unblock: utf8proc/2.3.0-1
has caused the Debian Bug report #927958,
regarding [pre-a] unblock: utf8proc/2.3.0-1
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.)


-- 
927958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927958
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: unblock

Please unblock package utf8proc

(explain the reason for the unblock here)

I'm astonished that the unicode (11.* -> 12.*) transition happend at
such a deep freeze stage. utf8proc is tightly coupled with the
unicode-data version, and the new unicode-data version incured FTBFS:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927941

The simplest way to fix this bug is to bump utf8proc to 2.3.0

(include/attach the debdiff against the package in testing)

According to upstream NEWs/changelog
https://github.com/JuliaStrings/utf8proc/commit/eb39b060e7e518941a912e1f51bae1cc6316f547
And the commit history (97ef668 -> 454f601)
https://github.com/JuliaStrings/utf8proc/commits/master
The major change from 2.2.0 (testing) to 2.3.0 (not yet packaged)
is the support for unicode-data (= 12). There is no breaking change.
So I request an unblock for 2.3.0-1

unblock utf8proc/2.3.0-1

-- System Information:
Debian Release: 10.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--- End Message ---
--- Begin Message ---
Mo Zhou:
> control: tags -1 -moreinfo
> 
> Hi Niels,
> 
> utf8proc 2.3.0-1 has been successfully built by all architectures:
> https://buildd.debian.org/status/package.php?p=utf8proc
> it should be ready to be unblocked.
> 
> On Sat, Apr 27, 2019 at 06:58:00AM +0000, Niels Thykier wrote:
>> Please go ahead with the proposed changes and remove the moreinfo tag
>> once it is in unstable and ready to be unblocked.
>>
>> Thanks,
>> ~Niels
> 

Unblocked, thanks.
~Niels

--- End Message ---

Reply to: