Bug#746005: Status of lilypond

2016-10-18 Thread Don Armstrong 
On Tue, 18 Oct 2016, Antonio Ospite wrote:
> However I could reproduce the issue from "make doc-stage-1" with just
> this file:
> 
> ---
> \version "2.19.50"
> 
> \sourcefilename "measure-counter.ly"
> 
> \relative c' {
>   \startMeasureCount
>   \repeat unfold 5 {
> a4 b c d
>   }
>   \stopMeasureCount
> }
> 
> \layout {
>   \context {
> \Staff
> \consists #Measure_counter_engraver
>   }
> }
> ---
> 
> So it looks like this particular issue is triggered by
> scm/scheme-engravers.scm which is where Measure_counter_engraver is
> defined.
> 
> I'll have to learn some more guile to see if I can reduce the test
> case further.

Awesome; this matches with what I saw when I was looking at trying to
debug it.

> The issue from "make doc-stage-1" seems unrelated to that, tho.

Yeah.

Let me know if you figure out what is going on here; I'd love to get
lilypond back into testing.

-- 
Don Armstrong  https://www.donarmstrong.com

The solution to a problem changes the problem.
 -- Peer's Law

Bug#746005: Status of lilypond

2016-10-18 Thread Antonio Ospite 
On Tue, 11 Oct 2016 15:09:57 -0700
Don Armstrong  wrote:

> On Mon, 10 Oct 2016, Antonio Ospite wrote:
> > I tried compiling lilypond with guile-2.0 from Debian unstable, and
> > building the binaries works, and some simple input file worked too.
>
> Yes, but it fails for more complicated input files, as evidenced by the
> failure to build the documentation.
>

I also tried to build the latest code from upstream:

 $ git clone git://git.sv.gnu.org/lilypond.git lilypond.git
 $ cd lilypond.git/
 $ git checkout dev/janneke/wip-guile2
 $ git rebase master
 $ git apply ../lilypond/debian/patches/use_debians_help2man
 $ git apply ../lilypond/debian/patches/support_guile_2
 $ ./autogen.sh --disable-checking --enable-debugging --enable-guile2 
--disable-optimising --prefix=$PWD/build
 $ make && make doc-stage-1

And I get the same result.

> I'm not sure if this is a case of a guile bug or a lilypond bug, though.
> 

I don't know that either.

However I could reproduce the issue from "make doc-stage-1" with just
this file:

---
\version "2.19.50"

\sourcefilename "measure-counter.ly"

\relative c' {
  \startMeasureCount
  \repeat unfold 5 {
a4 b c d
  }
  \stopMeasureCount
}

\layout {
  \context {
\Staff
\consists #Measure_counter_engraver
  }
}
---

So it looks like this particular issue is triggered by
scm/scheme-engravers.scm which is where Measure_counter_engraver is
defined.

I'll have to learn some more guile to see if I can reduce the test
case further.

Also, when looking at the current status, I found that one of the
blockers was about those "Mark procedures"[1,2], and that the bug has been
solved in guile 2.0.12, see [3,4].

The issue from "make doc-stage-1" seems unrelated to that, tho.

Thanks,
   Antonio

[1] https://lists.gnu.org/archive/html/guile-devel/2015-11/msg3.html
[2] https://lists.gnu.org/archive/html/guile-devel/2016-06/msg00024.html
[3] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=19883
[4] 
http://git.savannah.gnu.org/cgit/guile.git/commit/?h=stable-2.0=8dff3af087c6eaa83ae0d72aa8b22aef5c65d65d

-- 
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?

Bug#746005: Status of lilypond

2016-10-12 Thread Don Armstrong 
On Mon, 10 Oct 2016, Antonio Ospite wrote:
> I tried compiling lilypond with guile-2.0 from Debian unstable, and
> building the binaries works, and some simple input file worked too.

Yes, but it fails for more complicated input files, as evidenced by the
failure to build the documentation.

I'm not sure if this is a case of a guile bug or a lilypond bug, though.


-- 
Don Armstrong  https://www.donarmstrong.com

I leave the show floor, but not before a pack of caffeinated Jolt gum
is thrust at me by a hyperactive girl screaming, "Chew more! Do more!"
The American will to consume more and produce more personified in a
stick of gum. I grab it.
 -- Chad Dickerson

Bug#746005: Status of lilypond

2016-10-10 Thread Antonio Ospite 
On Sun, 9 Oct 2016 13:47:43 +0200
"Dr. Tobias Quathamer"  wrote:

> Hi,
> 
> I've just seen your mail to the bug report and wanted to give a short 
> update.
> 
> There's the latest version of lilypond (2.19.48) available in the 
> collab-maint git repository[1], together with some fixes for guile-2.0.
> 
> However, the build fails with guile-2.0, so I cannot upload the package 
> to experimental. I'm not able to fix the build failures.
>

Hi,

I tried compiling lilypond with guile-2.0 from Debian unstable, and
building the binaries works, and some simple input file worked too.

Building the debian packages indeed fails, I tried the
debian-experimental branch with git-buildpackage:

  DIST=sid ARCH=amd64 BUILDER=pbuilder \
gbp buildpackage --git-debian-branch=debian-experimental \
  --git-pbuilder -d

and the failure is in the "doc-stage-1" target.

It can be triggered in a local build with "make && make doc-stage-1".

The last command, the one which fails, is basically this one:

LANG=C $PWD/out/bin/lilypond -V -I .  -dbackend=eps --formats=ps,png,pdf  
-dinclude-eps-fonts -dgs-load-fonts --header=doctitle --header=doctitleca 
--header=doctitlecs --header=doctitlede --header=doctitlees --header=doctitlefr 
--header=doctitlehu --header=doctitleit --header=doctitleja --header=doctitlenl 
--header=doctitlezh --header=texidoc --header=texidocca --header=texidoccs 
--header=texidocde --header=texidoces --header=texidocfr --header=texidochu 
--header=texidocit --header=texidocja --header=texidocnl --header=texidoczh 
-dcheck-internal-types -ddump-signatures -danti-alias-factor=2 -I  "./"  -I  
"$PWD/input/regression"  -I  "$PWD/input/regression" -I "$PWD/out/lybook-db" 
--formats=eps  -deps-box-padding=3.00  -dread-file-list 
-dno-strip-output-dir  
"$PWD/out/lybook-db/snippet-names--3837230955040507853.ly"

Which gives this output before the failure:


---
Processing `.../lilypond/out/lybook-db/d2/lily-6e9bfc0d.ly'
Parsing...
[.../lilypond/out/share/lilypond/current/ly/init.ly
Using `nederlands' note names...
 [.../lilypond/out/lybook-db/d2/lily-6e9bfc0d.ly
  [.../lilypond/out/share/lilypond/current/ly/lilypond-book-preamble.ly]
Renaming input to: `measure-counter.ly']
Interpreting music...
[.../lilypond/out/share/lilypond/current/fonts/otf/emmentaler-20.otf
Replace font name from Emmentaler-20 to Emmentaler-20.][8]
elapsed time: 0.28 seconds
Element count 465 (spanners 24) 
Preprocessing graphical objects...
Grob count 859
[emmentaler-20_7.029296875]
Replace font name from Emmentaler-20 to Emmentaler-20.
Replace font name from Emmentaler-20 to Emmentaler-20.
Replace font name from Emmentaler-20 to Emmentaler-20.
Replace font name from Emmentaler-20 to Emmentaler-20.
Replace font name from Emmentaler-20 to Emmentaler-20.
Replace font name from Emmentaler-20 to Emmentaler-20.
[lilypond_serif_3.068359375]
Replace font name from TeXGyreSchola-Regular to TeXGyreSchola-Regular.
Replace font name from TeXGyreSchola-Regular to TeXGyreSchola-Regular.
Replace font name from TeXGyreSchola-Regular to TeXGyreSchola-Regular.
Replace font name from TeXGyreSchola-Regular to TeXGyreSchola-Regular.
Replace font name from TeXGyreSchola-Regular to TeXGyreSchola-Regular.
Replace font name from TeXGyreSchola-Regular to TeXGyreSchola-Regular.
Replace font name from TeXGyreSchola-Regular to TeXGyreSchola-Regular.
Replace font name from TeXGyreSchola-Regular to TeXGyreSchola-Regular.
Replace font name from TeXGyreSchola-Regular to TeXGyreSchola-Regular.
Replace font name from TeXGyreSchola-Regular to TeXGyreSchola-Regular.
Replace font name from TeXGyreSchola-Regular to TeXGyreSchola-Regular.
Replace font name from TeXGyreSchola-Regular to TeXGyreSchola-Regular.
Calculating line breaks... 
Drawing systems... Backtrace:
In ice-9/boot-9.scm:
 157: 13 [catch #t # ...]
In unknown file:
   ?: 12 [apply-smob/1 #]
In ice-9/eval.scm:
 411: 11 [eval # #]
 432: 10 [eval # #]
In srfi/srfi-1.scm:
 619: 9 [for-each # #]
In ice-9/eval.scm:
 432: 8 [eval # #]
In ice-9/boot-9.scm:
 157: 7 [catch ly-file-failed # 
...]
In unknown file:
   ?: 6 [ly:parse-file "d2/lily-6e9bfc0d.ly"]
   ?: 5 [ly:book-process-to-systems # #< Output_def> ...]
   ?: 4 [ly:side-position-interface::move-to-extremal-staff #]
   ?: 3 [ly:axis-group-interface::width #]
   ?: 2 [ly:grob::stencil-width #]
In ice-9/eval.scm:
 411: 1 [eval # #]
In unknown file:
   ?: 0 [# "2"]

ERROR: In procedure #:
ERROR: Wrong type to apply: #
---


Have you forwarded this upstream?

[...]
> I'm afraid that the next stable release of Debian will not contain 
> lilypond, which is a real pity.
> 

I only tried lilypond once, so I don't think I classify as a user, but I'd
like to have the option to install it from the Debian archives in order
to give it a another quick try in the future.

Thanks,
   Antonio

--

Bug#746005: Status of lilypond

2016-10-09 Thread Dr. Tobias Quathamer 

Hi,

I've just seen your mail to the bug report and wanted to give a short 
update.


There's the latest version of lilypond (2.19.48) available in the 
collab-maint git repository[1], together with some fixes for guile-2.0.


However, the build fails with guile-2.0, so I cannot upload the package 
to experimental. I'm not able to fix the build failures.


Building the development version of lilypond in a Debian stable chroot 
(with guile-1.8) succeeds, so it's definitely a problem of the new guile.


I'm afraid that the next stable release of Debian will not contain 
lilypond, which is a real pity.


Regards,
Tobias

[1] https://anonscm.debian.org/cgit/collab-maint/lilypond.git/



signature.asc
Description: OpenPGP digital signature