Hi Adam, Thanks for pointing out the feature freeze, and sorry for forgetting about it :-( I think I will go for option 3, as the bad-free bug can cause program crashes. Once the feature freeze is over, I'll revist the release of 0.4.8. Do we keep this bug open, or shall I simply file a new bug once the time has come?
Thanks, Gertjan On Wed, 22 May 2019 20:40:24 +0200, Adam Borowski <kilob...@angband.pl> wrote: >On Wed, May 22, 2019 at 09:14:11AM +0200, Gertjan Halkes wrote: >> * Package name : libt3highlight >> Version : 0.4.8-1 > >> Changes since the last upload: >> >> * New upstream release. > >Hi! >This upload is targetted at unstable, yet doesn't look like something fit >for a late-freeze update. It is somewhat controversial whether this matters >much for a near-leaf package, but it makes the life of the Release Team >busier, and some people have strong opinions about the issue. > >Thus, I'd propose either: >1. pausing until Buster is released, or >2. uploading to experimental instead, or >3. if you consider it important, isolating just the bad free fix, and > applying it as a patch to 0.4.6 (I don't know how severe the bug is) > > >Meow! >-- >⢀⣴⠾⠻⢶⣦⠀ Latin: meow 4 characters, 4 columns, 4 bytes >⣾⠁⢠⠒⠀⣿⡁ Greek: μεου 4 characters, 4 columns, 8 bytes >⢿⡄⠘⠷⠚⠋ Runes: ᛗᛖᛟᚹ 4 characters, 4 columns, 12 bytes >⠈⠳⣄⠀⠀⠀⠀ Chinese: 喵 1 character, 2 columns, 3 bytes <-- best! >
