Your message dated Sat, 22 Oct 2005 10:22:49 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#334877: marked as done (lilypond - fails to build)
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)
--------------------------------------
Received: (at submit) by bugs.debian.org; 20 Oct 2005 13:23:01 +0000
>From [EMAIL PROTECTED] Thu Oct 20 06:23:01 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mx02.uni-tuebingen.de [134.2.3.12]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1ESaNo-0006HA-00; Thu, 20 Oct 2005 06:23:01 -0700
Received: from mobilewave.waldi.eu.org (vpn0289.extern.uni-tuebingen.de
[134.2.165.39])
by mx02.uni-tuebingen.de (8.12.3/8.12.3) with ESMTP id j9KDMwp2023638
for <[EMAIL PROTECTED]>; Thu, 20 Oct 2005 15:22:58 +0200
Received: by mobilewave.waldi.eu.org (Postfix, from userid 1000)
id C23FA184F5; Thu, 20 Oct 2005 15:21:27 +0200 (CEST)
Date: Thu, 20 Oct 2005 15:21:27 +0200
From: Bastian Blank <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: lilypond - fails to build
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.11
X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-7; AVE: 6.32.0.8; VDF:
6.32.0.103; host: mx02)
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: lilypond
Version: 2.6.3-4
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of lilypond_2.6.3-4 on debian01 by sbuild/s390 69
[...]
> Processing include: markup-commands.tely
> lilypond-book.py: error: file not found: markup-commands.tely
>
> Traceback (most recent call last):
> File "../../scripts/lilypond-book.py", line 1616, in ?
> main ()
> File "../../scripts/lilypond-book.py", line 1582, in main
> chunks = do_file (file)
> File "../../scripts/lilypond-book.py", line 1489, in do_file
> chunks))
> File "../../scripts/lilypond-book.py", line 1484, in process_include
> return do_file (name)
> File "../../scripts/lilypond-book.py", line 1489, in do_file
> chunks))
> File "../../scripts/lilypond-book.py", line 1484, in process_include
> return do_file (name)
> File "../../scripts/lilypond-book.py", line 1417, in do_file
> input_fullname = find_file (input_filename)
> File "../../scripts/lilypond-book.py", line 629, in find_file
> ly.exit (1)
> File "/build/buildd/lilypond-2.6.3/share/lilypond/2.6.3/python/lilylib.py",
> line 139, in exit
> raise _ ('Exiting (%d)...') % i
> Exiting (1)...
> make[3]: *** [out/lilypond.nexi] Error 1
> make[3]: Leaving directory `/build/buildd/lilypond-2.6.3/Documentation/user'
> make[2]: *** [all] Error 2
> make[2]: Leaving directory `/build/buildd/lilypond-2.6.3/Documentation'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/build/buildd/lilypond-2.6.3'
> make: *** [build-stamp] Error 2
> ******************************************************************************
> Build finished at 20051020-0853
> FAILED [dpkg-buildpackage died]
Bastian
---------------------------------------
Received: (at 334877-done) by bugs.debian.org; 22 Oct 2005 17:22:50 +0000
>From [EMAIL PROTECTED] Sat Oct 22 10:22:50 2005
Return-path: <[EMAIL PROTECTED]>
Received: from vp085189.reshsg.uci.edu (becket.becket.net) [128.195.85.189]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1ETN50-0007BY-00; Sat, 22 Oct 2005 10:22:50 -0700
Received: from tb by becket.becket.net with local (Exim 4.54)
id 1ETN4z-0005Sx-TC; Sat, 22 Oct 2005 10:22:49 -0700
From: Thomas Bushnell BSG <[EMAIL PROTECTED]>
To: Steve Langasek <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: Bug#334877: marked as done (lilypond - fails to build)
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
X-Reply-Permission: Posted or emailed replies to this message constitute
permission for an emailed response.
X-PGP-Fingerprint: 1F0A1E51 63 28 EB DA E6 44 E5 5E EC F3 04 26 4E BF 1A 92
X-Zippy-Says: I represent a sardine!!
Date: Sat, 22 Oct 2005 10:22:49 -0700
In-Reply-To: <[EMAIL PROTECTED]> (Steve Langasek's
message of "Sat, 22 Oct 2005 05:10:47 -0700")
Message-ID: <[EMAIL PROTECTED]>
User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Version: 2.6.3-5
Steve Langasek <[EMAIL PROTECTED]> writes:
>> * debian/rules (build, build-doc): Redirect input from /dev/tty in MAKE
>> invocations. It seems that lilypond assumes that, if stdin is not a
>> terminal, we must be running under a gui. This changes the behavior
>> of the program in several fundamental ways, causing the scripts used
>> for generating documentation to fail. (Closes: #334877)
>
> Er, that doesn't work. Redirecting input from /dev/tty is only meaningful
> if you *have* a tty... which on a buildd, you don't.
I think you'll see that you do (though nothing good and only bad
things happen if you try to read from it). We can't know for sure
until the goddam tetex bug is fixed.
Please don't reopen bugs without actually seeing the problem continue;
just claiming "I know it's there even though I can't see it" creates
extra work for me and you.
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
