Обсуждение: My buildfarm member now giving permission denied

Поиск
Список
Период
Сортировка

My buildfarm member now giving permission denied

От
Larry Rosenman
Дата:
FreeBSD SVN rev:
r352600   -      -          1.69G 2019-09-22 13:13
r352873   NR     /          43.1G 2019-09-29 16:36

I went from r352600 to r352873 and now I'm getting PostgreSQL permission 
denied
errors on the check phase of the build.

FreeBSD folks: Any ideas?
PostgreSQL folks: FYI.



-- 
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 214-642-9640                 E-Mail: ler@lerctr.org
US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106



Re: My buildfarm member now giving permission denied

От
Larry Rosenman
Дата:
On 10/01/2019 8:27 pm, Larry Rosenman wrote:
> FreeBSD SVN rev:
> r352600   -      -          1.69G 2019-09-22 13:13
> r352873   NR     /          43.1G 2019-09-29 16:36
> 
> I went from r352600 to r352873 and now I'm getting PostgreSQL 
> permission denied
> errors on the check phase of the build.
> 
> FreeBSD folks: Any ideas?
> PostgreSQL folks: FYI.
latest build log:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=peripatus&dt=2019-10-02%2001%3A20%3A14


-- 
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 214-642-9640                 E-Mail: ler@lerctr.org
US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106



Re: My buildfarm member now giving permission denied

От
Kyle Evans
Дата:
On Tue, Oct 1, 2019 at 8:32 PM Larry Rosenman <ler@lerctr.org> wrote:
>
> On 10/01/2019 8:27 pm, Larry Rosenman wrote:
> > FreeBSD SVN rev:
> > r352600   -      -          1.69G 2019-09-22 13:13
> > r352873   NR     /          43.1G 2019-09-29 16:36
> >
> > I went from r352600 to r352873 and now I'm getting PostgreSQL
> > permission denied
> > errors on the check phase of the build.
> >
> > FreeBSD folks: Any ideas?
> > PostgreSQL folks: FYI.
> latest build log:
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=peripatus&dt=2019-10-02%2001%3A20%3A14
>

Just to follow up with this for list' sake; this was fixed by r352952.

Thanks,

Kyle Evans