Hi,

please upload 16.0 to unstable as this is needed by utf8proc.

best,

werdahias


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

Kernel: Linux 6.12.38+deb13-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: OpenRC (via /run/openrc), PID 1: init
LSM: AppArmor: enabled

- -- no debconf information
-----BEGIN PGP SIGNATURE-----

iIsEARYKADMWIQQUWTv/Sl6/b+DpcW7svtu2B7myvgUCaLdEcBUcd2VyZGFoaWFz
QGRlYmlhbi5vcmcACgkQ7L7btge5sr4umwD/W5XYSkbq2vyYan0lazIrCy692rWn
KAvEXDrVsBZH7cQA/1lepyGA9/0nMjnNJCR3CsYVfDhD4y0e2taOkLqVCCoK
=DkeR
-----END PGP SIGNATURE-----

We believe that the bug you reported is fixed in the latest version of
unicode-data, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1113798@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alastair McKinstry <mckinstry@debian.org> (supplier of updated unicode-data package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Wed, 03 Sep 2025 06:52:17 +0100
Source: unicode-data
Architecture: source
Version: 16.0-2
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry <mckinstry@debian.org>
Changed-By: Alastair McKinstry <mckinstry@debian.org>
Closes: 1113798
Changes:
 unicode-data (16.0-2) unstable; urgency=medium
 .
   * Push to unstable. Closes: 1113798
   * Standards-Version: 4.7.2
Checksums-Sha1:
 4c5960baf39a5b3d58210ab04bed3ab832c2494c 1781 unicode-data_16.0-2.dsc
 db1ca4209d56c3b1a51230ea46507447d8274779 4000 unicode-data_16.0-2.debian.tar.xz
Checksums-Sha256:
 d5aa745fbf94fc0b7de24c36d9b840ccf85730bf472e42f8fafb2f28ce4c593a 1781 unicode-data_16.0-2.dsc
 9def2502c635ce66b4014eaf4dfff6731de11d798d4ba3a4ae0dfcfcf99796e2 4000 unicode-data_16.0-2.debian.tar.xz
Files:
 9403ce8c5004a22f070e6d4ce2e4aef9 1781 misc optional unicode-data_16.0-2.dsc
 84005a33f99ed45915b2cbb6b61b8c3f 4000 misc optional unicode-data_16.0-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmi32A0ACgkQy+a7Tl2a
06UF1BAAo/vWoQT8qr5Ny0eJZnFjr4ZE7KbVRuzt4zGoS1d2wWelVsBVbA5SLQwD
fk/Kbrrmahv7xhZKEuZ8PviGY2MjwC0z6HGjVvJFPAZ5B3Ca+tHbxH3pDsPOcoul
aw6ytpj4UpP4dIsaMxRN0UP3PW+VetKkxmgpTA+TgsIHUH07B18cn+6HrJcMbsgH
JuOAEviH54azLj7vPSyqjX7XaniuEzcy9J7j7Q3jGpmS6AWe70vmmriV/MDLT48+
Kls4mPSElXJ5a/j8coHbwbdJ4bu1BOZsSK3SVuC/wDKSUZ9MCYdFWE369lOxNlOA
SiMZa+f/ImQqkbO3SGRU8Md0LcRp49BW1MbVFZdxUxy6lqkr1Q1zGyoAYy0j7I94
Iit54WNm8C/25z0x3Cyz5AuUgOVJ+gLGaQ0onANyglhFHsYUxNSibbE7+QyQQWQt
JENZsYuwUQvBicMvc/7ju+VXVrbgiajtDoL9LmpYNzPfwesXgzf0uA70ZtbhRMAd
ov00qiZTPUW3hGqMEfJshpOvytuL25ze8urYJ1kp/dyCONXzr9fFbVB9KsZyRbL0
tem232NYMHr+uX5uZK4+s1fGyVy1laxoxS5D4gFElynQYPi8ipzVHREY7zpn9GBE
QeLhmloi76+NE5Z2u/Dyfbmb5qbou0oAiqa/KrmSU4DptuskI4I=
=/HBe
-----END PGP SIGNATURE-----

Hi,

I just wanted to remind you that new major versions of unicode-data
are basically a transition and some coordination is ideal. See
https://wiki.ubuntu.com/DesktopTeam/Emoji#unicode-data_packaging

Here are links to bugs for remaining issues:

- https://bugs.debian.org/1114134 golang-github-mattn-go-runewidth
- https://bugs.debian.org/1114527 wine
- https://bugs.debian.org/1114528 node-unicode-data etc
- https://bugs.debian.org/1114529 libxmlada

In this case, I think uploading unicode-data 16 to Unstable now was
ok, since Unicode 16 is almost a year old and we are at the beginning
of the Debian development cycle. I'm emailing in part because I think
we'll need to coordinate better for Unicode 17 which is being released
upstream in a few days.

Thank you,
Jeremy Bícha