From: newbluemoon <newbluemoon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: lilypond: update to 2.21.3
Date: Tue, 14 Jul 2020 21:12:03 +0200 [thread overview]
Message-ID: <20200714191203.VvzzuDjBLcigUH59iIIzcUlZsD8hpcrGFjGvmAAdoQQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23531@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 366 bytes --]
New comment by newbluemoon on void-packages repository
https://github.com/void-linux/void-packages/pull/23531#issuecomment-658361564
Comment:
I’ll work on using the new system-texlive instead of texlive-bin for the next update which should simplify the template a bit and should prevent those 'tlmgr not found' errors. In the meantime this should be good as is.
next prev parent reply other threads:[~2020-07-14 19:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-12 7:45 [PR PATCH] lilypond: update to 2.21.2 newbluemoon
2020-07-14 18:58 ` [PR PATCH] [Updated] " newbluemoon
2020-07-14 19:12 ` newbluemoon [this message]
2020-07-26 15:47 ` [PR PATCH] [Updated] lilypond: update to 2.21.3 newbluemoon
2020-07-26 15:56 ` newbluemoon
2020-07-26 22:59 ` fosslinux
2020-07-26 23:42 ` q66
2020-07-27 3:15 ` newbluemoon
2020-07-27 4:04 ` q66
2020-07-27 4:08 ` q66
2020-07-27 6:55 ` newbluemoon
2020-07-27 8:49 ` [PR PATCH] [Updated] " newbluemoon
2020-07-27 8:53 ` newbluemoon
2020-08-18 5:43 ` [PR PATCH] [Updated] lilypond: update to 2.21.4 newbluemoon
2020-08-22 19:13 ` newbluemoon
2020-08-22 19:20 ` lilypond: update to 2.21.5 newbluemoon
2020-08-30 13:12 ` [PR PATCH] [Updated] " newbluemoon
2020-08-31 5:11 ` [PR PATCH] [Updated] lilypond: use system texlive for build newbluemoon
2020-09-20 16:15 ` newbluemoon
2020-09-26 13:33 ` [PR PATCH] [Updated] lilypond: update to 2.21.6 newbluemoon
2020-10-03 8:05 ` newbluemoon
2020-10-12 17:52 ` newbluemoon
2020-10-24 15:09 ` [PR PATCH] [Merged]: lilypond: update to 2.21.7 leahneukirchen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200714191203.VvzzuDjBLcigUH59iIIzcUlZsD8hpcrGFjGvmAAdoQQ@z \
--to=newbluemoon@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).