Hi,
I'm seeking permission/advice on uploading unicode-data 17.0.0 to unstable.
This is not a standard transition; a number of packages need rebuilding
and in some cases new versions, but there is no BEN file or easy way to
write one.
I propose that for each affected package, Built-Using: ${Built-Using}
should be present.
To the best I can discover (thanks everyone), the following packages are
affected and need to be rebuilt:
(See https://salsa.debian.org/debian/unicode-data/-/wikis/home for a
live note):
* console-data
o Builds ok
* slang2
o Builds ok
* fntsample
o Builds ok
* gucharmap
o FTBFS. Needs new 17.0.1 upstream.
* re2
o Builds ok
* python-unicodedata2
o FTBFS. New upstream 17.0.0 builds ok
* meli
o Builds ok
* node-regexpp
o Builds ok
* courier-unicode
o Builds ok
* golang-github-mattn-go-runewidth
o FTBFS. New upstream 0.0.19 also doesn't trivially build, has
missing dependencies
o #1122257 <https://bugs.debian.org/1122257>
* libxmlada
<https://salsa.debian.org/debian/libxmlada/-/blob/debian/master/debian/README>
o FTBFS. New upstream 26.0.0. FTBFS with unicode 16 already:
|raised ADA.ASSERTIONS.ASSERTION_ERROR : file name too long:
Tangut_Components_Supplement|
* node-unicode-data
o Builds package node-unicode-16.0.0 ; builds ok with changes 16 -> 17
* unicode-idna
o Needs to move to upstream 17.0.0; trivial
o Doesn't depend on unicode-data. Merge unicode-idna into
unicode-data?
* unicode-cldr-core
o At v46. Should be updated to v48 for Unicode 17
o Do NMU, Propose merging into unicode-data?
* utf8proc
o 2.10.0 FTBFS, New upstream 2.11.3 works
* wine
o level2. Depends on unicode-idna, unicode-cdlr-core
o FTBFS on unrelated issue