Francisco Vila writes:
> 2013/4/26 Federico Bruni :
>>
>> 2013/4/24 Don Armstrong
>>>
>>> It will be uploaded to unstable once the current testing releases
>>> (wheezy). Then it will transition to the new testing (jessie), and
>>> soon after that I'll make an upload to backports.
>>>
>>> Because
2013/4/26 Federico Bruni :
>
> 2013/4/24 Don Armstrong
>>
>> It will be uploaded to unstable once the current testing releases
>> (wheezy). Then it will transition to the new testing (jessie), and
>> soon after that I'll make an upload to backports.
>>
>> Because 2.16 released well after the freez
2013/4/24 Don Armstrong
> > I wonder what it's stopping from being included in testing and if we
> > can help somehow. The Debian freeze should end soon, I think. The
> > current bugs are here:
> > http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=lilypond;dist=unstable
>
> It will be uploaded to
On Wed, 24 Apr 2013, Federico Bruni wrote:
> The next Debian stable, which is going to be released in a few days,
> will have 2.14 again. Hopefully 2.16 will be added to backports in
> the next future. But it's in experimental since september:
> http://packages.qa.debian.org/l/lilypond.html
>
> I
2013/4/24 David Kastrup
> > The next Debian stable, which is going to be released in a few days,
> > will have 2.14 again.
>
> "Again"?
>
> Current Debian stable has 2.12.3. So we are making progress.
yes, you are right
however, having 2.16 would be a better progress
lilypond is not in the bac
Federico Bruni writes:
> Speaking about LilyPond on Linux... yesterday I've seen that version
> 2.16 is still in debian experimental:
> http://packages.debian.org/search?keywords=lilypond
>
> The next Debian stable, which is going to be released in a few days,
> will have 2.14 again.
"Again"?
Speaking about LilyPond on Linux... yesterday I've seen that version 2.16
is still in debian experimental:
http://packages.debian.org/search?keywords=lilypond
The next Debian stable, which is going to be released in a few days, will
have 2.14 again. Hopefully 2.16 will be added to backports in the
