for another release.
--
Don Armstrong http://www.donarmstrong.com
Show me your flowcharts and conceal your tables, and I shall continue
to be mystified. Show me your tables, and I won't usually need your
flowcharts; they'll be obvious.
-- Fredrick P. Brooks Jr., The Mythical
On Sun, 21 Sep 2014, David Kastrup wrote:
Don Armstrong d...@debian.org writes:
What is the current status of #1055[1] (support for Guile 2.0 in
lilypond)?
I'm currently working on it. There is a branch dev/guilev2 with the
current work. Current objective is to make it through the test
On Sun, 21 Sep 2014, Don Armstrong wrote:
OK. I *might* be able to convince the guile maintainer to keep 1.8 just
for lilypond, but that also might mean that I'll end up having to
maintain guile 1.8 too.
Could you point me at a list of guile 2.0 bugs which are affecting
lilypond? Having
On Sun, 21 Sep 2014, David Kastrup wrote:
Don Armstrong d...@debian.org writes:
Could you point me at a list of guile 2.0 bugs which are affecting
lilypond? Having that list handy would help me convince the guile
maintainer (and also Debian's release managers and security
On Sun, 21 Sep 2014, David Kastrup wrote:
Don Armstrong d...@debian.org writes:
Could you point me at a list of guile 2.0 bugs which are affecting
lilypond? Having that list handy would help me convince the guile
maintainer (and also Debian's release managers and security
On Sun, 21 Sep 2014, David Kastrup wrote:
Don Armstrong d...@debian.org writes:
I'm just trying to keep lilypond in Debian.
Yes, that would be very desirable.
So it looks like the guile maintainer is going to be willing to ship
guile 1.8 if lilypond doesn't support guile 2.0. So keep up
, which will likely happen in February at the latest.
Thanks in advance.
1: https://code.google.com/p/lilypond/issues/detail?id=1055
--
Don Armstrong http://www.donarmstrong.com
I will not make any deals with you. I've resigned. I will not be
pushed, filed, stamped, indexed
. I've requested
that texi2html stay around for the time being, but it's likely that this
will only be a viable short-term solution.
--
Don Armstrong http://www.donarmstrong.com
Q: What Can a Thoughtful Man Hope for Mankind on Earth, Given the
Experience of the Past Million
for me is just the licenses of those files;
source I can figure out in most cases.
--
Don Armstrong http://www.donarmstrong.com
[On a trip back from collecting grass seeds in tropical bird stomachs
and being thought by the customs agents to be transporting Marijuana.]
Anyone
#restricted-use
2: http://www.debian.org/logos/openlogo-nd.svg
--
Don Armstrong http://www.donarmstrong.com
We have to face the fact that either all of us are going to die
together or we are going to learn to live together and if we are to
live together we have to talk
On Fri, 28 Dec 2012, David Kastrup wrote:
Don Armstrong d...@debian.org writes:
The attached patch fixes a segfault in mark_smob where s gets
optimized away and garbage collected before m goes out of scope,
leading to a segfault.
There may be other cases of this bug floating around
The attached patch fixes a segfault in mark_smob where s gets
optimized away and garbage collected before m goes out of scope,
leading to a segfault.
There may be other cases of this bug floating around, but I didn't
look particularly hard for them.
Don Armstrong
--
I shall require
On Mon, 01 Oct 2012, Pavel Roskin wrote:
On Thu, 13 Sep 2012 14:51:53 -0700
Don Armstrong d...@debian.org wrote:
While it's correct, you can trivially work around this problem by
changing
#!@PERL@ -w
to
#!@PERL@ -w
#! perl -w
Considering the subsequent discussion, it's
for these programs too, but it's at least a
start.]
Don Armstrong
--
Maybe I did steal your heart
and I am such a perfect criminal
that you never noticed
-- a softer world #481
http://www.asofterworld.com/index.php?id=481
http://www.donarmstrong.com http://rzlab.ucr.edu
.
Don Armstrong
1: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
--
The solution to a problem changes the problem.
-- Peer's Law
http://www.donarmstrong.com http://rzlab.ucr.edu
___
lilypond-devel mailing list
On Tue, 29 May 2012, Colin Campbell wrote:
On 12-05-29 06:02 PM, Don Armstrong wrote:
The following patch fixes an issue which keeps lilypond from building
properly on GCC 4.7. [It's also almost certainly a bug in addition to
this.]
[...]
Don, would you have a look at our outstanding
a/debian/changelog b/debian/changelog
index a4bbb2f..f2cb168 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+lilypond (2.14.2-3) unstable; urgency=low
+
+ * Fix redefinition of s in Music_sequence::first_start. (Closes
+#672087).
+
+ -- Don Armstrong d...@debian.org Sun, 13
of funds
would be handled by SFC or SPI in an open manner.[3] I believe the
overhead for both SPI and SFC are on the order of 5% (though I think
SFC has a non-mandatory overhead), with additional overhead for
transfer fees.
Don Armstrong
1: http://www.spi-inc.org; full disclosure: I'm a Debian
. :(
Would it be reasonable to have it open /dev/null if /dev/tty isn't a
device? [I haven't written much scheme, but assuming that's ok, I can
whip it up later.]
Don Armstrong
--
The trouble with you, Ibid he said, is that you think you're the
biggest bloody authority on everything
-- Terry Pratchet
. :(
Would it be reasonable to have it open /dev/null if /dev/tty isn't a
device? [I haven't written much scheme, but assuming that's ok, I can
whip it up later.]
Don Armstrong
--
The trouble with you, Ibid he said, is that you think you're the
biggest bloody authority on everything
-- Terry Pratchet
I'm building the packages in Debian.]
Don Armstrong
--
Some pirates achieved immortality by great deeds of cruelty or
derring-do. Some achieved immortality by amassing great wealth. But
the captain had long ago decided that he would, on the whole, prefer
to achieve immortality by not dying
know I personally don't want to maintain
guile-1.8, so if at some point it stops being maintained in Debian,[2]
someone else will have to step up and maintain it for us to continue
distributing lilypond.
Don Armstrong
1: This is YA example of why choosing GPLv2 only is a bad idea if all
you want
On Thu, 10 Sep 2009, Joseph Wakeling wrote:
Don Armstrong wrote:
(There are a significant number of files distributed in lilypond
which are under v2 or later, or v3 or later, as well as things
like input/mutopia/claop.py, which isn't even Free Software, as it
cannot be modified.[2
On Thu, 10 Sep 2009, Graham Percival wrote:
On Wed, Sep 09, 2009 at 03:36:39PM -0700, Don Armstrong wrote:
(There are a significant number of files distributed in lilypond which
are under v2 or later, or v3 or later, as well as things like
input/mutopia/claop.py, which isn't even Free
that they should have, which
makes this kind of thing very difficult.
But by all means, please help work on this. It'll certainly make my
life easier when I have to go through and audit the code for inclusion
in Debian (which I naïvely assumed had already been done before I took
over maintenance.)
Don
25 matches
Mail list logo
