Re: Poudriere package builds for 101amd64-default have not run since 1-Jan-2017

[Simon Wright]

On 14/01/2017 15:26, Mathieu Arnold wrote:

Le 14/01/2017 à 05:57, Simon Wright a écrit :

Hi all

I sync my local ports tree to the same release as is used to build
packages. Checking my logs and the logs on beefy6 which is/was the

Has anything changed with the build system or are there issues? There
are a few security issues in r430183 which I guess are fixed in more

Adding to what was already said, builds are often shuffled around
without any notice, and the beefyX boxes should never be accessed
directly, if you really need this kind of informations,
pkg-status.freebsd.org is the place to go to.

Thanks again for the tip, have a good weekend!

Simon.

Thanks Mathieu, that points me to the solution: pull the json file from pkg-status.freebsd.org instead of beefy6 and parse it for the build info for the jail I'm interested in. In this case whichever jail is building 10.x packages. That will give me the revision for the latest completed package-build run then I can go back to synching to that ports revision and building my ~30 packages with non-default options from that rather than the latest available. My system is a bit of a cludge since it is not possible to directly pull the revision info used to build a given package or group of packages. Ideally this would be included in the output of pkg info or similar command. If we could do that, the whole process would be much more straightforward. I realise that trying to keep a local ports tree and poudriere system in sync with the build cluster will never be completely correct and prone to breakage, but it (mostly!) works for my small-scale deployment . . . .

smime.p7s
Description: S/MIME Cryptographic Signature