[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Uploaded gettext 0.10.36-1 (m68k) to erlangen



-----BEGIN PGP SIGNED MESSAGE-----

Format: 1.7
Date: Tue,  3 Apr 2001 10:43:23 +0200
Source: gettext
Binary: gettext-doc gettext-base gettext
Architecture: m68k
Version: 0.10.36-1
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon <buildd@q650.biophys.uni-duesseldorf.de>
Changed-By: Santiago Vila <sanvila@debian.org>
Description: 
 gettext    - GNU Internationalization utilities
 gettext-base - GNU Internationalization utilities for the base system
Closes: 28696 38414 38935 41823 52571 52858 56039 69519 85311 87735
Changes: 
 gettext (0.10.36-1) unstable; urgency=low
 .
   * New upstream release. It should fix the following bugs:
   - Documentation is now more accurate (Closes: #28696).
   - DESTDIR is now supported (Closes: #38414, #41823, #52571, #85311).
   - gettextize now prints the right aclocal directory (Closes: #38935, #52858).
   - intl/Makefile.in removes libintl.h upon clean (Closes: #56039).
   - gettextize now checks for $gettext_dir before using it (Closes: #69519).
   - Norwegian Nynorsk is now "nn" (Closes: #87735).
   * Added the file NEWS to the doc directory.
   * Removed build-dependency on texinfo, since the .texi is now untouched.
   * glibc >= 2.2 is now required for the build, to avoid the creation of
     a shared libintl library with features not included in libc.
   * No more ./configure --with-included-gettext. This is also required
     to avoid the shared library.
Files: 
 63bcf81eab47aa16ecc64942773302cb 94032 base standard gettext-base_0.10.36-1_m68k.deb
 363bf63b8386f784d28df7a1d7e13f45 348384 devel optional gettext_0.10.36-1_m68k.deb

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQCVAwUBOsroNG547I3m3eHJAQHUnQP/b9xNYpYlc0rnV94TBf44O2rjFVd0VWPV
2w29E1tRtcDAqTGWVaZW+NISggJtW9o2RqT9cUf+EQg6IeN31aZMXZOGk4Yqnwg/
NQPOd+jKq/vBff3n43uQm+pEMFq0wYRUrla7M3z9QwEt3gN5BRVGx2UGuSpOOO4I
8bnjx7YxxxY=
=VUIP
-----END PGP SIGNATURE-----



Reply to: