Re: Lilypond and distribution bugtrackers [was: LSR is not at the stable release level]

2012-10-02 Thread Martin Tarenskeen
On Tue, 2 Oct 2012, Graham Percival wrote: If not, perhaps it's worth subscribing bugs-lilypond to trackers for the major distros (Debian, Ubuntu, Fedora, etc.) so that the development team at least gets alerted to the issues out there? Those distros can come talk to us if they want to send

Re: Lilypond and distribution bugtrackers [was: LSR is not at the stable release level]

2012-10-02 Thread Graham Percival
On Tue, Oct 02, 2012 at 06:18:34PM +0200, Joseph Rushton Wakeling wrote: > Looking at the Ubuntu/Launchpad bug list for Lilypond makes me > wonder -- is there any mechanism in place to ensure Lilypond > developers receive bug reports placed in distros' bugtrackers? No. > If not, perhaps it's wort

Re: Lilypond and distribution bugtrackers [was: LSR is not at the stable release level]

2012-10-02 Thread Joseph Rushton Wakeling
On 10/02/2012 11:51 PM, Colin Hall wrote: bugs-lilypond is for receiving reports against the code we release. Can you suggest a viable alternative to ensure that the development team receive notice of downstream bug reports? ___ bug-lilypond maili

Re: Lilypond and distribution bugtrackers [was: LSR is not at the stable release level]

2012-10-02 Thread Janek Warchoł
On Tue, Oct 2, 2012 at 11:51 PM, Colin Hall wrote: > > On Tue, Oct 2, 2012 at 6:18 PM, Joseph Rushton Wakeling > wrote: > > perhaps it's worth subscribing bugs-lilypond to trackers for the major > > distros (Debian, Ubuntu, Fedora, etc.) so that the development team at least > > gets alerted to t

Re: Lilypond and distribution bugtrackers [was: LSR is not at the stable release level]

2012-10-02 Thread Colin Hall
On Tue, Oct 02, 2012 at 10:45:30PM +0200, Janek Warcho wrote: > On Tue, Oct 2, 2012 at 6:18 PM, Joseph Rushton Wakeling > wrote: > > perhaps it's worth subscribing bugs-lilypond to trackers for the major > > distros (Debian, Ubuntu, Fedora, etc.) so that the development team at least > > gets aler

Re: Lilypond and distribution bugtrackers [was: LSR is not at the stable release level]

2012-10-02 Thread Janek Warchoł
On Tue, Oct 2, 2012 at 6:18 PM, Joseph Rushton Wakeling wrote: > perhaps it's worth subscribing bugs-lilypond to trackers for the major > distros (Debian, Ubuntu, Fedora, etc.) so that the development team at least > gets alerted to the issues out there? sounds like +1 Janek

Re: LSR is not at the stable release level

2012-10-02 Thread Joseph Rushton Wakeling
On 10/02/2012 07:17 PM, James wrote: Still it's all 'moot' (American version) as we have no snippet log to look at. It could be a memory leak - I see for instance all those old messages show up with Mike's woodwind fingering charts. So whatever they are using is not that current. It's 2.14.2, w

Re: LSR is not at the stable release level

2012-10-02 Thread James
On 2 October 2012 17:54, Joseph Rushton Wakeling wrote: > On 10/02/2012 06:40 PM, James wrote: >> >> Well unless they are using 1GB of RAM, I personally have not had any >> problems with 2GB or RAM. So I'd find it hard to believe it was RAM. > > > AFAICS they're not building it on local machines b

Re: LSR is not at the stable release level

2012-10-02 Thread Joseph Rushton Wakeling
On 10/02/2012 06:40 PM, James wrote: Well unless they are using 1GB of RAM, I personally have not had any problems with 2GB or RAM. So I'd find it hard to believe it was RAM. AFAICS they're not building it on local machines but on automated server systems, possibly on cloud-based virtual serve

Re: LSR is not at the stable release level

2012-10-02 Thread James
Hello, On 2 October 2012 17:24, Joseph Rushton Wakeling wrote: > On 10/02/2012 06:21 PM, James wrote: >> >> So without the snippet log I cannot really tell, but it doesn't look >> that clean to start with. Maybe someone else can care comment? > > > Do you have any remarks on the suspicion given i

Re: LSR is not at the stable release level

2012-10-02 Thread Joseph Rushton Wakeling
On 10/02/2012 06:21 PM, James wrote: So without the snippet log I cannot really tell, but it doesn't look that clean to start with. Maybe someone else can care comment? Do you have any remarks on the suspicion given in the bugtracker that it's because of the very large amounts of memory requir

Re: LSR is not at the stable release level

2012-10-02 Thread James
Hello, On 2 October 2012 17:08, Joseph Rushton Wakeling wrote: > On 09/30/2012 02:39 PM, David Kastrup wrote: >> >> http://bugs.launchpad.net/ubuntu/+source/lilypond/+bug/1047693> > > > Regarding Ubuntu, has anybody been contacted about this bug? > https://bugs.launchpad.net/ubuntu/+source/lilypo

Lilypond and distribution bugtrackers [was: LSR is not at the stable release level]

2012-10-02 Thread Joseph Rushton Wakeling
Looking at the Ubuntu/Launchpad bug list for Lilypond makes me wonder -- is there any mechanism in place to ensure Lilypond developers receive bug reports placed in distros' bugtrackers? If not, perhaps it's worth subscribing bugs-lilypond to trackers for the major distros (Debian, Ubuntu, Fed

Re: LSR is not at the stable release level

2012-10-02 Thread Joseph Rushton Wakeling
On 09/30/2012 02:39 PM, David Kastrup wrote: http://bugs.launchpad.net/ubuntu/+source/lilypond/+bug/1047693> Regarding Ubuntu, has anybody been contacted about this bug? https://bugs.launchpad.net/ubuntu/+source/lilypond/+bug/1021570 There's also this (quite old) not-quite-bug, which might be

Re: LSR is not at the stable release level

2012-10-02 Thread Joseph Rushton Wakeling
On 09/30/2012 02:39 PM, David Kastrup wrote: http://bugs.launchpad.net/ubuntu/+source/lilypond/+bug/1047693> AFAICS Ubuntu just imports whatever's in Debian Sid at the time they make their 6-monthly fork. In principle they can pull in an updated package from Debian (they've done this for ot

Re: LSR is not at the stable release level

2012-10-02 Thread Eluze
David Kastrup wrote > "Phil Holmes" < > mail@ > > writes: > >> "Eluze" < > eluzew@ > > wrote in message >> news: > 1348959173728-133838.post@.nabble > ... >>> it's a shame - the LSR still works with an old stable version >>> (actual stable >>> is 2.16.0, LSR is 2.14.2) >>> >>> this means >>