On Wed, Apr 15, 2015 at 4:22 AM, Matthew Seaman matt...@freebsd.org wrote:
On 2015/04/15 12:03, Mike Clarke wrote:
Many thanks, that provided the essential clue. beefy6.nyi.freebsd.org
provides
logs for 101amd64-default and 84amd64-default.
A bit of digging around enabled me to put
On Wed, Apr 15, 2015 at 08:55:23AM -0700, Kevin Oberman wrote:
My thanks to whoever made this possible. New hardware of this sort is a bit
expensive and the time of those who can integrate it all is invaluable.
I'm not the one working on this so I'm somewhat butting in, however:
You guys
I've updated the script to make use of your information and did some
other tweaks.
https://gist.github.com/reedacartwright/8622973baf89b263a6d7
On Wed, Apr 15, 2015 at 4:03 AM, Mike Clarke
jmc-freeb...@milibyte.co.uk wrote:
On Tuesday 14 Apr 2015 11:30:19 Don Lewis wrote:
On 14 Apr, Mike
On Tuesday 14 Apr 2015 11:30:19 Don Lewis wrote:
On 14 Apr, Mike Clarke wrote:
[snip]
The problem is that 101amd64-default hasn't been built on
beefy2.isc.freebsd.org since version 381523 on 2015-03-18_03h47m09s.
The mystery is where do we get the logs from now?
Look for
On 2015/04/15 12:03, Mike Clarke wrote:
Many thanks, that provided the essential clue. beefy6.nyi.freebsd.org
provides
logs for 101amd64-default and 84amd64-default.
A bit of digging around enabled me to put together the following list:
beefy1.isc.freebsd.org
93i386-default
It is possible to grab the revision information from the build logs.
I have written a script to pull the number and update a local svn copy
of the ports.
https://gist.github.com/reedacartwright/8622973baf89b263a6d7
On Sun, Apr 12, 2015 at 10:40 AM, Simon Wright simon.wri...@gmx.net wrote:
On
On Tuesday 14 Apr 2015 02:06:35 Reed A. Cartwright wrote:
It is possible to grab the revision information from the build logs.
I have written a script to pull the number and update a local svn copy
of the ports.
https://gist.github.com/reedacartwright/8622973baf89b263a6d7
That script is
If you have any patches for the script, please send them my way and I
will merge them as needed.
It looks to me like 101amd64-default no longer exists. Maybe it has
been disabled for some reason.
On Tue, Apr 14, 2015 at 4:37 AM, Mike Clarke
jmc-freeb...@milibyte.co.uk wrote:
On Tuesday 14 Apr
On 14 Apr, Mike Clarke wrote:
On Tuesday 14 Apr 2015 02:06:35 Reed A. Cartwright wrote:
It is possible to grab the revision information from the build logs.
I have written a script to pull the number and update a local svn copy
of the ports.
On 12/04/2015 18:50, Mike Clarke wrote:
Sounds like it would be a useful feature but in the meantime could anyone
point me to where I can find the SVN revision used by the ports cluster when
building for 101amd64-default? It used to be on
beefy2.isc.freebsd.org/#latest_builds but that now only
On Thursday 02 Apr 2015 10:13:34 Mel Pilgrim wrote:
On 2015-04-01 13:42, Mike Clarke wrote:
Where can I now obtain the revision number for the ports tree used for the
latest package build?
Although the above method has worked in the past it's a bit of a bodge.
The ideal way would be if
+--On 2 avril 2015 10:13:34 -0700 Mel Pilgrim
list_free...@bluerosetech.com wrote:
| On 2015-04-01 13:42, Mike Clarke wrote:
| Where can I now obtain the revision number for the ports tree used for
| the latest package build?
|
| Although the above method has worked in the past it's a bit of a
On 2015-04-01 13:42, Mike Clarke wrote:
Where can I now obtain the revision number for the ports tree used for the
latest
package build?
Although the above method has worked in the past it's a bit of a bodge. The
ideal
way would be if this information could be accessed directly from the
I use pkg upgrade to maintain most of my ports but a small number need to be
built
from source. To avoid problems I aim to keep my ports tree in sync with the
snapshots
used by the package cluster.
Until a couple of weeks ago I was able to obtain the revision number of the
ports
snapshot
14 matches
Mail list logo
