Re: [sage-devel] Re: setuptools install problem
On Thu, May 15, 2014 at 12:53 AM, Ralf Stephan wrote: > It may be possible to test newer package versions in patchbot without > official ticket by forking Sage on github, installing the package in the > local > Sage, publish the changed branch on github, and use that branch as > base_repo with patchbot. This may work also with unsafe tickets because > the cloning into /tmp copies upstream/ too. I'm testing that soon. Yes, that should work fine. Perhaps we should have a standard patchbot branch that is usually master but also contains the rare fix like this. > If this doesn't work then my fork of patchbot soon will have a version > with a --keep-tmp option that doesn't delete failed installs in /tmp so > that the setuptools problem can be postmortemed. I have stopped > making pull requests at robertb/patchbot. > > https://github.com/rwst/patchbot I've been out of the country with extremely limited internet access the last two weeks; please keep the pull requests coming and I will get to them (along with all of my other backlog). > On Tuesday, May 13, 2014 9:51:17 PM UTC+2, Peter Bruin wrote: >> >> I started a patchbot based on 6.3.beta1, and the problem has unfortunately >> popped up again with the new setuptools version: >> >> >> http://patchbot.sagemath.org/log/16348/debian/wheezy/sid/x86_64/3.2.0-57-generic/selmer/2014-05-13%2019:57:47%20+0100 >> >> >> Op woensdag 7 mei 2014 10:05:32 UTC+1 schreef Ralf Stephan: >>> >>> http://trac.sagemath.org/ticket/16300 >>> >>> People running patchbot with errors on setuptools install please try >>> version 2.2b1 of setuptools and report if this changes the behaviour >>> or not. >>> >>> Regards, > > -- > 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 > email to sage-devel+unsubscr...@googlegroups.com. > To post to this group, send email to sage-devel@googlegroups.com. > Visit this group at http://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- 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 email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Please review #13125
I didn't put it there. I agree that its silly, but so is much of the bureaucratic process behind these grants. Afaik we don't have a policy formulated. On Saturday, May 17, 2014 11:40:25 PM UTC+1, Nathann Cohen wrote: > > Hm... Could we not cite grants in source code ? :-/ > > +This module has, in part, received funding from the European Union's > +Seventh Framework Programme (FP7/2007-2013) under grant agreement > +FP7-ICT-247914. > -- 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 email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Please review #13125
Hm... Could we not cite grants in source code ? :-/ +This module has, in part, received funding from the European Union's +Seventh Framework Programme (FP7/2007-2013) under grant agreement +FP7-ICT-247914. -- 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 email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Notification if a branch gets merge conflicts (changes form "green" to "red")
R. Andrew Ohana wrote: Well it is a bit different than other changes, since nothing actually changes in the ticket itself (which would prompt a notification). Rather the plugin is just a special render for the branch field, so the merge is not actually checked until someone actually loads the page for the first time (results of the merge are cached in the trac database until invalidated). If something along these lines were added, it would have to be in the release management scripts (potentially coupled with a xmlrpc interface to the trac plugin). Yep. But any bot able to comment on tickets (or to send mail) could presumably trigger a recheck when the default milestone changes (i.e., upon a release), and hence indirectly (or directly) notify the involved people if a branch no longer applies. [How exactly does the cache entry get invalidated? Does is just expire?] -leif -- () The ASCII Ribbon Campaign /\ Help Cure HTML E-Mail -- 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 email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Notification if a branch gets merge conflicts (changes form "green" to "red")
Well it is a bit different than other changes, since nothing actually changes in the ticket itself (which would prompt a notification). Rather the plugin is just a special render for the branch field, so the merge is not actually checked until someone actually loads the page for the first time (results of the merge are cached in the trac database until invalidated). If something along these lines were added, it would have to be in the release management scripts (potentially coupled with a xmlrpc interface to the trac plugin). -- 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 email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Please review #13125
bump On Monday, May 12, 2014 1:09:20 PM UTC+1, Volker Braun wrote: > > This fixes some critical bugs in comparison with infinities > -- 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 email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: Notification if a branch gets merge conflicts (changes form "green" to "red")
Ralf Stephan wrote: On Friday, May 16, 2014 1:19:08 PM UTC+2, Wilfried Lübbe wrote: > Would it be possible to reveive an email notification when the color changes to red (like for other changes of the ticket)? And set the ticket to needs-work, *beg*... Alternatively, introduce another trac ticket field, or just fill "Work issues"... -leif -- () The ASCII Ribbon Campaign /\ Help Cure HTML E-Mail -- 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 email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: setuptools install problem
It is possible that the /tmp installation is broken anyway. With setuptools-3.6 I get 4 out of 4 failures because some paths point back to the original sage/ directory, but some not and the underlying files are not there (numpy for example). Moreover, none of the 6.2 TestsPassed runs (n=47) is an unsafe ticket and thus a /tmp install. The snapshot method proposed in another thread gets increasingly attractive to me. On Friday, May 16, 2014 3:58:21 PM UTC+2, Peter Bruin wrote: > > It would be great if that worked. I disabled the tmp directory for the > moment and am testing all tickets in the same directory, but that can leave > the tree in a bad state. > > Peter > > > Op vrijdag 16 mei 2014 10:03:01 UTC+1 schreef Ralf Stephan: >> >> Ah I finally found the relevant upstream ticket: >> >> https://bitbucket.org/pypa/setuptools/issue/168/ez_setuppy-failing-sporadically-when >> which appears resolved with setuptools-3.5.2 >> >> Next is testing of a version >= 3.5.2 >> >> Regards, >> >> On Thursday, May 15, 2014 9:53:36 AM UTC+2, Ralf Stephan wrote: >>> >>> It may be possible to test newer package versions in patchbot without >>> official ticket by forking Sage on github, installing the package in the >>> local >>> Sage, publish the changed branch on github, and use that branch as >>> base_repo with patchbot. This may work also with unsafe tickets because >>> the cloning into /tmp copies upstream/ too. I'm testing that soon. >>> >>> If this doesn't work then my fork of patchbot soon will have a version >>> with a --keep-tmp option that doesn't delete failed installs in /tmp so >>> that the setuptools problem can be postmortemed. I have stopped >>> making pull requests at robertb/patchbot. >>> >>> https://github.com/rwst/patchbot >>> >>> Regards, >>> >>> On Tuesday, May 13, 2014 9:51:17 PM UTC+2, Peter Bruin wrote: I started a patchbot based on 6.3.beta1, and the problem has unfortunately popped up again with the new setuptools version: http://patchbot.sagemath.org/log/16348/debian/wheezy/sid/x86_64/3.2.0-57-generic/selmer/2014-05-13%2019:57:47%20+0100 Op woensdag 7 mei 2014 10:05:32 UTC+1 schreef Ralf Stephan: > > http://trac.sagemath.org/ticket/16300 > > People running patchbot with errors on setuptools install please try > version 2.2b1 of setuptools and report if this changes the behaviour > or not. > > Regards, > -- 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 email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
