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

Uploaded lilypond 1.0.1-1 (source i386) to masterscp



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

Format: 1.5
Date: Fri, 14 Aug 1998 03:30:05 -0600
Source: lilypond
Binary: lilypond
Architecture: source i386
Version: 1.0.1-1
Distribution: unstable
Urgency: low
Maintainer: Anthony Fok <foka@debian.org>
Description: 
 lilypond   - The GNU Project music typesetter.
Changes: 
 lilypond (1.0.1-1) unstable; urgency=low
 .
   * New upstream release.
   * [aclocal.m4]: Temporarily changed OPTIMIZE="-O2" to OPTIMIZE="-O"
       to avoid egcs (c++) complaint of "Internal compiler error"
       on my computer.
   * [scripts/mudela-book.py]: Added "#!@PYTHON@" at the top.  This string
       expands to "#!/usr/bin/python" in /usr/bin/mudela-book.
       (Thanks to Lintian.  :-)
   * [debian/control]: Recommends: python-base (>= 1.5.1).
       (Again, thanks to Lintian.  :-)
   * [debian/postrm]: Now also removes the generated LilyPond fonts
       *.{tfm,pk} under /var/spool/texmf when called as "postrm remove".
   * [debian/preinst]: Yes, have to bring this back to remove the generated
       LilyPond fonts in /var/spool/texmf because "postrm remove" didn't do
       its jobs in previous versions.  Oops.  :-)
   * [debian/rules]: Installs a few new upstream documentation files, and
       the example files in out/ directories are moved to parent directories.
Files: 
 e11841202bb5dc9fc9ac100f3c9e5c6c 621 tex optional lilypond_1.0.1-1.dsc
 20637dfb8e1a2061aee3db4608658529 759417 tex optional lilypond_1.0.1.orig.tar.gz
 dd6a0b7593aa589202e2893418e89312 6309 tex optional lilypond_1.0.1-1.diff.gz
 9923503c7078c88a582da5021d53bc9f 934926 tex optional lilypond_1.0.1-1_i386.deb

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

iQCVAwUBNdQSUx1nCwXgpaL5AQESCwP9H3CTeeK6BY7+4eeBkdY251vxMdM2LAFi
QMywLsZoKCATvQGcJIsVs0K+r2X51eHAXRy2YIRauQoJtltJ6Qw1yxdV8y2XWfSm
AFV5wJ9mIRikkl7Ln3+ITL3ZC3yO7/93N2wy1BxqtcPxvg4LeOP4j5KrpZD/GLu5
M4jQTOZsjMk=
=H9zS
-----END PGP SIGNATURE-----


Reply to: