ok for me
On (2017-03-23 15:56), Pavel Korovin wrote:
> On 03/23, Daniel Jakots wrote:
> > I'm not the maintainer so I don't have the last word. That said, IMHO
> > the current state is fine but I don't have a strong opinion about it.
>
> Oops. Daniel, Robert, I'm sorry.
> I missed the real MAINT
On 03/23, Daniel Jakots wrote:
> I'm not the maintainer so I don't have the last word. That said, IMHO
> the current state is fine but I don't have a strong opinion about it.
Oops. Daniel, Robert, I'm sorry.
I missed the real MAINTAINER because of the update Daniel have sent to ports@.
--
Wit
On Tue, 21 Mar 2017 14:46:48 +0300, Pavel Korovin wrote:
> On 03/17, Daniel Jakots wrote:
> >
> > Here's a diff to update gitea to 1.1.0. ChangeLog is quite long and
> > it says:
> >
>
> Hi Daniel,
> Works fine for me as well, thank you!
Thanks for your report.
> You forgot to allocate the
On Tue, Mar 21, 2017 at 02:46:48PM +0300, Pavel Korovin wrote:
> On 03/17, Daniel Jakots wrote:
> >
> > Here's a diff to update gitea to 1.1.0. ChangeLog is quite long and it
> > says:
> >
>
> Hi Daniel,
> Works fine for me as well, thank you!
>
> You forgot to allocate the user/group id for _g
On 03/17, Daniel Jakots wrote:
>
> Here's a diff to update gitea to 1.1.0. ChangeLog is quite long and it
> says:
>
Hi Daniel,
Works fine for me as well, thank you!
You forgot to allocate the user/group id for _gitea user in
$PORTSDIR/infrastructure/db/user.list, and 787 is already allocated:
Hi,
Here's a diff to update gitea to 1.1.0. ChangeLog is quite long and it
says:
> BREAKING
>
> The SSH keys can potentially break, make sure to regenerate the
> authorized keys
https://github.com/go-gitea/gitea/releases
Lightly tested from a new install, it works fine.
Comments? OK?
