rebase to 6.0
Merge branch 'ticket/9457' into ticket/9457.2
updated database_cremona_ellcurve pkg
do not test that elapsed time is 0.00s
Let ATLAS build on Cygwin64.
accept Laurent series in PowerSeriesRing._element_constructor_()
Merge branch 'u/niles/ticket/9457.2' of git://trac.sagemath.org/sage into ticket/9457-power_series_comparison
reviewer patch for #8198
Add comment about not picking up Win64 as OS on Cygwin64.
Trac #6431: PowerSeriesRing._element_constructor_() does not accept Laurent series

{{{
sage: CDF[['t']]( ~(~CDF[['t']].gen()^2) )
Traceback (most recent call last):
...
TypeError: a float is required
}}}

URL: http://trac.sagemath.org/6431
Reported by: ncalexan
Ticket author(s): Peter Bruin
Reviewer(s): Marc Mezzarobba
Trac #9457: power series equality fails when trailing coefficients are zero

Comparison of power series uses `list` instead of `padded_list`.  This
drops trailing zeros, and means that power series equality is buggy:

{{{
sage: A.<t> = PowerSeriesRing(ZZ)
sage: g = t + t^3 + t^5 + O(t^6); g
t + t^3 + t^5 + O(t^6)
sage: g == t + O(t^3)   # should be True
False

sage: [g == g.add_bigoh(i) for i in range(7)]    # these should all be
True
[True, False, True, False, True, False, True]

sage: g.add_bigoh(3).list()  # drops trailing zero
[0, 1]
sage: g.add_bigoh(3).padded_list()
[0, 1, 0]
}}}

URL: http://trac.sagemath.org/9457
Reported by: niles
Ticket author(s): Niles Johnson
Reviewer(s): Peter Bruin
Trac #16112: Let ATLAS build on Cygwin64

A line I introduced in #14605 actually prevent ATLAS from building...

URL: http://trac.sagemath.org/16112
Reported by: jpflori
Ticket author(s): Jean-Pierre Flori
Reviewer(s): Sebastien Gouezel
Trac #16013: Update Cremona's table of elliptic curves to 340000

The new upstream tarball is at

  http://boxen.math.washington.edu/home/cremona/database_cremona_ellcurv
e-20140325.tar.bz2

The new commit only changes the package-version.txt and checksums.ini
files.

URL: http://trac.sagemath.org/16013
Reported by: cremona
Ticket author(s): John Cremona
Reviewer(s): Jeroen Demeyer
Trac #16109: Timing instability in doctest reporter

Random doctest failure on the buildbot:
{{{
sage -t --long src/sage/doctest/reporting.py
**********************************************************************
File "src/sage/doctest/reporting.py", line 265, in
sage.doctest.reporting.DocTestReporter.report
Failed example:
    DTR.report(FDS, False, 0, (sum([len(t.examples) for t in doctests]),
D), "Good tests")
Expected:
        [... tests, 0.00 s]
Got:
        [103 tests, 0.01 s]
**********************************************************************
File "src/sage/doctest/reporting.py", line 275, in
sage.doctest.reporting.DocTestReporter.report
Failed example:
    DTR.report(FDS, False, 0, (sum([len(t.examples) for t in doctests]),
D), "Doctest output including the failure...")
Expected:
        [... tests, 1 failure, 0.00 s]
Got:
        [103 tests, 1 failure, 0.01 s]
**********************************************************************
File "src/sage/doctest/reporting.py", line 289, in
sage.doctest.reporting.DocTestReporter.report
Failed example:
    DTR.report(FDS, False, 0, (sum([len(t.examples) for t in doctests]),
D), "Good tests")
Expected:
        1 unlabeled test not run
        4 long tests not run
        5 magma tests not run
        2 other tests skipped
        [... tests, 0.00 s]
Got:
        1 unlabeled test not run
        4 long tests not run
        5 magma tests not run
        2 other tests skipped
        [103 tests, 0.01 s]
**********************************************************************
}}}
obviously we shouldn't doctest that the time is really 0.00s

URL: http://trac.sagemath.org/16109
Reported by: vbraun
Ticket author(s): Volker Braun
Reviewer(s): Jeroen Demeyer