On Thu, Jan 29, 2026 at 11:09:14PM +0100, Simon Josefsson wrote: > retitle 1101483 please package gettext 0.24, 0.25, 0.26, 1.0 or later version > thanks > > With version 1.0 of gettext release out now, and still somewhat early in > the debian forky release cycle, couldn't we upload gettext 1.0 -- at > least to experimental -- and start working on reporting and documenting > the problems in packages not working with modern gettext? > > What is holding up things here? This bug report could be blocked on > those bugs, to make things more transparent here. > > I suggest that even if there are 40 RC bugs due to packages not working > with gettext 1.0, we should get those reported and start to nudge > maintainers to fix things.
Yes, I agree. The plan I had in mind was to report those bugs as severity:normal while gettext is still somewhere in people.debian.org and see how far we can get providing patches. Have you taken a look at the build logs I have here? https://people.debian.org/~sanvila/build-logs/gettext-0.26/ Could you suggest some text with general hints to fix those bugs? (to put either in the same page or maybe in the wiki). That's really the main thing which is stopping me from starting the process. > It isn't unreasonable to have gettext 1.0 as > a forky release goal IMHO. Are there any known important packages that > for some reason cannot easily be made to work with gettext 1.0? For > some very obscure package failing with 1.0, I wonder if maybe dropping > translation support from that package isn't better than keeping the rest > of Debian stuck on ancient gettext versions. I prefer not to think in terms of tradeoffs. I agree that having a more recent gettext in forky is feasible, I'm just unsure about the text that should be used to report the bugs, and I of course welcome help regarding that. Thanks.
