As the maintainer, I've received this bug report:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255009
If you'd like to run the daemon under a user different from the default git,
you also need to change the ownership of the working directories, especially
/var/*/gitea.
The expectation is
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,
Am 12.04.21 um 10:33 schrieb Koichiro Iwao:
> On Mon, Apr 12, 2021 at 10:18:20AM +0200, Antoine Brodin wrote:
>> On Mon, Apr 12, 2021 at 10:05 AM Koichiro Iwao wrote:
>>>
>>> The branch main has been updated by meta:
>>>
>>> URL:
>>>
Thanks Dan,
Will fixit soon.
Kind Regards,
Moin
> On 14 Apr, 2021, at 00:41, Dan Langille wrote:
>
> At present, the home page for audio/faac is set to a domain which is no
> longer relevant to the port.
>
> Should we set that to https://github.com/knik0/faac in pkg-descr?
>
> --
> Dan
At present, the home page for audio/faac is set to a domain which is no longer
relevant to the port.
Should we set that to https://github.com/knik0/faac in pkg-descr?
--
Dan Langille
d...@langille.org
___
freebsd-ports@freebsd.org mailing list
On Mon, 12 Apr 2021, Peter Jeremy via freebsd-ports wrote:
Except that git will arbitrarily and randomly decide that it needs to
run "gc" - which is similarly extravagant in memory usage. Last time I
found one running, it thrashed that poor VM for 3 days.
Would this be a good time to
> On 14. Apr 2021, at 00:54, Dave Horsfall wrote:
>
> On Mon, 12 Apr 2021, Peter Jeremy via freebsd-ports wrote:
>
>> Except that git will arbitrarily and randomly decide that it needs to run
>> "gc" - which is similarly extravagant in memory usage. Last time I found
>> one running, it
On 2021-04-13 15:53, Dave Horsfall wrote:
On Mon, 12 Apr 2021, Peter Jeremy via freebsd-ports wrote:
Except that git will arbitrarily and randomly decide that it needs to run
"gc" - which is similarly extravagant in memory usage. Last time I found
one running, it thrashed that poor VM for 3
