Date: Mon, 25 Oct 2021 09:21:02 +1100 From: Kubilay Kocak <koobs@FreeBSD.org> To: Michael Gmelin <freebsd@grem.de>, ports@freebsd.org Subject: Re: Portscout and gitlab Message-ID: <47a371c0-6a75-59ef-eed0-30c7fb9b0ea7@FreeBSD.org> In-Reply-To: <20211017002228.136908cf@bsd64.grem.de> References: <E36E78B2-310D-4F26-B39F-27E0B070BAA8@grem.de> <20211017002228.136908cf@bsd64.grem.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 17/10/2021 9:22 am, Michael Gmelin wrote: > > > On Sat, 16 Oct 2021 20:35:09 +0200 > Michael Gmelin <freebsd@grem.de> wrote: > >> Hi, >> >> It seems like portscout didn‘t pick up the new version of >> net-im/signald, is there anything I as a maintainer can do, or would >> this need to be added as a feature to portscout itself? >> >> Thanks >> Michael > > To clarify my request: > Currently the port is using GL_COMMIT - I was wondering if there is a > way to get releases from gitlab and if so, if portscout would pick > those up as well. > > Thanks > > Hey Michael, sorry for delay Hit me up on IRC, Discord (or wherever) so we can isolate the issue or necessary feature. It's pretty easy to run portscout locally (limiting it to your ports) and running debug to see how portscout is processing this request, and the code paths its going through. portscout sources are up in the FreeBSD GitHub Organization as well, so we can PR support for GitLab, or whatever it turns out to be. ./koobs
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47a371c0-6a75-59ef-eed0-30c7fb9b0ea7>