-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
media-sound/lilypond: fix compilation with fontforge wrt #557160 #311
Conversation
Since I am an active user of this package I can proxy-maintain it, as it seems to be abandoned by the maintainer. I would like to get the other lilypond bugs fixed and bump the ebuild for the developement release. |
Indeed I see many bugs open. I'll try to get in contact with the maintainers. |
@LilRC: good news! The maintainers will be happy to have a proxied maintainer. Please add yourself to metadata.xml and the proxy-maintainers herd. |
By the way, for git patches it's usually better to take the git format patch (with the commit message etc.) |
@mgorny: I added myself as maintainer in metadata.xml and sent a mail to proxy-maint@gentoo.org, as I guess that is the way to be added to the proxy-maintainers herd. Also, do you mean sending the patches by mail rather than via pull requests? |
@gentoo/proxy-maint, need approval for making this package |
indeed yes |
metadata.xml is missing the herd; the line <herd>scheme</herd>
<herd>proxy-maintainers</herd> hmm: <email>hkBst@gentoo.org</email>
<name>Marijn Schouten</name> It appears he is an ex dev, never heard of him. So current line 5-8 will also require deleting, and the patch here needs ammending accordingly. |
@idella: Fixed. Also, all lilypond bugs [1] need to be reassigned. [1] https://bugs.gentoo.org/buglist.cgi?quicksearch=lilypond |
hmm sure, fair comment |
Package-Manager: portage-2.2.23
Package-Manager: portage-2.2.23
Oh, sorry! There was a merge conflict I missed... I will fix and rebase right now! Just a few minutes, please. |
Oh, sorry again for the noice. I realised it was only on my local copy of the repo there were issues. The commits should be fine. :) |
Will do this first thing to morrow. Late. Sorry for presuming dev had left. |
Test run drew error; see Bug 557160 |
@hasufell if you got anything here, that's fine |
The ebuild has been built effectively by a dev and a user in their systems, confirming the patch is functional. The dep fontforge itself has issues distinct to the lilypond package. I shall likely commit it tomorrow. |
pushed |
Thank you! |
Package-Manager: portage-2.2.23