Your message dated Sun, 17 Sep 2006 17:02:17 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#359855: fixed in lilypond 2.6.5-1
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: lilypond
Version: 2.6.3-10
Severity: serious

From my pbuilder build log:

...
Processing `out-www/collated-files.tely:1026 (lily-609190913.ly)'
Parsing...
Renaming input to: `font-family-override.ly'
Interpreting music...
Preprocessing graphical objects...
Calculating line breaks... [2]
Writing header field `texidoc' to `lily-609190913.texidoc'...
Writing header field `texidoc' to `lily-609190913.texidoc'...
Writing lily-609190913-systems.tex...
Writing lily-609190913-systems.texi...
Layout output to `lily-609190913-1.eps'...
Layout output to `lily-609190913.eps'...
Converting to PNG...Error: /unregistered in --glyphshow--
Operand stack:

Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--   
--nostringval--   2   %stopped_push   --nostringval--   --nostringval--   
--nostringval--   false   1   %stopped_push   1   3   %oparray_pop   1   3   
%oparray_pop   --nostringval--   1   3   %oparray_pop   1   3   %oparray_pop   
.runexec2   --nostringval--   --nostringval--   --nostringval--   2   
%stopped_push   --nostringval--   --nostringval--   --nostringval--   
--nostringval--   --nostringval--
Dictionary stack:
   --dict:1123/1686(ro)(G)--   --dict:0/20(G)--   --dict:121/200(L)--
Current allocation mode is local
Last OS error: 2
Current file position is 2772390
GPL Ghostscript 8.50: Unrecoverable error, exit code 1

We were called in barnumber 3.
GS exited with status: 256lilypond-book.py: warning: `lilypond' failed (status 
1) (ignored)

lilypond-book.py: error: Process [snip long line] exited unsuccessfully.
Removing `collated-files.texi'
Traceback (most recent call last):
  File "../../scripts/lilypond-book.py", line 1616, in ?
    main ()
  File "../../scripts/lilypond-book.py", line 1599, in main
    ly.exit (1)
  File "/tmp/buildd/lilypond-2.6.3/share/lilypond/2.6.3/python/lilylib.py", 
line 139, in exit
    raise _ ('Exiting (%d)...') % i
Exiting (1)...
make[4]: *** [out-www/collated-files.texi] Error 1
make[4]: Leaving directory `/tmp/buildd/lilypond-2.6.3/input/regression'
make[3]: *** [WWW] Error 2
rm out-www/sakura-sakura.ly out-www/typography-demo.ly out-www/puer-fragment.ly 
out-www/les-nereides.ly out-www/wilhelmus.ly
make[3]: Leaving directory `/tmp/buildd/lilypond-2.6.3/input'
make[2]: *** [WWW] Error 2
make[2]: Leaving directory `/tmp/buildd/lilypond-2.6.3'
make[1]: *** [web] Error 2
make[1]: Leaving directory `/tmp/buildd/lilypond-2.6.3'
make: *** [build-doc-stamp] Error 2
-- 
Daniel Schepler


--- End Message ---
--- Begin Message ---
Source: lilypond
Source-Version: 2.6.5-1

We believe that the bug you reported is fixed in the latest version of
lilypond, which is due to be installed in the Debian FTP archive:

lilypond-data_2.6.5-1_all.deb
  to pool/main/l/lilypond/lilypond-data_2.6.5-1_all.deb
lilypond-doc_2.6.5-1_all.deb
  to pool/main/l/lilypond/lilypond-doc_2.6.5-1_all.deb
lilypond_2.6.5-1.diff.gz
  to pool/main/l/lilypond/lilypond_2.6.5-1.diff.gz
lilypond_2.6.5-1.dsc
  to pool/main/l/lilypond/lilypond_2.6.5-1.dsc
lilypond_2.6.5-1_i386.deb
  to pool/main/l/lilypond/lilypond_2.6.5-1_i386.deb
lilypond_2.6.5.orig.tar.gz
  to pool/main/l/lilypond/lilypond_2.6.5.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Bushnell, BSG <[EMAIL PROTECTED]> (supplier of updated lilypond package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Thu,  7 Sep 2006 22:34:19 -0700
Source: lilypond
Binary: lilypond-data lilypond-doc lilypond
Architecture: source all i386
Version: 2.6.5-1
Distribution: unstable
Urgency: low
Maintainer: Thomas Bushnell, BSG <[EMAIL PROTECTED]>
Changed-By: Thomas Bushnell, BSG <[EMAIL PROTECTED]>
Description: 
 lilypond   - A program for typesetting sheet music
 lilypond-data - LilyPond music typesetter (data files)
 lilypond-doc - LilyPond Documentation in HTML, PS and DVI formats
Closes: 357057 359855 387644
Changes: 
 lilypond (2.6.5-1) unstable; urgency=low
 .
   * New upstream release.  Lilypond 2.8 for Debian is currently stalled
     because guile-1.8 is required for it, and the Debian builds of
     guile-1.8 are encountering bugs.  So let's at least get the last
     lilypond-2.6 into etch in case guile-1.8 doesn't get there in time.
   * stepmake/bin/config.sub, stepmake/bin/config.guess: Use debian
     versions, from autotools-dev 20060702.1.
 .
   * lily/include/accidental-interface.hh (Accidental_interface): Declare
     member accurate_boxes without qualification.
   * lily/include/stem.hh (Stem): Declare member beam_multiplicity without
     qualification.
   * lily/include/slur-scoring.hh (Slur_score_state): Declare member
     generate_avoid_offsets without qualification.
     (Thanks to Martin Michlmayr <[EMAIL PROTECTED]> for the patch.)
     (Closes: #357057, #387644)
 .
   * mf/GNUmakefile (pfa_warning): Select only the first line of mftrace
     --version output for mftrace check, since mftrace now prints more than
     just one line.
 .
   * debian/control (Build-Depends-Indep): Add ttf-bitstream-vera and
     ttf-freefont. (Many thanks to Bill Allombert <[EMAIL PROTECTED]>
     for the fix.) (Closes: #359855)
 .
   * debian/control (Build-Depends): Require at least version 2.4.1-1 of
     libfontconfig1-dev; 2.4.0 was missing FcConfigAppFontAddDir, which we
     need.
 .
   * debian/rules (binary-indep): Don't symlink logos anymore.
Files: 
 17c8ffa11b684ecf1d6e31a9d4964846 1384 tex optional lilypond_2.6.5-1.dsc
 faf24d726b61c92f081ea804f37ef029 2379201 tex optional 
lilypond_2.6.5.orig.tar.gz
 53296466c5572d4d4fb7d059bd7c1025 48113 tex optional lilypond_2.6.5-1.diff.gz
 f99d723b636da7ab1b9a96dd10a169b9 4764804 tex optional 
lilypond-data_2.6.5-1_all.deb
 41476dbaff366a20ab121b38bde6c9c1 17279452 doc optional 
lilypond-doc_2.6.5-1_all.deb
 4cb293ac5f5721d657b346d75575c7d3 1177470 tex optional lilypond_2.6.5-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFFDeBhqMsB9b6fcOoRAolJAKCIwoepfLUAZ5c30NfV6Y1vEjb2KgCgybkW
4Y9bf7+3/15LLVpyuzBd/XE=
=W3ag
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to