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

lyx: Version 1.1.4-7 (replaces 1.1.4-6 and -4) uploaded to master



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

Format: 1.6
Date: Thu, 13 Apr 2000 09:34:53 -0400
Source: lyx
Binary: lyx
Architecture: source i386
Version: 1.1.4-7
Distribution: frozen unstable
Urgency: low
Maintainer: Peter S Galbraith <psg@debian.org>
Description: 
 lyx        - High Level Word Processor
Changes: 
 lyx (1.1.4-7) frozen unstable; urgency=low
 .
   * NMU requested by Michael Meskes <meskes@debian.org>
   * Applied patch-1.1.4fix3:
     This patch fixes the following problems in LyX 1.1.4fix2 (these are in
     fact bugs of LyX 1.1.4 which were not fixed by the 1.1.4fix[12] patches):
 .
     * LyX often crashed after repeated use of the backspace key. This problem
       actually existed since long ago in the program, but did not strike very
       often before version 1.1.4. This is probably the main reason why
       you will want to apply this patch.
     * error insets were not removed correctly, which caused the removal or
       nearby characters in the documents. This is a serious problem too.
     * filenames for images in docbook mode were truncated
     * font tags for SGML output were wrong.
     * -lintl was not added on the link list when compiling on system
       which have gettext installed, but not in libc.
     * one header file contained C++ comments, whereas it is compiled with a
       C compiler.
Files: 
 7820521379064ab4f58d7b7de339c2da 606 contrib/text optional lyx_1.1.4-7.dsc
 13d4339053045e8ae7d9e547493f63a2 36790 contrib/text optional lyx_1.1.4-7.diff.gz
 0adbf937ec7f5911baf3270d26101bbb 2405330 contrib/text optional lyx_1.1.4-7_i386.deb

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

iQCVAwUBOPcdjbwVH8jSqROhAQG/NAQAje6MY+zemWHk+FBIXlBi5v80xd9B/p9s
mxRVNZrTTbetnWy8M+jjbxuDO4N2mwosCeUUbI4kA+1YoqSpstkA4CqhXU1RZsfm
GXOjtHiMdcAzsHSFBWJfk3PzhmkRnUW+8EckukXPjvNXyxe3o3+Wb2L8wQDAmPqJ
q9CGh8ddAnA=
=tmFI
-----END PGP SIGNATURE-----


Reply to: