On 02/26/2018 04:59 PM, Dusty Mabe wrote:
>
>
> On 02/26/2018 07:51 PM, Kevin Fenzi wrote
>> This is not the case with any of the bodhi enabled releases. They only
>> update the buildroot from base packages + stable updates + specific
>> packages that are added as buildroot overrides.
>
> Yeah
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/26/2018 07:51 PM, Kevin Fenzi wrote:
> On 02/22/2018 07:34 PM, Dusty Mabe wrote:
>>
>> If I understand correctly there was a new lorax build [1] that completed
>> at 01:11 UTC (02/23) that then made it into the runroot of a task [2] that
>>
On 02/22/2018 07:34 PM, Dusty Mabe wrote:
>
> If I understand correctly there was a new lorax build [1] that completed
> at 01:11 UTC (02/23) that then made it into the runroot of a task [2] that
> was part of a pungi compose [3] that started at 14:54 UTC (02/22).
runroot is confusing here as we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
If I understand correctly there was a new lorax build [1] that completed
at 01:11 UTC (02/23) that then made it into the runroot of a task [2] that
was part of a pungi compose [3] that started at 14:54 UTC (02/22).
I think this caused problems
