Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 18 Sep 2014 12:05:02 +0100
From:      Arthur Chance <>
To:        Matthias Apitz <>,
Subject:   Re: A lot of pkg problems
Message-ID:  <>
In-Reply-To: <20140918064103.GA1195@tiny-r269739>
References:  <1812950.bWcWxrzvJI@penguin> <> <> <> <> <> <20140917085023.GA1534@tiny-r269739> <> <20140917134133.GA2080@tiny-r269739> <> <20140918064103.GA1195@tiny-r269739>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On 18/09/2014 07:41, Matthias Apitz wrote:
> El día Wednesday, September 17, 2014 a las 03:56:58PM +0100, Arthur Chance escribió:
>>> Thanks. Is this with a recent version of poudriere. The presentation of
>>> the logs has changed to use 'json'. See here:
>> root@arthur:1# poudriere version
>> 3.0.17
> I'm using a poudriere version 3.1pre from around mid of August (I have
> not updated since this the host itself, only the ports tree in the
> jail).

I take it that's the development version of the port?

>> I tend to upgrade at weekends, so haven't got yesterday's 3.0.18 version.
>> My logs are plain text and I see nothing in that link that suggests they
>> should be JSON. Are you sure that's the link you meant? It was last
>> updated 2013-07-16 so wouldn't contain anything new.
> Yes, at the very end in the mime types.

That's just a generic directive for nginx, as already exists in the 
current mime.types.

 > Check also this page:
> "... There’s even a very useful JSON-based web frontend to poudriere
> that’s included. Point your webserver or FTP server to show
> /usr/local/poudriere/data/logs/bulk/91x64/latest and take a look. This
> is an easy way to monitor the status of bulk port builds without looking
> at the terminal. ..."

Does you have an index.html in the latest log directory? If you do, what 
do you get if you point your browser at it? Using the URL just ending in 
"latest" should do the usual web server tap dance to redirect it to the 
directory form of the URL with a trailing slash and that should pick up 
index.html but will only work if you have an nginx index directive in 
your config. By default nginx won't do that.

> As I said, until now I could make this working, maybe because it's
> nearly at the end of my todo list :-)
> 	matthias

Want to link to this message? Use this URL: <>