Hi
I would like to plan a transition for unicode-data 16.0.0 -> 17.0.0
Version 17 is now in experimental, and by design this *should* be a
trivial upgrade: the package ships tables of data that should be
extended only, no drop in functionality or change in format.
However see #1113798, a transition is preferred as strict version
locking in some packages (notably utf8proc) causes issues.
I would appreciate advice on how to do this. Some packages have
"Build-Using: " metadata on unicode-data:
$ grep-aptavail -F Built-Using -s Package,Built-Using -r 'unicode-data'
reveals:
* console-data
*
slang2
*
courier-unicode
*
re2
*
python-unicodedata2
*
fntsample
*
gucharmap
But build-rdeps reveals 459 packages have a build-depend on
unicode-data. This seems excessive to rebuild; most are recursive rdeps
and likely false positives, and there is no apparent way to check
beyond forcing all to add "built-using".
Any recommendations?
Best regards
Alastair
--
Alastair McKinstry,
GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5
e:[email protected], im: @alastair:mckinstry.ie
https://mastodon.ie/@amckinstry
