+lilypond (2.12.3-8) unstable; urgency=low
+
+ * Fix bad Recommends on texlive-latex-base (Closes: #594403)
+ * Ditch useless links (Closes: #522120)
+ * Apply patch from 77c34ddc (Werner Lemberg <wl@gnu.org>)
+ to fix compilation with g++ 4.5 (Closes: #606642).
+ Thanks to Colin Watson for an alternative patch.
+ * Add parts of patch f113bf2f (Benjamin Peterson <benjamin@python.org>)
+ to fix segfaults on invalid engraver names.
+ * Update standards version; no changes
+
+ -- Don Armstrong <don@debian.org> Fri, 06 May 2011 16:39:42 -0700
+
+lilypond (2.12.3-7) unstable; urgency=low
+
+ * Use /dev/stderr instead of /dev/tty (Closes: #574629)
+ * Use py_support to require rebuilds when python's API changes (Closes:
+ #380855)
+ * Properly remove empty /usr/share/info/lilypond directory and replace
+ with symlink
+
+ -- Don Armstrong <don@debian.org> Tue, 24 Aug 2010 15:52:59 -0700
+
+lilypond (2.12.3-6) unstable; urgency=low
+
+ * Fix syntax error in scm/lily.scm. Thanks to dann frazier for pointing
+ out the fix. (Closes: #574629)
+ * Depend on ghostscript (Closes: #575906)
+
+ -- Don Armstrong <don@debian.org> Wed, 31 Mar 2010 20:57:04 -0700
+
+lilypond (2.12.3-5) unstable; urgency=low
+
+ * Its guile that's being used, not MIT scheme; use access? instead of
+ file-writable? (Closes: #572290)
+
+ -- Don Armstrong <don@debian.org> Thu, 04 Mar 2010 23:38:32 -0800
+
+lilypond (2.12.3-4) unstable; urgency=low
+
+ * Scheme uses file-writeable for some reason (Closes: #572290)
+
+ -- Don Armstrong <don@debian.org> Thu, 04 Mar 2010 08:38:33 -0800
+
lilypond (2.12.3-3) unstable; urgency=low
* Use /dev/null if /dev/tty isn't writable (Closes: #572290)