+lilypond (2.1.0-1) unstable; urgency=low
+
+ * New upstream release.
+ * Build-Requires: pfaedit (>= 0.0.20031020-3) to prevent FTBFS on alpha.
+ Thanks to Petter Reinholdtsen for the bug report, and thanks to
+ Peter Hawkins for adopting the PfaEdit package! (Closes: Bug#217216)
+ * Build process used to redirect to /dev/stderr which does not exist in
+ all environments. Upstream replaced it with ">&2" in 1.9.0 in August.
+ Thanks to Daniel Schepler for the bug report. (Closes: #215481)
+ * Added symlink from /usr/share/lilypond/$(VERSION)/fonts/type1 to
+ /usr/share/texmf/fonts/type1/public/lilypond. Thanks to Pedro Kroger
+ and Mats Bengtsson's discussion on the lilypond-devel:
+ http://mail.gnu.org/archive/html/lilypond-devel/2003-10/msg00016.html
+
+ -- Anthony Fok <foka@debian.org> Sat, 25 Oct 2003 19:34:41 +0800
+
+lilypond (1.8.1-1) unstable; urgency=low
+
+ * New upstream release.
+ * Thanks to Jan Nieuwenhuizen for the following fixes:
+ debian/control (Build-Depends): Add flex-old as alternative to flex.
+ Deprecate bison 1.75.
+
+ -- Anthony Fok <foka@debian.org> Wed, 27 Aug 2003 00:24:20 +0800
+
+lilypond (1.8.0-1) unstable; urgency=low
+
+ * New upstream release.
+
+ -- Anthony Fok <foka@debian.org> Wed, 13 Aug 2003 00:23:36 +0800
+
+lilypond (1.7.29-1) unstable; urgency=medium
+
+ * New upstream release, preparing for lilypond-1.8. :-)
+ * stepmake/bin/add-html-footer.py: Use LOGNAME only if it exists.
+ pbuilder unsets LOGNAME and Python returns KeyError.
+ Thanks to Daniel Schepler for the report. (Closes: Bug#193065)
+ * debian/rules: Revert to calling ./configure rather than ./autogen.sh.
+ * An issue with autoconf <= 2.57 and g++ >= 3.3 has been preventing
+ getopt-long.cc from compiling. A workaround was checked in by upstream
+ author Jan Nieuwenhuizen on 2003-06-08, and the fix in aclocal.m4 was
+ backported from 1.7.29. (Closes: Bug#197761)
+ * Mark Brown says 1.7.27 has fixed FTBFS on m86k too. Thanks for the
+ note! (Closes: Bug#200510)
+ * Run dh_scrollkeeper to register *.omf files.
+
+ -- Anthony Fok <foka@debian.org> Fri, 1 Aug 2003 05:40:04 +0800
+
+lilypond (1.6.9-2) unstable; urgency=medium
+
+ * CVS updates as of 2003-04-29. (Thanks, Jan!)
+ * "Empty midi2ly.1" problem has been fixed upstream. (Closes: Bug#181927)
+ * Build-Depends: autoconf2.13 and run autogen.sh in debian/rules
+ to ensure this package passes the auto-build daemons. :-)
+
+ -- Anthony Fok <foka@debian.org> Thu, 1 May 2003 13:18:57 +0800
+
+lilypond (1.6.9-1) unstable; urgency=medium
+
+ * New upstream release with CVS updates as of 2003-04-15.
+ Jan Nieuwenhuizen has backported fixes to deal with build problems
+ with flex (>= 2.5.29).
+ * Rebuild with guile-1.6 packages.
+ * Merged debian/* fixes by upstream author Jan Nieuwenhuizen (Thanks!):
+ - Depend on mftrace (>= 1.0.17-1) instead of pktrace.
+ - Add guile-1.6-dev as alternative dependency to libguile-dev
+ - Bugfix for docdir when with changed package name.
+ - Remove bibtex2html dependencies. (LilyPond has come with its own
+ bib2html for some time now. However, xpmtoppm and pnmtopng from
+ netpbm is still needed - foka)
+ - Remove gcc-3.x/lexer kludge.
+ * midi2ly.1 was empty because help2man calls midi2ly but it couldn't
+ "import midi": python/out/midi.so wasn't built until later. Added
+ a kludge in debian/rules to regenerate midi2ly.1 manually.
+ Thanks to Colin Watson for reporting the bug. (See Bug#181927)
+
+ -- Anthony Fok <foka@debian.org> Mon, 28 Apr 2003 03:50:50 +0800
+
+lilypond (1.6.6-2) unstable; urgency=high
+
+ * Hmm, so /usr/share/texmf/dvips/config is an symlink, and thus
+ /usr/share/lilypond/1.6.6/dvips/lilypond.map conflicts with tetex-base.
+ Let's move it to /etc/texmf/dvips/lilypond.map then, and make it a
+ conffile. Thanks for all the (duplicate) bug reports! ;-)
+ (Closes: Bug#169811, #169812, #169877, #169946)
+
+ -- Anthony Fok <foka@debian.org> Sat, 23 Nov 2002 19:21:04 +0800
+
+lilypond (1.6.6-1) unstable; urgency=medium
+
+ * New upstream release.
+ * Updated Debian section in Documentation/topdocs/INSTALL.texi.
+ * FTBFS bug due to bugs in bison-1.50. Now explicitly Build-Depends
+ on bison << 1:1.50 or >= 1:1.75-1. (Closes: Bug#165662)
+
+ -- Anthony Fok <foka@debian.org> Tue, 22 Oct 2002 02:05:33 +0800
+
+lilypond (1.6.4-1) unstable; urgency=medium
+
+ * New upstream release.
+ * Higher urgency because of memory corruption bugs in previous releases.
+
+ -- Anthony Fok <foka@debian.org> Sun, 22 Sep 2002 01:55:29 +0800
+
+lilypond (1.6.3-1) unstable; urgency=low
+
+ * New upstream release.
+
+ -- Anthony Fok <foka@debian.org> Sat, 21 Sep 2002 11:14:48 +0800
+
+lilypond (1.6.2-1) unstable; urgency=low
+
+ * New upstream release.
+ * Check g++ version and run lexer-gcc-3.1.sh if necessary.
+
+ -- Anthony Fok <foka@debian.org> Tue, 10 Sep 2002 23:37:27 +0800
+
+lilypond (1.6.0-1) unstable; urgency=medium
+
+ * New upstream release.
+ * binary-arch: Changed "DH_OPTIONS=-a" to "DH_OPTIONS=-s" so that
+ dpkg-gencontrol would not 't choke on lilypond1.3 for unlisted
+ architectures. Thanks to Ryan Murray for the report and suggested
+ fix. (Closes: Bug#157766)
+
+ -- Anthony Fok <foka@debian.org> Sun, 25 Aug 2002 11:59:01 +0800
+
+lilypond (1.5.68-2) unstable; urgency=low
+
+ * Oops, I was missing Build-Depends on python-dev. Thanks to LaMont
+ Jones and his hppa build daemon for the report. (Closes: Bug#153402)
+ * lilypond should Depends instead of Recommends tetex-extra.
+ Thanks to Russell Neches for the report. (Closes: Bug#152228)
+ * lilypond-indent.el is now installed in lilypond 1.5.x.
+ Thanks to Christophe Rhodes for the report. (Closes: Bug#139070)
+
+ -- Anthony Fok <foka@debian.org> Thu, 18 Jul 2002 23:41:44 +0800
+
+lilypond (1.5.68-1) unstable; urgency=low
+
+ * New upstream release, gearing up for 1.6.0.
+ * Thanks to upstream author Jan Nieuwenhuizen for updating the Debian
+ package to work with 1.5.68.
+ * As per Jan's suggestion, now Build-Depends: pktrace (>= 1.0.3-1),
+ pfaedit (>= 0.0.20020312-1), autotrace, t1utils
+
+ -- Anthony Fok <foka@debian.org> Wed, 17 Jul 2002 03:20:23 +0800
+
+lilypond (1.4.13-1) unstable; urgency=low
+
+ * New upstream release.
+ * Depends: pktrace
+
+ -- Anthony Fok <foka@debian.org> Mon, 6 May 2002 04:09:32 +0800
+
+lilypond (1.4.12-1) unstable; urgency=high
+
+ * New upstream maintenance release.
+ * Several important fixes (including our bison-related patch added
+ to 1.4.10-1) are included since 1.4.11 this release. (Now, I
+ don't even need to increase teTeX's extra_mem_top, extra_mem_bot
+ or pool_size! :-) Please include in Woody.
+ * Fixed a typo in lilypond-doc package description: typestting ->
+ typesetting. Thanks, Matt Zimmerman! (Closes: Bug#125083)
+
+ -- Anthony Fok <foka@debian.org> Sun, 24 Feb 2002 02:06:15 +0800
+
+lilypond (1.4.10-1) unstable; urgency=high
+
+ * New upstream release.
+ * lilypond failed to build with bison >= 1.30 because bison's output file
+ has been renamed. Applied an upstream fix. (Closes: Bug#133692)
+ * lilypond's documentation also failed to build with the latest
+ tetex or texinfo package. Instead of increasing extra_mem_top and
+ extra_mem_bot, increasing pool_size does the trick.
+
+ -- Anthony Fok <foka@debian.org> Mon, 18 Feb 2002 11:41:31 +0800
+
+lilypond (1.4.9-1) unstable; urgency=high
+
+ * New upstream release.
+ * Oops, libc6-dev is known as libc6.1-dev and libc-dev on some
+ architectures. Fixed Build-Depends so that lilypond can be built
+ on all platforms. Thanks to Colin Watson for reporting the bug.
+ (Closes: Bug#120208)
+
+ -- Anthony Fok <foka@debian.org> Tue, 27 Nov 2001 23:28:11 +0800
+
+lilypond (1.4.8-2) unstable; urgency=high
+
+ * [debian/rules]: Use -s instead of -a so that lilypond would get built
+ on all architectures even when the dummy lilypond1.3 package isn't
+ built. Thanks to Ryan Murray for the report. (Closes: Bug#117622)
+ * Depends on python instead of python-base. The python scripts in
+ lilypond work with old and new Python versions.
+ * Build-Depends on "-z combreloc"-enabled binutils (>= 2.11.92.0.10-2)
+ and libc6-dev (>= 2.2.4-5) so that lily runs faster! :-)
+
+ -- Anthony Fok <foka@debian.org> Sun, 11 Nov 2001 10:45:10 +0800
+
lilypond (1.4.8-1) unstable; urgency=high
* New upstream release. (Closes: Bug#111132)
lilypond (1.4.3-1) unstable; urgency=high
* New upstream release.
- * Urgency high because Lilypond-1.2.17 is too buggy and yet it has
- been stuck in testing forever. Lilypond-1.4.x fixes multiple
+ * Urgency high because LilyPond-1.2.17 is too buggy and yet it has
+ been stuck in testing forever. LilyPond-1.4.x fixes multiple
serious bugs. :-)
* Ah, silly me, lilypond was conflicting against itself! I forgot
to remove this relics during the switch from lilypond1.3 to lilypond.
* Initial Release.
-- Anthony Fok <foka@gpu.srv.ualberta.ca> Wed, 6 Aug 1997 04:40:57 -0600
-
-Local variables:
-mode: debian-changelog
-add-log-mailing-address: "foka@debian.org"
-End:
projects / lilypond.git / blobdiff