Maintainership for print/lilypond-devel

Hi everyone, I would like to offer maintaining the print/lilypond-devel port. Attached you'll find a patch bringing the port to the current version 2.19.47. A few more tests might still be necessary, but as the port is already marked for deletion I wanted to put the work I've done into the open

Re: Maintainership for print/lilypond-devel

Hi everyone, I have fixed a few embarrassing issues with the previous path and am now sufficiently confident about it to submit e PR: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212435 Best regards, Martin On 05/09/2016 14:51, Martin Neubauer wrote: > Hi everyone, > > I w

Request for commit

Hello everyone, If there is a committer out there with a little time to spare, I would be grateful if they would take a look here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213656 Best regards, Martin -- All of the above. signature.asc Description: OpenPGP digital signature

Re: [Bug 215076] print/lilypond-devel: update to 2.19.52

Eww, forgot to upload the patch. On 05/12/2016 19:02, bugzilla-nore...@freebsd.org wrote: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215076 > > Bug ID: 215076 >Summary: print/lilypond-devel: update to 2.19.52 >Product: Ports & Packages >

Re: ports-mgmt/poudriere-devel does not follow options

On 28/02/2020 17:20, Miroslav Lachman wrote: > I am using Poudriere for a long time. I switched to poudriere-devel few > days ago because I want to test ports overlay. > I run >    poudriere options -z php71m103 -p default -f > /usr/local/etc/poudriere.d/pkglists/php71m103 > just to be sure

Re: ports-mgmt/poudriere-devel does not follow options

On 01/03/2020 00:29, Miroslav Lachman wrote: > Martin Neubauer wrote on 2020/02/29 23:44: >> >> >> On 28/02/2020 17:20, Miroslav Lachman wrote: >>> I am using Poudriere for a long time. I switched to poudriere-devel few >>> days ago because

Re: ports-mgmt/poudriere-devel does not follow options

On 01/03/2020 10:06, Miroslav Lachman wrote: > I migrated from "poudriere" to "poudriere-devel" about week ago that's > when I noticed this problem. That's why I suspect poudriere-devel. > Everything worked for me for years with poudriere. > > I search my command history and I never called

Re: python 2.7 marked as deprecated and EOL while 2.7.18 RC is available

On 18/04/2020 11:57, D'Arcy Cain wrote: > I tried building lilypond with python2.7 removed from USES but its > configure script failed due to Python < 3.0. I couldn't find any > discussion about upgrading the version of Python but WikipediA says that > it has 120,000 lines Python code. As far as

Re: Port OPTIONS advice

On 20/05/2020 20:07, SirDice wrote: > On Wed, May 20, 2020 at 7:45 PM Martin Neubauer wrote: > >> How about something like: >> >> >> OPTIONS_DEFINE_amd64= JIT >> OPTIONS_DEFINE_i386=JIT >&

Re: Port OPTIONS advice

How about something like: OPTIONS_DEFINE_amd64= JIT OPTIONS_DEFINE_i386=JIT JIT_CONFIGURE_ENABLE= jit On 20/05/2020 19:25, SirDice wrote: > Hi, > > Some time ago I took over maintainership of fs-uae. Port itself is doing

Re: Port OPTIONS advice

On 20/05/2020 19:45, Martin Neubauer wrote: > JIT_CONFIGURE_ENABLE= jit Sorry, JIT_CONFIGURE_OFF= --without-jit -- Mrs. Peacock in the study with a knife. signature.asc Description: OpenPGP digital signature

print/lilypond-devel: build failure on 13.0-CURRENT

Hello all, A few days ago I started getting reports of build failures for print/lilypod-devel (e.g. http://beefy18.nyi.freebsd.org/data/head-amd64-default/p546132_s364744/logs/lilypond-devel-2.21.5.log) Due to lack of time at the moment I wasn't able to set up a FreeBSD 13 system in order to

Re: stable postgresql11 appears to have issues

There is already an outstanding issue for quite some time: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244403 There seems not to be a proper fix yet, but at least for me the workaround mentioned might work for you as well. Just add DEFAULT_VERSIONS+=llvm=10 to make.conf Good luck, Martin

Re: How to fix/patch hardcoded values

In that case you might try an appropriate invocation of REINPLACE_CMD in post-patch. On 27/12/2020 22:58, Nuno Teixeira wrote: Hello I've just submited a new port net/gitup and I used a simple workaround to help program find its config

Re: MASTER_SITES=GH? like SF

Maybe try USE_GITHUB= yes instead. On 18/01/2021 08:32, Nuno Teixeira wrote: Hello, I will use graphics/glfw port as an example: MASTER_SITES= SF The project moved to github so I will prefer use GH releases instead of SF: