Don Armstrong writes:
> This should probably be demoted to a warning and result in @itemx being
> interpreted as an @item and the offending packages fixed.
Hi, Don.
That would certainly help, but still leave three errors to address on
the lilypond side:
out/changes.texi:55: raising the section
Processing control commands:
> clone -1 -2
Bug #707190 [src:lilypond] lilypond: FTBFS with texinfo 5.1
Bug 707190 cloned as bug 707195
> reassign -2 texinfo
Bug #707195 [src:lilypond] lilypond: FTBFS with texinfo 5.1
Bug reassigned from package 'src:lilypond' to 'texinfo'.
No longer marked as foun
Control: clone -1 -2
Control: reassign -2 texinfo
Control: retitle -2 @itemx which does not follow @item should be a warning
instead of an error
Control: found -2 5.1.dfsg.1-2
Control: affects -2 lilypond
Control: severity -2 important
On Tue, 07 May 2013, Aaron M. Ucko wrote:
> Builds of lilypon
Source: lilypond
Version: 2.16.2-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Builds of lilypond against texinfo 5.1 (which recently landed in
unstable) have been failing, as detailed below. Could you please look
into these errors?
Thanks!
-
4 matches
Mail list logo