[sage-devel] Re: spkg statistics
And speaking of version bumps, there is a trivial IPython update that has been sitting on trac for two weeks: http://trac.sagemath.org/14810 -- 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/groups/opt_out.
[sage-devel] Re: spkg statistics
I'd be happy if there were more frequent reviews of updated packages, for example I packaged Gap-4.6.3 (http://trac.sagemath.org/14039) and it just lingered on trac until 4.6.4 came out. IMHO we should just get rid of some of the red tap for pure version bumps; If the package maintainer makes an update to the latest upstream then there is no point in somebody reviewing that, it should just be updated automatically. E.g. in Fedora package rpm updates are pushed either immediately by review (Bodhi karma) or after a certain time (2 weeks) without negative feedback. The 4ti2 spkg is currently broken with newer gccs http://trac.sagemath.org/13498 so the dozen downloads or so might just be one person trying to compile it on multiple machines. AFAIK it doesn't do anything that Sage can't do without 4ti2, so its mostly there to satisfy requirements of other packages. -- 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/groups/opt_out.
[sage-devel] Re: spkg statistics
Hi Volker, On 2013-07-05, Volker Braun vbraun.n...@gmail.com wrote: I'd be happy if there were more frequent reviews of updated packages, for example I packaged Gap-4.6.3 (http://trac.sagemath.org/14039) and it just lingered on trac until 4.6.4 came out. IMHO we should just get rid of some of the red tap for pure version bumps; If the package maintainer makes an update to the latest upstream then there is no point in somebody reviewing that, it should just be updated automatically. If I am not mistaken, the last version bump of Gap gave rise to several doctests that needed to be fixed. At least, in my p_group_cohomology spkg, I needed to fix stuff because of a change in some random generator in Gap. So, a version bump requires at least a make ptestlong check. Best regards, Simon -- 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/groups/opt_out.
[sage-devel] Re: spkg statistics
Sorry if I wasn't clear, the package maintainer must of course make sure that the doctests pass. Usually there are some minor changes, e.g. we do doctest the GAP version number which will always change. Or the output order of the upstream source changes. That does require some good judgement to verify that the output is still correct, but is there anybody who is better qualified to check that than the spkg maintainer? An really subtle bugs will only be found when the code is actually used, not by having it bitrot on a trac ticket. On Friday, July 5, 2013 11:17:40 AM UTC-4, Simon King wrote: If I am not mistaken, the last version bump of Gap gave rise to several doctests that needed to be fixed. At least, in my p_group_cohomology spkg, I needed to fix stuff because of a change in some random generator in Gap. So, a version bump requires at least a make ptestlong check. -- 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/groups/opt_out.
Re: [sage-devel] Re: spkg statistics
Interesting stats. On Fri, Jul 5, 2013 at 8:13 AM, Volker Braun vbraun.n...@gmail.com wrote: I'd be happy if there were more frequent reviews of updated packages, for example I packaged Gap-4.6.3 (http://trac.sagemath.org/14039) and it just lingered on trac until 4.6.4 came out. IMHO we should just get rid of some of the red tap for pure version bumps; If the package maintainer makes an update to the latest upstream then there is no point in somebody reviewing that, it should just be updated automatically. E.g. in Fedora package rpm updates are pushed either immediately by review (Bodhi karma) or after a certain time (2 weeks) without negative feedback. +1. Hopefully with git it'll be as simple as changing the version number via a git pull and uploading/pointing to a new upstream tarball, and the patchbot will be able to test it so a trivial bump will be a trivial review. The 4ti2 spkg is currently broken with newer gccs http://trac.sagemath.org/13498 so the dozen downloads or so might just be one person trying to compile it on multiple machines. AFAIK it doesn't do anything that Sage can't do without 4ti2, so its mostly there to satisfy requirements of other packages. -- 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/groups/opt_out. -- 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/groups/opt_out.
