On Fri, Nov 10, 2017 at 01:47:23PM +0100, Erik Bray wrote:
[...]
> I don't understand the issue here--if a package is a dependency of
> Sage then it will be built, right? This only seems to apply to
> optional packages.
Yes. As far as i am concerned, optional packages are a very important part
of
On Fri, Nov 10, 2017 at 1:38 PM, Thierry
wrote:
> On Fri, Nov 10, 2017 at 01:04:36PM +0100, Thierry wrote:
> [...]
>> But, if we want to add an option to let the patchbot install a new package
>> proposed by some ticket, after testing that ticket, the patchbot will be
>> in a different state than
Hi Thierry, thanks for clarifying on this--
On Fri, Nov 10, 2017 at 1:04 PM, Thierry
wrote:
> Hi,
>
> On Fri, Nov 10, 2017 at 12:35:51PM +0100, Erik Bray wrote:
>> It seems to me those should be among the most important, if not *the*
>> most important tickets to farm out to patchbots across multi
On Fri, Nov 10, 2017 at 01:04:36PM +0100, Thierry wrote:
[...]
> But, if we want to add an option to let the patchbot install a new package
> proposed by some ticket, after testing that ticket, the patchbot will be
> in a different state than before to test other tickets, in this situation,
> the p
Hi,
On Fri, Nov 10, 2017 at 12:35:51PM +0100, Erik Bray wrote:
> It seems to me those should be among the most important, if not *the*
> most important tickets to farm out to patchbots across multiple
> platforms. If it made sense to I would set my Windows patchbot to
> prioritize these among all
It seems to me those should be among the most important, if not *the*
most important tickets to farm out to patchbots across multiple
platforms. If it made sense to I would set my Windows patchbot to
prioritize these among all others.
New versions of packages are far more likely to break across
p
