El día Tuesday, November 11, 2014 a las 05:00:08PM -0500, Adam McDougall
escribió:
>
> As long as the machine does not crash, you can re-run bulk after
> cancelling it or it dying, and it starts fresh builds of any packages
> which were not complete from a previous run. If libX11 succeeded, it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/11/14 15:00, Adam McDougall wrote:
> On 11/11/2014 16:52, Russell L. Carter wrote:
[...]
>> Is there really no way to restart a bulk build from unchanged
>> state when you're say already 2/3 through 900+ ports?
>>
>> Thanks, Russell
>
> As
On 11/11/2014 16:52, Russell L. Carter wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> On 11/11/14 10:06, Russell L. Carter wrote:
>> Hi, I am curious what is the best way to recover/restart an
>> interrupted poudriere bulk build. The man page is not helpful
>> here.
>>
>
> S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/11/14 10:06, Russell L. Carter wrote:
> Hi, I am curious what is the best way to recover/restart an
> interrupted poudriere bulk build. The man page is not helpful
> here.
>
So I had another opportunity to look into this, and I see
I can st
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I am curious what is the best way to recover/restart an
interrupted poudriere bulk build. The man page is not
helpful here.
If I just try rerunning the build command, I get:
>> Error: jail already running: current-amd64-default
Looking thro
