Re: [sage-devel] Re: How to make package managers cry

On Wednesday, May 9, 2018 at 8:48:04 PM UTC+2, Erik Bray wrote: > > Yes--I have in the past suggested we use either Town Crier, https://trac.sagemath.org/ticket/22176 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this

Re: [sage-devel] Re: optional package doctests badly broken

On 2018-05-11 01:51, Simon King wrote: Making a bug visible and thus preventing it from being released You're making the same mistake as other people in this thread: the implication in this sentence does not hold (or at least, to a much smaller extent than one would hope). -- You received

Re: [sage-devel] Trac downtime for upgrades

I wouldn't worry about it too much especially if you expect the downtime to be relatively short. Just do the upgrade... -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an

[sage-devel] Trac downtime for upgrades

Hi all, I have some long overdue updates for Sage's Trac that I've been putting off deploying for several months, for various reasons. However, I believe it *is* ready to deploy. This upgrade will require a database migration, so it will require taking the site down for a few minutes to perform

[sage-devel] Re: [sagemath-admins] Trac downtime for upgrades

When it is down will it say why it is down? On Fri, May 11, 2018 at 2:47 AM Erik Bray wrote: > Hi all, > > I have some long overdue updates for Sage's Trac that I've been > putting off deploying for several months, for various reasons. > However, I believe it *is* ready

[sage-devel] Re: Trac downtime for upgrades

On Fri, May 11, 2018 at 5:12 PM, Erik Bray wrote: > On Fri, May 11, 2018 at 11:47 AM, Erik Bray wrote: >> Hi all, >> >> I have some long overdue updates for Sage's Trac that I've been >> putting off deploying for several months, for various reasons.

Re: [sage-devel] optional package doctests badly broken

On Thu, May 10, 2018 at 7:37 PM, Jeroen Demeyer wrote: > On 2018-05-10 17:20, Thierry wrote: >> >> Run more patchbots, with various combinations of optional packages >> included. > > > -1 > > That would more the problem more visible at best, but it wouldn't *solve* > anything.

[sage-devel] Re: Trac downtime for upgrades

On Fri, May 11, 2018 at 11:47 AM, Erik Bray wrote: > Hi all, > > I have some long overdue updates for Sage's Trac that I've been > putting off deploying for several months, for various reasons. > However, I believe it *is* ready to deploy. > > This upgrade will require a

Re: [sage-devel] optional package doctests badly broken

On Fri, May 11, 2018 at 7:37 AM Erik Bray wrote: > On Thu, May 10, 2018 at 7:37 PM, Jeroen Demeyer > wrote: > > On 2018-05-10 17:20, Thierry wrote: > >> > >> Run more patchbots, with various combinations of optional packages > >> included. > > > > > >

Re: [sage-devel] optional package doctests badly broken

On 11 May 2018 at 16:11, William Stein wrote: > > On Fri, May 11, 2018 at 7:37 AM Erik Bray wrote: > >> On Thu, May 10, 2018 at 7:37 PM, Jeroen Demeyer >> wrote: >> > On 2018-05-10 17:20, Thierry wrote: >> >> >> >> Run more

Re: [sage-devel] optional package doctests badly broken

On Fri, May 11, 2018 at 05:17:16PM +0100, John Cremona wrote: > On 11 May 2018 at 16:11, William Stein wrote: > > > > > On Fri, May 11, 2018 at 7:37 AM Erik Bray wrote: > > > >> On Thu, May 10, 2018 at 7:37 PM, Jeroen Demeyer > >>

[sage-devel] Re: Trac downtime for upgrades

On Fri, May 11, 2018 at 6:08 PM, Erik Bray wrote: > On Fri, May 11, 2018 at 5:12 PM, Erik Bray wrote: >> On Fri, May 11, 2018 at 11:47 AM, Erik Bray wrote: >>> Hi all, >>> >>> I have some long overdue updates for Sage's Trac