On Thu, May 19, 2005 at 02:57:20PM +0200, Santiago Vila wrote: > There is a RC bug in gettext (#307749), which is still unfixed in sarge. > To have it fixed, either 0.14.1-11 or 0.14.4-2 should be allowed in testing. > This is the info from update-excuses: > * gettext_tpu (0.14.1-10 to 0.14.1-11) > + Maintainer: Santiago Vila > + Not touching package, as requested by freeze (contact > debian-release if update is needed) > + NEEDS APPROVAL BY RM > + Not considered > * gettext (0.14.1-10 to 0.14.4-2) > + Maintainer: Santiago Vila > + 13 days old (needed 5 days) > + Not touching package, as requested by freeze (contact > debian-release if update is needed) > + Not considered > I would like to see 0.14.4-2 in sarge because of the changes in 0.14.2-1. > I am well aware that none of the changes is RC by itself, but IMHO, > when considered together, they make the release of gettext in unstable > to be in a much better shape than version 0.14.1-11 in proposed-updates. > > Version 0.14.4 has been in unstable since 14th April, and it is still > a 0.14.x release, so any serious bug it might contain is surely a bug > in the testing version as well (as it happened with Bug #307749 itself). > [ The debdiff tool will probably show a lot of changed lines, but they are > mostly the result of using new auto* tools and the new licensing terms on > a lot of files ]. Well, by all rights 0.14.4-1 ought to have already been in before we froze, so -- accepted. Thanks, -- Steve Langasek postmodern programmer
Attachment:
signature.asc
Description: Digital signature