Update print/lilypond-devel to latest version
Created attachment 177699 [details] Patch for print/lilypond-devel to 2.19.52
Hi Martin, thanks for your submission. For this and future issues, please: - Confirm the change (patch) passes QA (portlint & poudriere). For more information see: https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/testing.html - Set the maintainer-approval flag to + on attachments for ports you are maintainer of. Attachment -> Details -> maintainer-approval [+] - Don't CC the freebsd-ports mailing list, as new Ports & Package issues are already automatically assigned to the freebsd-ports-bugs list. - Setting maintainer-feedback flag to + is only required if it is set to ? first (which means asking the maintainer for feedback, which doesn't apply when the maintainer is the reporter)
I tried building the patch here on Poudriere in a 12-HEAD jail and it failed: configure: creating ./config.status config.status: creating config.make config.status: creating config.hh WARNING: Please consider installing optional programs or files: URW++ OTF fonts (download OTF files from 'http://git.ghostscript.com/? p=urw-core35-fonts.git;a=commit;h=79bcdfb34fbce12b592cce389fa7a19da6b5b018' and put them under '~/.local/share/fonts' etc., or use --wi th-urwotf-dir) gs >= 9.20 (installed: 9.16) extractpdfmark (Optionally using Ghostscript >= 9.20 together with Extract PDFmark can sign ificantly reduce the disk space required for building the documentation and the final PDF files.) ERROR: Please install required programs: /usr/local/bin/fontforge >= 20110222 (installed: ) See INSTALL.txt for more information on how to build LilyPond
Created attachment 180084 [details] Patch for print/lilypond-devel to 2.19.55
The new patch also fails to build on Poudriere: config.status: creating config.make config.status: creating config.hh WARNING: Please consider installing optional programs or files: URW++ OTF fonts (download OTF files from 'http://git.ghostscript.com/?p=urw-core35-fonts.git;a=commit;h=79bcdfb34fbce12b592cce389fa7a19da6b5b018' and put them under '~/.local/share/fonts' etc., or use --with-urwotf-dir) gs >= 9.20 (installed: 9.16) extractpdfmark (Optionally using Ghostscript >= 9.20 together with Extract PDFmark can significantly reduce the disk space required for building the documentation and the final PDF files.) ERROR: Please install required programs: /usr/local/bin/fontforge >= 20110222 (installed: ) See INSTALL.txt for more information on how to build LilyPond
Created attachment 180664 [details] Patch for print/lilypond-devel to 2.19.56
(In reply to Raphael Kubo da Costa from comment #5) Hello Raphael, Thanks for your feedback. Unfortunately I wasn't able to reproduce the problem (using poudriere-devel). Did you perhaps make some additional modification to the ports tree used by poudriere that might interfere with the build? In any case it would be a great help if you could send me the full build log so I can see what's happening (or not happeninjg) until the point of failure. Thanks in advance, Martin
I finally took some time to investigate this; the problem is that my jail is built with WITHOUT_GNU_GREP_COMPAT=yes, and STEPMAKE_GET_VERSION in aclocal.m4 uses extended regular expressions in a call to grep without passing -E, which breaks fontforge's version detection when grep(1) is built with the option I mentioned. I tried it on 10.3 with a default grep(1) and the patch indeed worked. By the way, have you tried removing MAKE_JOBS_UNSAFE? I've tried this on a jail with many cores and it worked fine, though the best would be passing a low -j number.
I am getting this from poudriere: ====>> Checking for filesystem violations... done ====>> Error: Filesystem touched during build: extra: var/db/fontconfig/30f1f778d4121994232d6adf0fafd1af-le64.cache-7 build of print/lilypond-devel ended at Sun Mar 12 12:22:26 CET 2017 Could you take a look?
(In reply to Thomas Zander from comment #9) Would mind sending me the full log? I just finished another run from poudriere which finished with no errors.
Created attachment 180883 [details] Patch for print/lilypond-devel to 2.19.57
Created attachment 180923 [details] fs-violation log from poudriere Newest patch generates the same fs violation. Full log attached.
I didn't get any errors here with in an 10.3-i386 jail. Does adding USES=fonts help your build pass?
(In reply to Raphael Kubo da Costa from comment #13) Nope, same error, also reproducible on a 10.3 i386 poudriere jail. You are running "poudriere testport", right?
Right.
Created attachment 180960 [details] fs-violation log from poudriere on 10.3 i386 Here is my poudriere log from 10.3 / i386 jail. Can you check for differences in your log?
Hmm, I tried building with poudriere instead of poudriere-devel and got the same filesystem violation error.
+bdrewery. I wonder if this is a bug in the non-devel version of Poudriere.
After some bisection, Poudriere stopped complaining once the BUILD_AS_NON_ROOT option's default became "yes". If I set it to "no", I get the same fontconfig error with a later version of Poudriere.
(In reply to Thomas Zander from comment #9) > I am getting this from poudriere: > > ====>> Checking for filesystem violations... done > ====>> Error: Filesystem touched during build: > extra: var/db/fontconfig/30f1f778d4121994232d6adf0fafd1af-le64.cache-7 > build of print/lilypond-devel ended at Sun Mar 12 12:22:26 CET 2017 > > Could you take a look? Is this with or without BUILD_AS_NON_ROOT? (yes or no?) I think what is happening is that this cache is not generated either at fontconfig package creation time or installation time when building as non-root, and then when the build runs later the cache is generated unexpectedly.
(In reply to Bryan Drewery from comment #20) > (In reply to Thomas Zander from comment #9) > > I am getting this from poudriere: > > > > ====>> Checking for filesystem violations... done > > ====>> Error: Filesystem touched during build: > > extra: var/db/fontconfig/30f1f778d4121994232d6adf0fafd1af-le64.cache-7 > > build of print/lilypond-devel ended at Sun Mar 12 12:22:26 CET 2017 > > > > Could you take a look? > > Is this with or without BUILD_AS_NON_ROOT? (yes or no?) That's with BUILD_AS_NON_ROOT=no (the default in ports-mgmt/poudriere 3.1.15). > I think what is happening is that this cache is not generated either at > fontconfig package creation time or installation time when building as > non-root, and then when the build runs later the cache is generated > unexpectedly. Would you say that's a bug in Poudriere or is there something we can do in the port itself?
I've tried building lilypond-devel-2.19.51_1 (the version currently in ports) with BUILD_AS_NON_ROOT=no and got the same fontconfig error. So given this update will not introduce a regression, I'm going to land it.
A commit references this bug: Author: rakuco Date: Fri Mar 24 10:58:50 UTC 2017 New revision: 436807 URL: https://svnweb.freebsd.org/changeset/ports/436807 Log: Update to 2.19.57. PR: 215076 Submitted by: m.ne@gmx.net (maintainer) Changes: head/print/lilypond-devel/Makefile head/print/lilypond-devel/distinfo head/print/lilypond-devel/files/patch-Documentation_GNUmakefile head/print/lilypond-devel/files/patch-config.make.in head/print/lilypond-devel/files/patch-configure head/print/lilypond-devel/files/patch-flower_include_std-string.hh head/print/lilypond-devel/files/patch-flower_include_std-vector.hh head/print/lilypond-devel/files/patch-lily_include_lily-guile.hh head/print/lilypond-devel/files/patch-python_GNUmakefile head/print/lilypond-devel/files/patch-stepmake_stepmake_texinfo-vars.make head/print/lilypond-devel/pkg-plist