On 2018-03-27 14:29, Wookey wrote:
On 2018-03-22 22:31 +0100, Aurelien Jarno wrote:
On 2018-03-07 12:08, Hector Oron wrote:
> 2018-03-07 12:01 GMT+01:00 Philipp Kern :
To do more tests I agree that we should deploy it on more buildds. For
*this phase*, I believe enabling
On 2018-03-22 22:31 +0100, Aurelien Jarno wrote:
> On 2018-03-07 12:08, Hector Oron wrote:
> > 2018-03-07 12:01 GMT+01:00 Philipp Kern :
> To do more tests I agree that we should deploy it on more buildds. For
> *this phase*, I believe enabling lingering and deploying it by hand
On 27.03.2018 09:22, Julien Cristau wrote:
> On 03/22/2018 10:31 PM, Aurelien Jarno wrote:
>> To do more tests I agree that we should deploy it on more buildds. For
>> *this phase*, I believe enabling lingering and deploying it by hand is
>> the best. Is it something acceptable?
>>
> Sounds ok to
On 03/27/2018 09:35 AM, Philipp Kern wrote:
> That all said: I'm happy to brainstorm and to implement proposed
> solutions. Right now that seems to require more infrastructural changes
> though and I'd rather focus on getting rid of buildd itself first.
>
That's fair.
Cheers,
Julien
On 03/22/2018 10:31 PM, Aurelien Jarno wrote:
> To do more tests I agree that we should deploy it on more buildds. For
> *this phase*, I believe enabling lingering and deploying it by hand is
> the best. Is it something acceptable?
>
Sounds ok to me, though I'd prefer if the buildd user (as in