We are happy to announce the release of LilyPond 2.25.21. This is
termed a development release, but these are usually reliable for
testing new features and recent bug fixes. However, if you require
stability, we recommend using version 2.24.4, the current stable
release.
Please refer to the Install
We are happy to announce the release of LilyPond 2.25.20. This is
termed a development release, but these are usually reliable for
testing new features and recent bug fixes. However, if you require
stability, we recommend using version 2.24.4, the current stable
release.
Please refer to the Install
We are happy to announce the release of LilyPond 2.25.19. This is
termed a development release, but these are usually reliable for
testing new features and recent bug fixes. However, if you require
stability, we recommend using version 2.24.4, the current stable
release.
Please refer to the Install
On Sat, 2024-08-03 at 20:52 +0200, Johannes Feulner wrote:
> Hi there,
>
> I would like to join the development team. Please set permissions on
> gitlab for me (jofeu, @jofeux) so that I could upload dev branches.
Done, welcome! Please note though that uploading dev branches to
https://gitlab.co
We are proud to announce the release of GNU LilyPond 2.24.4. LilyPond
is a music engraving program devoted to producing the highest-quality
sheet music possible. It brings the aesthetics of traditionally
engraved music to computer printouts.
This version contains a number of fixes since the releas
On Mon, 2024-07-08 at 22:30 +0200, Jonas Hahnfeld wrote:
> On Sun, 2024-06-16 at 22:24 +0200, Jonas Hahnfeld wrote:
> > Hi all,
> >
> > it's been 7 months since the last stable (bugfix) release, LilyPond
> > 2.24.3. Today I went through the list of all (smalle
We are happy to announce the release of LilyPond 2.25.18. This is
termed a development release, but these are usually reliable for
testing new features and recent bug fixes. However, if you require
stability, we recommend using version 2.24.3, the current stable
release.
Please refer to the Install
On Sun, 2024-07-14 at 10:54 +0200, Jonas Hahnfeld wrote:
> Hi all,
>
> heads-up for people verifying my emails: I generated a new PGP key,
> attached to this message and uploaded to keyservers, that I will use
> to sign my future emails. The old key has not been compromised, I
Hi all,
heads-up for people verifying my emails: I generated a new PGP key,
attached to this message and uploaded to keyservers, that I will use to
sign my future emails. The old key has not been compromised, I only
took the opportunity to use newer cryptography options.
Cheers
Jonas
621780CB46
On Tue, 2024-07-09 at 14:22 +0200, Thomas Morley wrote:
> Please have a look at https://gitlab.com/lilypond/lilypond/-/issues/6726
> A showstopper for next stable?
Thanks for the heads-up. As far as I can tell, and from local testing,
this only affects the current master / unstable releases. So ye
On Mon, 2024-06-17 at 19:37 +, Werner LEMBERG wrote:
> > > I also suggest !2359.
> >
> > So far I didn't backport any documentation improvements to
> > stable/2.24. Is there anything special about this one?
>
> I think these index entries complete the list of essential syntax
> elements in t
On Sun, 2024-06-16 at 22:24 +0200, Jonas Hahnfeld wrote:
> Hi all,
>
> it's been 7 months since the last stable (bugfix) release, LilyPond
> 2.24.3. Today I went through the list of all (smaller) merge requests
> and marked those that we might want to apply to the stable/2.
On Mon, 2024-06-17 at 03:16 +, Werner LEMBERG wrote:
> > [...] we could think about having LilyPond 2.24.4 in early / mid
> > July. What do you think?
>
> +1
>
> I also suggest !2359.
So far I didn't backport any documentation improvements to stable/2.24.
Is there anything special about thi
Hi all,
it's been 7 months since the last stable (bugfix) release, LilyPond
2.24.3. Today I went through the list of all (smaller) merge requests
and marked those that we might want to apply to the stable/2.24 branch
with the Backport label:
https://gitlab.com/lilypond/lilypond/-/merge_requests?st
We are happy to announce the release of LilyPond 2.25.17. This is
termed a development release, but these are usually reliable for
testing new features and recent bug fixes. However, if you require
stability, we recommend using version 2.24.3, the current stable
release.
Please refer to the Install
We are happy to announce the release of LilyPond 2.25.16. This is
termed a development release, but these are usually reliable for
testing new features and recent bug fixes. However, if you require
stability, we recommend using version 2.24.3, the current stable
release.
Please refer to the Install
On Wed, 2024-05-01 at 22:20 +0200, Michael Käppler wrote:
>
> > There is one caveat here that I would like to mention: During initial
> > testing in my fork, one test job unexpectedly hang during a lilypond
> > execution, using 100% CPU and eventually being killed after 60 minutes.
> > Subsequent
Hi all,
I mentioned this during the transition to Guile 3.0, and now I had the
time to prepare the required changes to move the base of our GitLab
testing to Ubuntu 22.04. The merge request to do so is here:
https://gitlab.com/lilypond/lilypond/-/merge_requests/2318
There is one caveat here that
We are happy to announce the release of LilyPond 2.25.15. This is
termed a development release, but these are usually reliable for
testing new features and recent bug fixes. However, if you require
stability, we recommend using version 2.24.3, the current stable
release.
Please refer to the Install
On Tue, 2024-04-02 at 16:40 +0200, Michael Käppler wrote:
> Am 01.04.2024 um 22:03 schrieb Jonas Hahnfeld via Discussions on LilyPond
> development:
> > As pointed out by Han-Wen in November, this is actually fairly little
> > code that gets dropped; we need to keep some relate
On Sun, 2023-11-05 at 22:36 +0100, Jonas Hahnfeld wrote:
> Step 4: Remove compatibility code for Guile 2.2
> This can happen after we made one or two releases with only Guile 3.0.
This is now up for review in the following merge request:
https://gitlab.com/lilypond/lilypond/-/merge_request
On Sat, 2024-03-23 at 23:03 +0100, Michael Käppler wrote:
> Hi Jonas,
> thanks for working on this!
>
> > Windows build with Guile JIT: https://cloud.hahnjo.de/s/Ek5x9rybpiPNtoj
> > This turns on just-in-time compilation that was added in Guile 3.0, but
> > we had to keep disabled on Windows until
On Sat, 2024-03-23 at 14:08 -0700, Kenneth Wolcott wrote:
> Hi Jonas;
>
> I hope that the following information is useful:
>
> Lilypond performance stats for the engraving of one very small and one
> medium sized pieces
>
> native = Apple Silicon build
> foreign = x86_64
> other = MacPorts LP
On Sat, 2024-03-23 at 14:24 -0500, Karlin High wrote:
> On 3/23/2024 2:00 PM, Jonas Hahnfeld wrote:
> > Would be interesting to see how this compares to the "vanilla" package
>
> I tried it, 3 runs. First one maybe unfair because font cache
> initialization or somet
On Sun, 2024-03-24 at 03:20 -0700, Aaron Hill wrote:
> The error occurred from my WSL1 environment running Ubuntu 18.04.
> Probably my own fault for keeping bionic around.
Ah ok; yes, Ubuntu 18.04 is end-of-life since last year already, so I
didn't check its versions.
> I do have Ubuntu 20.04 u
On Sat, 2024-03-23 at 18:18 -0700, Aaron Hill wrote:
> On 2024-03-23 6:25 am, Jonas Hahnfeld wrote:
> > We are happy to announce the release of LilyPond 2.25.14. This is
> > termed a development release, but these are usually reliable for
> > testing new features and recent b
On Sat, 2024-03-23 at 11:39 -0700, Kenneth Wolcott wrote:
> Hi Jonas;
>
> I've tried engraving a couple of randomly chosen previous engravings
> (using LP 2.24.x) using the new LP 2.25.14 version on my Mac (Apple
> Silicon).
>
> Since none of my engravings are large, most of them are one to t
On Sat, 2024-03-23 at 17:46 +0100, Jean Abou Samra wrote:
> Le samedi 23 mars 2024 à 16:02 +0100, Jonas Hahnfeld via Discussions on
> LilyPond development a écrit :
> > Native Apple Silicon build: https://cloud.hahnjo.de/s/x9D62eASSn6Ng7D
> > This is a native arm64 ve
On Sat, 2024-03-23 at 11:41 -0500, Karlin High wrote:
> On 3/23/2024 10:02 AM, Jonas Hahnfeld via LilyPond user discussion wrote:
> > Windows build with Guile JIT: https://cloud.hahnjo.de/s/Ek5x9rybpiPNtoj
> > This turns on just-in-time compilation that was added in Guile 3.0, but
On Sat, 2024-03-23 at 14:25 +0100, Jonas Hahnfeld wrote:
> We are happy to announce the release of LilyPond 2.25.14. This is
> termed a development release, but these are usually reliable for
> testing new features and recent bug fixes.
Following this release, I made two special builds
We are happy to announce the release of LilyPond 2.25.14. This is
termed a development release, but these are usually reliable for
testing new features and recent bug fixes. However, if you require
stability, we recommend using version 2.24.3, the current stable
release.
Please refer to the Install
Hi all,
as noted in https://gitlab.com/lilypond/lilypond/-/merge_requests/2246,
we are starting to run into some issues because of dated software in
CentOS 7 and Ubuntu 20.04. For that reason, I'm proposing in
https://gitlab.com/lilypond/lilypond/-/merge_requests/2261 to upgrade
our platforms used
We are happy to announce the release of LilyPond 2.25.13. This is
termed a development release, but these are usually reliable for
testing new features and recent bug fixes. However, if you require
stability, we recommend using version 2.24.3, the current stable
release.
Please refer to the Install
On Mon, 2023-12-04 at 21:55 +0100, Jonas Hahnfeld wrote:
> On Sun, 2023-11-05 at 22:36 +0100, Jonas Hahnfeld wrote:
>
> > then remove automatic detection of Guile 2.2 from configure.
>
> I did not yet upload a merge request to make Guile 3.0 the default for
> all builds:
We are happy to announce the release of LilyPond 2.25.12. This is
termed a development release, but these are usually reliable for
testing new features and recent bug fixes. However, if you require
stability, we recommend using version 2.24.3, the current stable
release.
Please refer to the Install
On Thu, 2023-12-14 at 17:43 +, Werner LEMBERG wrote:
> > > > Looks like it was fixed?
> > > > https://status.gitlab.com/pages/history/5b36dc6502d06804c08349f7
> > >
> > > Yep, thanks.
> >
> > I spoke too early – it's still not working properly.
>
> On this page I read:
>
> For self-hosted
We are happy to announce the release of LilyPond 2.25.11. This is
termed a development release, but these are usually reliable for
testing new features and recent bug fixes. However, if you require
stability, we recommend using version 2.24.3, the current stable
release.
Please refer to the Install
On Sun, 2023-11-05 at 22:36 +0100, Jonas Hahnfeld wrote:
> Step 3: Switch to Guile 3.0
> Afterwards, we can merge
> https://gitlab.com/lilypond/lilypond/-/merge_requests/2163
I put the merge request back on Patch::review, along with
https://gitlab.com/lilypond/lilypond/-/merge_requests
We are proud to announce the release of GNU LilyPond 2.24.3. LilyPond
is a music engraving program devoted to producing the highest-quality
sheet music possible. It brings the aesthetics of traditionally
engraved music to computer printouts.
This version contains a number of fixes since the releas
On Wed, 2023-11-15 at 23:06 +0100, Jonas Hahnfeld wrote:
> Hi all,
>
> I backported the first batch of commits yesterday, some more merge
> requests are still tagged with the Backport label that I will take care
> of later (including "official" support for Guile 3.0
On Thu, 2023-11-16 at 11:11 -0600, Karlin High wrote:
> On Sun, Nov 12, 2023 at 6:26 AM Jonas Hahnfeld via LilyPond user
> discussion wrote:
> > If you have some time, please test them in your setups and report back in
> > case of problems!
>
> Seems OK so far. Window
Hi all,
I backported the first batch of commits yesterday, some more merge
requests are still tagged with the Backport label that I will take care
of later (including "official" support for Guile 3.0 unless somebody
objects until then). I plan to build the binaries on Saturday, November
18, and th
On Sat, 2023-11-11 at 19:37 +0100, Jonas Hahnfeld wrote:
> We are happy to announce the release of LilyPond 2.25.10.
And here are the binaries with Guile 3.0, built using
https://gitlab.com/lilypond/lilypond/-/merge_requests/2163 and
https://gitlab.com/lilypond/lilypond/-/merge_requests/2
On Sat, 2023-11-11 at 18:37 +0100, Han-Wen Nienhuys wrote:
> On Sun, Nov 5, 2023 at 10:36 PM Jonas Hahnfeld wrote:
> > Hi all,
> >
> > I hear LilyPond hasn't changed its Guile version since some time (more
> > than 18 months). So before we get too comfortable wit
We are happy to announce the release of LilyPond 2.25.10. This is
termed a development release, but these are usually reliable for
testing new features and recent bug fixes. However, if you require
stability, we recommend using version 2.24.2, the current stable
release.
Please refer to the Install
On Sun, 2023-11-05 at 22:36 +0100, Jonas Hahnfeld wrote:
> Step 1: Officially support Guile 3.0 and add optional CI testing
> I opened https://gitlab.com/lilypond/lilypond/-/merge_requests/2162 to
> add some compatibility with earlier versions of Guile 3.0 and then
> implement detectio
On Sun, 2023-11-05 at 22:48 +0100, Jean Abou Samra wrote:
> What I don't really understand is why you want to add compatibility
> with Guile 3.0.x for small x. Upstream completely breaks the normal
> expectation from what you would find in a point release, by putting
> features and even severely ba
Hi all,
I hear LilyPond hasn't changed its Guile version since some time (more
than 18 months). So before we get too comfortable with the current
situation, let me propose to move to Guile 3.0. Below is a plan for
that switch, with a transition period to test the official binaries.
Last time, when
We are happy to announce the release of LilyPond 2.25.9. This is termed
a development release, but these are usually reliable for testing new
features and recent bug fixes. However, if you require stability, we
recommend using version 2.24.2, the current stable release.
Please refer to the Installi
On Sun, 2023-09-03 at 14:40 +0200, Jonas Hahnfeld via Discussions on
LilyPond development wrote:
> For a possible timeline, we could wait for the release of LilyPond
> 2.25.8 (probably September 16/17 because I'm travelling next weekend,
> unless Jean wants to do it again) and
On Sun, 2023-09-03 at 14:40 +0200, Jonas Hahnfeld wrote:
> For a possible timeline, we could wait for the release of LilyPond
> 2.25.8 (probably September 16/17 because I'm travelling next weekend,
> unless Jean wants to do it again) and then merge the changes right
> afte
We are happy to announce the release of LilyPond 2.25.8. This is termed
a development release, but these are usually reliable for testing new
features and recent bug fixes. However, if you require stability, we
recommend using version 2.24.2, the current stable release.
Please refer to the Installi
On Sun, 2023-09-03 at 15:18 +0200, Jean Abou Samra wrote:
> Le dimanche 03 septembre 2023 à 14:48 +0200, Jonas Hahnfeld a écrit :
> > Can you please
> > change it to something more like:
> > "IMPORTANT: Binaries and documentation archives are NOT updated on
> > li
On Sun, 2023-09-03 at 14:29 +0200, Jean Abou Samra wrote:
> Le vendredi 01 septembre 2023 à 19:56 +0200, Jonas Hahnfeld a écrit :
> > Yes, could be a good idea. Looking at the directory, it seems like the
> > contents of README.html are displayed below the list of directories,
>
Hi all,
after some more work, I think I have resolved most details for
generating LilyPond's HTML documentation with texi2any. The only minor
detail I would like to call out (for transparency) is that we will
again have "see section" when building with Texinfo 6.7, essentially
reverting https://gi
On Fri, 2023-09-01 at 16:25 +0200, Jean Abou Samra wrote:
> > As for the issue, I consider that somewhat of an outlier: Most users
> > will follow the links on the website, and everything will work for
> > them. A small fraction tries to find the binaries where they used to be
> > (and I'm surprise
On Fri, 2023-09-01 at 14:31 +0200, Jean Abou Samra wrote:
> Hi,
>
> Per the release procedure
> https://lilypond.org/doc/v2.25/Documentation/contributor/release-checklist ,
> GitLab releases for LilyPond contain both binaries + doc tarballs and source
> tarballs generate by "make dist", while the
Hi all,
after months of preparations (if not years) and actual implementation
work during the last few weekends, I would like to share the first
complete prototype for generating LilyPond's HTML documentation with
texi2any: https://gitlab.com/lilypond/lilypond/-/merge_requests/2089
Before you get
We are proud to announce the release of GNU LilyPond 2.24.2. LilyPond
is a music engraving program devoted to producing the highest-quality
sheet music possible. It brings the aesthetics of traditionally
engraved music to computer printouts.
This version contains a number of fixes since the releas
On Tue, 2023-08-08 at 10:57 +0200, Jonas Hahnfeld via Discussions on
LilyPond development wrote:
> I finally have (fixed) internet again! With that, the plan would be to
> first check for additional backports and then build the binaries during
> the week, probably tomorrow or Thursday.
Hi all,
On Fri, 2023-07-28 at 08:28 +0200, Jonas Hahnfeld via Discussions on
LilyPond development wrote:
> On Sat, 2023-07-08 at 15:29 +0200, Jonas Hahnfeld via Discussions on
> LilyPond development wrote:
> > On Sat, 2023-07-01 at 15:02 +0200, Jonas Hahnfeld via Discussions on
On Mon, 2023-07-31 at 09:54 +0200, Jean Abou Samra wrote:
> > Yes, but flex has always been there as a dependency of some other
> > package I think, only not added in your environment variables. We can
> > explicitly add it to the Brewfile if you think that's better, but it
> > shouldn't change the
On Mon, 2023-07-31 at 01:15 +0200, Jean Abou Samra wrote:
> Hi,
>
> As a follow-up to the release: on macOS I encountered a quirk which is
> that the compiler spit out build errors on the Flex-generated lexer
> out/lexer.cc. (Now I find myself stupid for not saving the error messages
> somewhere.)
On Sun, 2023-07-30 at 18:31 +0200, Jean Abou Samra wrote:
> Trying to do the release, I got these messages during "./build-doc.sh":
>
> [...]
>
> Is that expected?
Yes, it has always been there for the online pages because the big-
pages use language content negotiation and aren't valid file nam
On Sat, 2023-07-08 at 15:29 +0200, Jonas Hahnfeld via Discussions on
LilyPond development wrote:
> On Sat, 2023-07-01 at 15:02 +0200, Jonas Hahnfeld via Discussions on
> LilyPond development wrote:
> > I plan to build the binaries next weekend, July 8th or 9th, for
> > th
On Mon, 2023-07-17 at 07:08 +0200, Jean Abou Samra wrote:
> Le samedi 08 juillet 2023 à 15:29 +0200, Jonas Hahnfeld via Discussions on
> LilyPond development a écrit :
> > Unfortunately, this won't happen: My fiber is cut and I don't have
> > (fixed) internet 😞 and wh
On Sat, 2023-07-01 at 15:02 +0200, Jonas Hahnfeld via Discussions on
LilyPond development wrote:
> I plan to build the binaries next weekend, July 8th or 9th, for
> the final release on Wednesday, July 12th.
Unfortunately, this won't happen: My fiber is cut and I don't have
(fi
On Sat, 2023-07-08 at 10:20 +, Werner LEMBERG wrote:
> Currently, `make bytecode && make doc` is broken:
https://lists.gnu.org/archive/html/lilypond-devel/2023-07/msg8.html
(it's not like there are hundreds of messages every day, a duplicate
thread doesn't serve anybody...)
signature.as
On Sat, 2023-07-01 at 21:34 +0200, Jean Abou Samra wrote:
> The idea of the delay between the build and the release is to let people test
> the binaries first, right?
Yes, I will upload the binaries to GitLab but only do the tagging +
announcement + website upload on Wednesday, in case anything c
Hi all,
after the unstable release 2.25.6 is out and the included update of
bdwgc seems to resolve the rare crashes on Windows (not backported
yet), I would like to go ahead with the stable version 2.24.2.
If there is anything else that needs to go in, please ping me on
GitLab. I plan to build th
We are happy to announce the release of LilyPond 2.25.6. This is termed
a development release, but these are usually reliable for testing new
features and recent bug fixes. However, if you require stability, we
recommend using version 2.24.1, the current stable release.
Please refer to the Installi
On Thu, 2023-06-22 at 14:32 +0200, Jean Abou Samra wrote:
> Recently, GitLab gained a "bulk edit" button in the MR view.
This button has "always" been there ...
> That means the person doing the release (currently Jonas) can
> easily assign all the MRs merged during the release in a few
> clicks,
On Fri, 2023-06-16 at 19:46 +0200, Jean Abou Samra wrote:
> Le vendredi 16 juin 2023 à 18:11 +0200, Jonas Hahnfeld a écrit :
> > I think I'd still lean towards doing the release as planned because (a)
> > the issue is already there with the current 2.25.5 and (b) it's also
On Fri, 2023-06-16 at 10:37 +0200, Jean Abou Samra wrote:
> I know that 2.25.6 was planned for this weekend. Unfortunately, due to
> https://gitlab.com/lilypond/lilypond/-/issues/6620 , current master is not
> going to work on Kubuntu and possibly other distros.
>
> I will try to find time this
We are happy to announce the release of LilyPond 2.25.5. This is termed
a development release, but these are usually reliable for testing new
features and recent bug fixes. However, if you require stability, we
recommend using version 2.24.1, the current stable release.
Please refer to the Installi
Hi all,
due to various constraints, I am kind of restricted when I will be able
to do the next releases, so I thought I might as well let you know:
LilyPond 2.25.5 will happen on the weekend of the 20th/21st (unless I
get too bored this next weekend...). I'm planning version 2.25.6 for
the second
On Fri, 2023-04-28 at 15:14 +, Werner LEMBERG wrote:
> Creating font configuration...
> Adding fontconfig configuration file:
> /usr/local/share/lilypond/2.25.5/fonts/emmentaler-font.conf
>
> Fontconfig error: No writable cache directories
Let's state the obvious candidate here: This is very
On Wed, 2023-01-04 at 14:39 +0100, Jonas Hahnfeld via Discussions on
LilyPond development wrote:
> Now, this works in our current setup, but it seems to me that there is
> an easier way to achieve this with "native" Texinfo tools: Instead of
>
> @node Translated
We are happy to announce the release of LilyPond 2.25.4. This is termed
a development release, but these are usually reliable for testing new
features and recent bug fixes. However, if you require stability, we
recommend using version 2.24.1, the current stable release.
Please refer to the Installi
On Mon, 2023-04-17 at 22:52 +0200, Jean Abou Samra wrote:
> Hi,
> Just a thought related to
> https://gitlab.com/lilypond/lilypond/-/merge_requests/1950: maybe we
> could add optional CI jobs running on CentOS 7 to compile Linux
> official binaries + MinGW binaries ?
Windows binaries are cross-com
We are happy to announce the release of LilyPond 2.25.3. This is termed
a development release, but these are usually reliable for testing new
features and recent bug fixes. However, if you require stability, we
recommend using version 2.24.1, the current stable release.
Please refer to the Installi
On Mon, 2023-03-13 at 22:20 +0100, Jonas Hahnfeld via Discussions on
LilyPond development wrote:
> On Wed, 2023-01-04 at 23:36 +0100, Jonas Hahnfeld via Discussions on
> LilyPond development wrote:
> > 1. All @ref{Translated} become @ref{Origin}, but as far as I understand
> > th
On Sun, 2023-03-19 at 23:56 +0100, Federico Bruni wrote:
> Actually I was curious to check the html output rather than the changes
> in the source.
> If it doesn't break working links, it's fine for me.
In the parts I touched, it is almost generating identical HTML (except
for the links to unnumb
On Mon, 2023-03-20 at 14:34 +, Werner LEMBERG wrote:
> Comparing
>
> http://lilypond.org/web.html
>
> with a self-compiled
>
> .../out-www/offline-root/Documentation/web/web.html
>
> I see the attached difference. Is it an oversight that
> `scripts/build/fix-docsize.sh` is not executed
Hi all,
sorry for dropping the ball on this topic...
On Wed, 2023-01-04 at 23:36 +0100, Jonas Hahnfeld via Discussions on
LilyPond development wrote:
> On Wed, 2023-01-04 at 22:58 +0100, Federico Bruni wrote:
> > Il giorno mer 4 gen 2023 alle 14:39:47 +0100, Jonas Hahnfeld
> &
On Sun, 2023-03-12 at 22:16 +, Werner LEMBERG wrote:
> > Well, what I was trying to say, and what I probably should have
> > made more explicit, is that "official" binaries from our side
> > require a bit of work. In fact, the support in our scripts needs
> > to be dealt with in advance, so "p
On Sun, 2023-03-12 at 21:50 +0100, Ben wrote:
> Hi Jonas,
>
> Thanks for your answer.
>
> I don't know how works macports, but it already managesto provide
> compiled versions for Apple ARM of lilypond (and frescobaldi).
>
> In fact, I can live with that, so I will wait.
Well, what I was try
On Thu, 2023-03-02 at 02:28 +0100, Ben wrote:
> Hello everyone,
>
> Thanks for the list.
>
> I would be interested in a version of lilypond natively for
> Apple processors.
>
> I work with a mac M1 and if someone explains me the procedure
> for the compilation, I can gladly compile this versi
On Thu, 2023-03-02 at 13:17 +0100, Jean Abou Samra wrote:
> ArchLinux gets it almost right, however I think that TeX Gyre fonts
> should be made required, https://bugs.archlinux.org/task/77700.
> Manjaro takes the package from ArchLinux.
FWIW I strongly disagree here: 99.9% of the users are fine w
On Sat, 2023-02-18 at 14:43 -0500, Shane Brandes wrote:
> That is great, but where can one find a list of changes between
> versions?
The current Changes document can be found here:
http://lilypond.org/doc/v2.25/Documentation/changes/
In general, all manuals for the development releases are linked
We are happy to announce the release of LilyPond 2.25.2. This is termed
a development release, but these are usually reliable for testing new
features and recent bug fixes. However, if you require stability, we
recommend using version 2.24.1, the current stable release.
Please refer to the Installi
On Mon, 2023-02-13 at 13:36 +0100, Janneke Nieuwenhuizen wrote:
> Han-Wen Nienhuys writes:
>
> Hey,
>
> > Every year, we go over the source code to update the copyright years
> > that are found in the source headers. I propose to stop this.
>
> +1
>
> > Also note that many other projects (eg. g
We are proud to announce the release of GNU LilyPond 2.24.1. LilyPond
is a music engraving program devoted to producing the highest-quality
sheet music possible. It brings the aesthetics of traditionally
engraved music to computer printouts.
This version includes a number of fixes since the releas
On Wed, 2023-02-08 at 19:08 +0100, Jonas Hahnfeld via Discussions on
LilyPond development wrote:
> > Otherwise, I plan to build the binaries on Thursday, February 9th, or
> > Friday the 10th, with the final release foreseen for Sunday the 12th.
>
> I didn't hear objection
On Wed, 2023-02-01 at 22:39 +0100, Jonas Hahnfeld via Discussions on
LilyPond development wrote:
> Hi all,
>
> after the situation with Debian seems to be resolved (guile-2.2 and
> lilypond-2.24.0 are in unstable and they should get into bookworm), I
> would like to come back
On Sun, 2023-02-05 at 13:05 +, Werner LEMBERG wrote:
> > These are *ancient*, the last version 10.11.6 was released in 2018.
> > Even if we find one, I think we must not introduce any workaround
> > for such outdated systems.
>
> *Must not*? This is a bit harsh IMHO.
Any workaround we introd
On Sun, 2023-02-05 at 12:54 +, Werner LEMBERG wrote:
> Looking into MacPorts 'lilypond-devel' log files for Yosimite
> (
> https://build.macports.org/builders/ports-10.10_x86_64-builder/builds/
> 211914/steps/install-port/logs/stdio)
> and El Capitan
> (
> https://build.macports.org/builders/po
On Mon, 2023-01-30 at 08:55 +, Werner LEMBERG wrote:
> The deadline for registering LilyPond as mentor organization for GSoC
> 2023 is February 7th. Do we want to participate?
>
> Who did the registration the last time? If necessary, I'm willing to
> do the registering process if we agree on
Hi all,
after the situation with Debian seems to be resolved (guile-2.2 and
lilypond-2.24.0 are in unstable and they should get into bookworm), I
would like to come back to the plan of releasing LilyPond 2.24.1 as a
bugfix version.
I just backported the last outstanding merge requests that I had
On Sun, 2023-01-29 at 20:41 +, Werner LEMBERG wrote:
> > That said, I just noticed /usr/share/icons/ going from 0.5M to 64M.
> > It's split between adwaita-icon-theme, humanity-icon-theme,
> > ubuntu-mono, all pulled in transitively by fontforge (via libgdraw6
> > and libgtk-3-0). I guess we c
1 - 100 of 1411 matches
Mail list logo
