FreeBSD ports you maintain which are out of date

2019-10-31 Thread portscout
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you

GL_xx tags fail when GL_SITE=https://git.zrythm.org

2019-10-31 Thread Yuri
In the port audio/zrythm when DISTVERSION=0.7.021 and GL_COMMIT=869fc2493d252506c7bf4f76d2e6ec25c0b5d1da 'make makesum' fails to fetch the tarball. What is wrong? Thanks, Yuri ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/

Re: GL_xx tags fail when GL_SITE=https://git.zrythm.org

2019-10-31 Thread Tobias Kortkamp
On Thu, Oct 31, 2019 at 12:14:39AM -0700, Yuri wrote: > In the port audio/zrythm when DISTVERSION=0.7.021 and > GL_COMMIT=869fc2493d252506c7bf4f76d2e6ec25c0b5d1da 'make makesum' fails > to fetch the tarball. > > > What is wrong? GL_* is for GitLab instances and https://git.zrythm.org does not

Re: GL_xx tags fail when GL_SITE=https://git.zrythm.org

2019-10-31 Thread Yuri
On 2019-10-31 00:57, Tobias Kortkamp wrote: GL_* is for GitLab instances andhttps://git.zrythm.org does not appear to be one anymore. It worked as a GitLab in the previous versions, but now it doesn't any more? Did it morph somehow? Yuri ___ fr

Re: GL_xx tags fail when GL_SITE=https://git.zrythm.org

2019-10-31 Thread Mathieu Arnold
On Thu, Oct 31, 2019 at 01:23:15AM -0700, Yuri wrote: > On 2019-10-31 00:57, Tobias Kortkamp wrote: > > GL_* is for GitLab instances andhttps://git.zrythm.org does not > > appear to be one anymore. > > > It worked as a GitLab in the previous versions, but now it doesn't any more? > > Did it mor

devel/rubygem-rbtrace fails in 2019Q4

2019-10-31 Thread Matthias Fechner
Dear all, has anyone an idea, why devel/rubygem-rbtrace  fails to build in 2019Q4 branch? https://pkg.fechner.net/data/120amd64-2019Q4/2019-10-31_12h47m53s/logs/errors/rubygem-rbtrace-0.4.11.log It must be something related not the the port itself, but I cannot find what commit has to be MFHed to