Package Details: lilypond-devel 2.19.81-2

Git Clone URL: (read-only)
Package Base: lilypond-devel
Description: An automated music engraving system (development version)
Upstream URL:
Licenses: GPL
Conflicts: lilypond, lilypond-git
Provides: lilypond=2.19.81
Submitter: pnorcks
Maintainer: haawda
Last Packager: haawda
Votes: 12
Popularity: 0.000071
First Submitted: 2008-06-08 22:18
Last Updated: 2018-02-12 20:03

Required by (16)

Sources (2)

Latest Comments

haawda commented on 2018-02-12 20:04

Thanks, fixed. Two s's were missing.

rkubosz commented on 2018-02-12 07:52


Installation of the package fails. The source url ( gives 404.

haawda commented on 2018-01-29 22:07

2.19.81 seems to be out, but I cannot download it.

jonarnold commented on 2016-03-07 19:21

WARNING: Please consider installing optional programs or files: texi2html dblatex lh CTAN package (texlive-lang-cyrillic or texlive-texmf-fonts) pngtopnm

ERROR: Please install required programs: TeX Gyre fonts OTF (make sure the fc-list utility can see them, e.g. 'sudo apt-get install fonts-texgyre', or use --with-texgyre-dir)

installing tex-gyre-fonts fixed the error

haawda commented on 2015-04-24 17:50

Added ghostscript as dependency.

kolewu commented on 2015-04-23 22:43

The (runtime) dependency 'ghostscript' is missing. Without it the conversion to pdf fails.

haawda commented on 2015-03-28 07:19

Updated to use gsfonts-cyr, thanks, bohoomil.

bohoomil commented on 2015-03-28 02:32

OK, here you are:

The package offers exactly the same functionality as gsfonts from [extra] and 't1-urw-fonts-ib' prior to upgrade. Hence if you install it, it'll replace any of 'gsfonts' / 't1-urw-fonts-ib' / 't1-urw-fonts-cyr-ib'. If you're going to use it with infinality-bundle as a replacement for 't1-urw-fonts-ib' or 't1-urw-fonts-cyr-ib', please refer to the included README file for instructions.

archmylinux commented on 2015-03-27 13:39

Bump for a package indeed :-)

haawda commented on 2015-03-27 13:34

That is indeed a very good idea. Please do so. If you want, Ican then take over maintaining that package.

bohoomil commented on 2015-03-27 00:03

I'm glad that you find `t1-urw-fonts-cyr-ib` useful. However, it is a quite unsafe to include it in make dependency array unless it is accessible to all users (now it isn't: not everyone is going to use infinality-bundle packages). I believe it might be wise to add it to the AUR in a somewhat stripped-down version (i.e. without ib specific files) and change the PKGBUILD accordingly. Please, let me know if you want me to prepare the package.

haawda commented on 2015-03-24 20:23

Thanks again, mgd.

mgd commented on 2015-03-24 11:18

I had reported the missing cyrillic characters and there now is an earlier version of the package under the name Dependency `t1-urw-fonts-cyr-ib'.

For me it worked as a temporary workaround to replace the dependency `t1-urw-fonts-ib' by `t1-urw-fonts-cyr-ib'.

On the long run I expect the cyrillic characters to reappear in the original font as they are supposed to be there. At this point in time is seems to be an upstream bug.


mgd commented on 2015-03-24 09:58

The font package 't1-urw-fonts-ib' at got updated on 19.March 2015.

The new package changes the fontname from 'Century Schoolbook' to 'Century SchoolBook' (not the capital 'B'). However much more desastrous for building lilypond is that apparently all cyrillic characters characters have been removed from the fonts.

Luckily I had saved a local copy of the version I downloaded on 4.March 2015, but at this point in time I do not know how to build this package from scratch (without w/o my saved package).

Does anybody know how to solve this using free fonts ?

I detected this while trying to build lilypond-2.19.17

haawda commented on 2015-03-12 20:46

You have to activate bohoomil's repo in your pacman.conf.

Server =

archmylinux commented on 2015-03-12 20:16

from packer:
Dependency `t1-urw-fonts-ib' of `lilypond-devel' does not exist.

Where or how do you guys get this package?

haawda commented on 2015-03-04 19:02

Definitely there is a reason for upstream's declaration of experimentality. But as guile 1.8 will vanish from man distribution's official repos, lilypond has to vanish, too, if they do not get guile 2 integration work.

Maybe it is a good compromise to ket this PKGBUILD depend on guile 1.8 for now, and point the real bleeding edge users to the lilypond-git PKGBUILD.

mgd commented on 2015-03-04 18:18

Done some further tinkering.

Changing PKGBUILD the following way makes both issues go away:
export GUILE=/usr/bin/guile1.8
export GUILE_CONFIG=/usr/bin/guile-config1.8
and remove
from the ./ command.

Seems the warning guile2 being highly experimental is there for a reason... :)

mgd commented on 2015-03-04 18:03

Well, that's one of the great things about open source. I was stuck where I was and now that I've seen your package I in turn have learned something :)

I can confirm building and installing your package works for me.

Thank you for you effort.

Unfortunately this version of Lilypond seems to have at least 2 issues:
- it can't process inputfiles with utf-8 characters (non ASCII-7) in their name.
- I have not been able to create any pdf at all. The conversion from ps to pdf utilizing gs fails. This holds for even the simplest lilypond files.

I have no idea what this is but if I were to speculate, I'd point my finger at the fonts inside t1-urw-fonts-ib being incompatible with ArchLinux stock gs.

Of course that is just guessing.

haawda commented on 2015-03-03 21:06

Forgot to say thanks, mgd. Without your comment I would not even have tried to build this. It gave me valuable insights.

haawda commented on 2015-03-03 20:52

mgd, your recipe woks for building lilypond, but fails at the install step of the PKGBUILD, where the build system tries to create otf fonts from the pfb-files using fontforge, and for this cyrillic letters are needed. The lilypond developers are not to blame for this, but the gsfonts package ships bad URW fonts.

Fortununately bohoomil's repo ships better ones.
Server =

You have to get t1-urw-fonts-ib from there, then you can use my newly uploaded PKGBUILD.

mgd commented on 2015-03-03 09:43

I've done some further tests and succeeded in compiling Lilypond 2.19.16. Here is what I had to do to make it compile:
1) Change line 189 of to read
i.e. removed the version check.
2) Commented out lines 83-85 and 87 in thus effectively removing the check whether the files c059013l.pfb c059016l.pfb c059033l.pfb c059036l.pfb contain any cyrillic character.
3) Invoked
./ --with-ncsb-dir=/usr/share/fonts/Type1 --enable-guile2
to rebuild configure and run it with the above options.

After that configure produced no errors and make all seems to have worked.

I have no idea whether the resulting lilypond is working properly. Most notably I have no idea whatsoever whether and to what end the cyrillic characters expected in the font files c059013l.pfb c059016l.pfb c059033l.pfb c059036l.pfb are needed. On my system these files contain no cyrillic characters. I don't know if in that case I should use other fonts and which.

Last not least I have enabled using guile2. On my system there is also installed guile1.8 (and guile-config1.8) but I have no idea how to tell configure to use this instead. However that seems to be the version expected by default.

So in a nutshell:
The above steps make configure run. The resulting makefile seems to work as well. I have done no other or further tests. I have not even tried to run the resulting Lilypond 2.19.16. I probably will do so eventually though.

mgd commented on 2015-03-02 23:35

The build problems that existed for 2.19.15 apparently have made it into 2.19.16 as well, i.e. both the font detection of the cyrillic Century Schoolbook font and the fontforge version check need to be fixed. Since they both happen during configure of the Lilypond source this is argueably a Lilypond bug.

In other words:
Eventually the Lilypond developers will come across these problems on their own machines. Until then someone needs to provide a fix.

On ArchLinux the fontforge check could probaly be skipped altogether (if we have it installed at all the version is new enough - assuming install from an official repo).

Not sure how to deal with the font detection problem. In fact I don't know whether I actually have the required font on my machine and why exactly the cyrillic requirement is there in the first place.

If we could drop this cyrillic requirement then fixing the font check appears to be easy as well (by changing "Century Schoolbook L" into "Century Schoolbook URW" and removing ":lang=ru" both in the fc-list string in configure).

Someone more knowledgeable than me needs to help out here.

archmylinux commented on 2015-03-02 18:50

Lilypond 2.19.16 is out :-)

I am wondering if this package is more suceptible to find a maintainer than

pnorcks commented on 2015-02-01 06:22

I am not finding time to fix the build problems with this package, so I will orphan it.

pnorcks commented on 2014-12-03 20:31

jeffutter: The missing fonts error is arguably a bug in LilyPond, since it now checks for an old version of the Ghostscript fonts, not accomodating newer versions. And the fontforge version check is broken now because some new version of fontforge changed the '--version' output format.

I'm not sure I'll have much time to investigate proper fixes, but at least I'll aim to report a bug in the near future.

jeffutter commented on 2014-11-09 16:05

This will not build/install for me. Here is the last few lines of output:

config.status: creating config.make
config.status: creating config.hh
config.status: config.hh is unchanged

WARNING: Please consider installing optional programs or files: dblatex lh CTAN package (texlive-lang-cyrillic or texlive-texmf-fonts)

ERROR: Please install required programs: International New Century Schoolbook fonts (make sure the fc-list utility can see them, or use --with-ncsb-dir) /usr/bin/fontforge >= 20110222 (installed: 6ffb25d7732adcc8d32dae75bd90bda90250304)

See INSTALL.txt for more information on how to build LilyPond
==> ERROR: A failure occurred in build().
The build failed.

pnorcks commented on 2014-01-01 01:41

As I did before when 2.16.0 was released, this package will follow the stable 2.18.* series until the 2.19 development releases begin.

The significant changes in 2.18 are found here:


pnorcks commented on 2013-09-10 05:54

akobel: The 'any' value for arch really means 'noarch', which declares the entire package to be platform-independent (no binaries). If it weren't for the 'lilypond' binary and the python midi module '', the package *would* be platform-independent :-) Regarding the build for other architectures, I am under the impression that Arch Linux proper is still a i686/x86_64 distro. The ARM effort is at

Try compiling the latest 2.17.26 release with the new texlive-bin and texlive-core packages (published on 2013-09-09), and see if you have better luck with the build. It builds okay for me.

Anonymous comment on 2013-08-26 16:42

Hm... Sorry, wait a minute. Lilypond builds fine, but unfortunately it looks like MetaPost segfaults in the current version shipped with texlive-bin. I'll try to find out how to resolve the issue and come back to you... :-/

Anonymous comment on 2013-08-26 14:19

Hi Patrick, fortunately arch=('i686' 'x86_64') is a little bit too pessimistic. :-)
I can confirm that Lily compiles smoothly and even runs on 'armv7h' (read: Samsung ARM Chromebook). I'd guess that also 'arm' (Android smartphones???) and 'armv6h' (Raspberry Pi) should work, since there are binary packages of the stable version provided in community for those.
Whether that's equivalent to 'any'? No idea.

*david_a* commented on 2013-07-25 06:44

Tried it and it seems fine. Thank you for your effort.

pnorcks commented on 2013-07-25 03:26

*david_a*: Yes, you're right. I forgot to update this package for the recent guile changes in the repos. I've uploaded an updated package file that should work. If it doesn't work, let me know.

*david_a* commented on 2013-07-24 14:22

Appears to compile; however, I can't make it produce any music. Doesn't lilypond still require _only_ guile 1.8 (i.e. can't use guile 2)?

smoge commented on 2013-03-12 07:43

pnorcks commented on 2012-10-11 02:35

The source tar was uploaded, so compile away with 2.17.4! :)

pnorcks commented on 2012-10-10 04:43

The 2.17.4 tarball appears to be missing from both and I'm sending a message to the bug-lilypond right now.

pnorcks commented on 2012-10-10 04:42

The 2.17.4 appears to be missing from both and I'm sending a message to the bug-lilypond right now.

pnorcks commented on 2012-08-28 01:42

Updated to 2.17.0. Some notes:

- The build system now groups all dependencies of the *HTML* documentation together with those of the info/man page documentation, so for now, --disable-documentation has been added to the package.

- Removed the .install file accordingly, until the issue is sorted upstream.

- Removed /usr/share/man* from the package, which is currently empty.

pnorcks commented on 2012-08-28 01:35

luolimao: Thanks for your feedback. I agree with your points about the makedeps, so I updated the array accordingly.

I would like to stick to BREs with sed, since I rarely see the '-r' option used anywhere. I also would rather be consistent with how the other repo packages are "fixing" shebangs for python2; a brief check shows that what I am using is still the convention.

Also, I would prefer to leave freetype2 and fontconfig listed explicitly, since their C APIs are used by LilyPond. So maybe they should be makedeps as well, but I would need to look into it.

luolimao commented on 2012-08-20 16:59

My bad, that regex should be
sed -ri 's:^#!.*(/usr/bin/)(env)?.*(python):#!\1\2 \32:' $file

luolimao commented on 2012-08-15 08:29

One more quick note:
bison and flex are in the [base-devel] group, and gettext, perl, and texinfo are in [base], so they shouldn't be in the makedeps.

luolimao commented on 2012-08-15 08:21

Quick note: you can change the lines that say:

.for file in $(find . -name '*.py' -print); do
.....sed -i 's_^#!.*/usr/bin/python_#!/usr/bin/python2_' $file
.....sed -i 's_^#!.*/usr/bin/env.*python_#!/usr/bin/env python2_' $file


for file in $(find -name '*.py'); do
sed -ri 's_^#!.*(/usr/bin/(env.*)?)(python)_#!\1\32_' $file

and get the same behavior. (Sorry, indentation doesn't really work in the AUR comments, so I had to use dots as indentation.)

Also, the freetype2 and fontconfig dependencies are redundant, since ghostscript depends on those 2 packages anyway.

Anyway, thanks for the rather quick version bump -- and for packaging this in general, really ;)

luolimao commented on 2012-08-15 08:18

Quick note: you can change the lines that say:

.for file in $(find . -name '*.py' -print); do
. sed -i 's_^#!.*/usr/bin/python_#!/usr/bin/python2_' $file
. sed -i 's_^#!.*/usr/bin/env.*python_#!/usr/bin/env python2_' $file


for file in $(find -name '*.py'); do
sed -ri 's_^#!.*(/usr/bin/(env.*)?)(python)_#!\1\32_' $file

and get the same behavior. (Sorry, indentation doesn't really work in the AUR comments, since extra spaces are stripped.)

Anyway, thanks for the rather quick version bump -- and for packaging this in general, really ;)

luolimao commented on 2012-08-15 08:17

Quick note: you can change the lines that say:

.for file in $(find . -name '*.py' -print); do
. sed -i 's_^#!.*/usr/bin/python_#!/usr/bin/python2_' $file
. sed -i 's_^#!.*/usr/bin/env.*python_#!/usr/bin/env python2_' $file


for file in $(find -name '*.py'); do sed -ri 's_^#!.*(/usr/bin/(env.*)?)(python)_#!\1\32_' $file

and get the same behavior. (Sorry, indentation doesn't really work in the AUR comments, so I had to put the "do" on a separate line.)

Anyway, thanks for the rather quick version bump -- and for packaging this in general, really ;)

smoge commented on 2012-01-16 23:39


pnorcks commented on 2012-01-06 06:24

Good idea. I've updated the PKGBUILD.

alexmerry commented on 2012-01-04 12:22

Can I suggest passing
to make install? That way, the lilypond vim files would be found automatically by vim.

pnorcks commented on 2011-08-13 05:58

Updated to 2.15.8-2, which requires TeX Live 2011 (from the testing repo). makedepends has been updated to 'texlive-core>=2011.23170' accordingly.

pnorcks commented on 2011-06-23 02:26

> Lilypond latest 'Stable' is 2.14.1. community repository version is very outdated (2.12.3-7), and no PKGBUILD seems to be available in aur yet.

I just reported a bug:

> Will just changing pkgname, pkgver, source and checksums in this PKGBUILD good enough to compile 2.14.1?

Yes, that will work.

> ps: 2.15.2 is out

Thanks, it's updated.

Anonymous comment on 2011-06-22 16:50

Lilypond latest 'Stable' is 2.14.1. community repository version is very outdated (2.12.3-7), and no PKGBUILD seems to be available in aur yet.

Will just changing pkgname, pkgver, source and checksums in this PKGBUILD good enough to compile 2.14.1?

ps: 2.15.2 is out

pnorcks commented on 2011-06-12 20:13

Thanks, updated.

smoge commented on 2011-06-12 19:42

2.15.1 is out!

pnorcks commented on 2010-10-23 00:23

Sure! You could change the --prefix configure option in the PKGBUILD.

The default value is "/usr/local", though I often like to install LilyPond to "$HOME/usr".

fsarud commented on 2010-10-22 23:59

Does someone know if there is a way I can install both lilypond and lilypond-devel at the same time? I'd like to try the devel version but in any case I need the stable release. Thanks!