Re: Restarting 'python-updates'
Marius Bakke writes: > Greetings Guix! > > Python 3.6.2 is scheduled to be released in about a week[0]. > > Our current Python 3.5 is EOL[1], so we should upgrade ASAP. 3.6.2 seems > like a good excuse. It would be good to start building a branch based on > it once it is released (or core-updates is merged, whichever is last). > > Are there any objections to deleting the current 'python-updates' branch > and starting a fresh one? Looking at `git log master..python-updates`, > most of the commits seem to have made their way to 'master' in some form. I think this should wait until after core-updates is merged. Our build farm capacity is already stretched quite thin, and "guix refresh -l python@3" estimates that 2886 rebuilds would be required per architecture. Given the limitations of "guix refresh -l", that might well be an underestimate. So that's at least 8600 builds total, or about half of the entire jobset on Hydra. I don't think we can afford to build this out at the same time as 'core-updates' is being built, and 'master' is being kept up-to-date. Even keeping 'master' up-to-date requires significant resources, given the frequency of updates that require rebuilding most of GNOME, Qt, IceCat, Libreoffice, Webkitgtk, etc. Mark
Re: Restarting 'python-updates'
On Fri, Jun 23, 2017 at 06:36:09PM +0200, Marius Bakke wrote: > Python 3.6.2 is scheduled to be released in about a week[0]. > > Our current Python 3.5 is EOL[1], so we should upgrade ASAP. 3.6.2 seems > like a good excuse. It would be good to start building a branch based on > it once it is released (or core-updates is merged, whichever is last). We could also start sooner with Python 3.6.1, if people are eager to begin working :) > Are there any objections to deleting the current 'python-updates' branch > and starting a fresh one? Looking at `git log master..python-updates`, > most of the commits seem to have made their way to 'master' in some form. No objections! > I would also like to try making the newer versions of 'pytest' and > 'mock' the default and instead add lower versions as necessary. Would > that be too much for one cycle? > > Updating the heavy-impact python libraries will require upgrading many > collateral packages and solving new dependency cycles, so I'm hoping we > can start this effort earlier to make the process smoother. Thoughts? It will be quite a bit of work to upgrade the "core" Python libraries, but we have to do it. Your suggestion to reverse the "default" versions is a good one. I thought this Nix proposal to treat Python tests as their own derivations is an interesting idea for cutting the Gordian knot of Python dependency cycles: https://github.com/NixOS/nixpkgs/issues/26400 But, I don't mind if we skip this for now. It depends on peoples' motivation. However, I want to fix the bytecode caching issue in this cycle. It's a bad performance bug :( https://github.com/NixOS/nixpkgs/issues/22569 signature.asc Description: PGP signature
Restarting 'python-updates'
Greetings Guix! Python 3.6.2 is scheduled to be released in about a week[0]. Our current Python 3.5 is EOL[1], so we should upgrade ASAP. 3.6.2 seems like a good excuse. It would be good to start building a branch based on it once it is released (or core-updates is merged, whichever is last). Are there any objections to deleting the current 'python-updates' branch and starting a fresh one? Looking at `git log master..python-updates`, most of the commits seem to have made their way to 'master' in some form. I would also like to try making the newer versions of 'pytest' and 'mock' the default and instead add lower versions as necessary. Would that be too much for one cycle? Updating the heavy-impact python libraries will require upgrading many collateral packages and solving new dependency cycles, so I'm hoping we can start this effort earlier to make the process smoother. Thoughts? [0] https://www.python.org/dev/peps/pep-0494/ [1] https://www.python.org/dev/peps/pep-0478/ signature.asc Description: PGP signature
Removing the python-updates branch [was Re: bug#25177: Test failures don't cause some Python packages to fail]
On Tue, Dec 13, 2016 at 10:34:03AM +0100, Marius Bakke wrote: > Sounds like we're going down the same road. I've started a branch with > the earlier patch and a few other fixes. Is it ok to overwrite the > existing 'python-updates' branch on Savannah? I'm going to delete that old branch tomorrow if there are no objections. I started it before I knew the magnitude of the work required, and I think it will be easier to start from scratch. signature.asc Description: PGP signature
Re: python-updates
On Fri, Aug 05, 2016 at 05:57:43PM -0400, Mark H Weaver wrote: > Andreas Enge writes: > > > On Fri, Aug 05, 2016 at 11:06:36AM -0400, Leo Famulari wrote: > >> Also, I can do the guile-2.0 update that Ludovic requested. > > > > The patch fails to apply: > >http://hydra.gnu.org:3000/build/1405519/nixlog/1/tail-reload > > Hopefully it is not needed any more? > > guile-arm-fixes.patch should not be needed for guile 2.0.12. Bah, fixed as fd90ea23548b7492631146b8886a5d38d8819f83. Sorry for the sloppiness.
Re: python-updates
Andreas Enge writes: > On Fri, Aug 05, 2016 at 11:06:36AM -0400, Leo Famulari wrote: >> Also, I can do the guile-2.0 update that Ludovic requested. > > The patch fails to apply: >http://hydra.gnu.org:3000/build/1405519/nixlog/1/tail-reload > Hopefully it is not needed any more? guile-arm-fixes.patch should not be needed for guile 2.0.12. Thanks, Mark
Re: python-updates
On Fri, Aug 05, 2016 at 11:06:36AM -0400, Leo Famulari wrote: > Also, I can do the guile-2.0 update that Ludovic requested. The patch fails to apply: http://hydra.gnu.org:3000/build/1405519/nixlog/1/tail-reload Hopefully it is not needed any more? Andreas
Re: python-updates
On Fri, Aug 05, 2016 at 11:06:36AM -0400, Leo Famulari wrote: > Also, I can do the guile-2.0 update that Ludovic requested. This I pushed as bd21159eba2cce3ca7226faa4772df64df06605d > Okay, thanks! But, shouldn't we merge master into python-updates first? > The python-updates branch was rather old. I did the merge locally, but I can't push the result to Savannah. I don't get any useful error messages: $ git push origin python-updates error: failed to push some refs to 'ssh://l...@git.sv.gnu.org/srv/git/guix.git'
Re: python-updates
On Fri, Aug 05, 2016 at 02:13:08PM +0200, Andreas Enge wrote: > On Thu, Aug 04, 2016 at 05:54:21PM -0400, Leo Famulari wrote: > > On Thu, Aug 04, 2016 at 05:23:24PM -0400, Leo Famulari wrote: > > > I'd like to upgrade setuptools as well. I should have pushed a patch for > > > that in an hour or so. > > This is done. Hopefully it all works! > > I added a jobset on hydra: > http://hydra.gnu.org/jobset/gnu/python-updates > > This allowed me to spot a mistake with the setuptools URL, which I corrected; > I will start a new evaluation now. Okay, thanks! But, shouldn't we merge master into python-updates first? The python-updates branch was rather old. Also, I can do the guile-2.0 update that Ludovic requested.
Re: python-updates
On Thu, Aug 04, 2016 at 05:54:21PM -0400, Leo Famulari wrote: > On Thu, Aug 04, 2016 at 05:23:24PM -0400, Leo Famulari wrote: > > I'd like to upgrade setuptools as well. I should have pushed a patch for > > that in an hour or so. > This is done. Hopefully it all works! I added a jobset on hydra: http://hydra.gnu.org/jobset/gnu/python-updates This allowed me to spot a mistake with the setuptools URL, which I corrected; I will start a new evaluation now. Andreas
Re: python-updates
On Thu, Aug 04, 2016 at 05:23:24PM -0400, Leo Famulari wrote: > I'd like to upgrade setuptools as well. I should have pushed a patch for > that in an hour or so. This is done. Hopefully it all works!
Re: python-updates
On Thu, Aug 04, 2016 at 10:56:51PM +0200, Ludovic Courtès wrote: > Hello! > > Leo Famulari skribis: > > > On Mon, Jul 11, 2016 at 10:29:48AM +0200, Ludovic Courtès wrote: > >> The ‘python-updates’ branch would seem right to me. > > > > The brand new python-updates branch is now ready for more Python-related > > commits! > > The build farm is almost idle now, apart from a long list of mips64el > builds. So I think it’s time to merge master in python-updates and get > it built! Thoughts? I'd like to upgrade setuptools as well. I should have pushed a patch for that in an hour or so. > that’s a safe upgrade. The patch below does that, but note that it does > not change ‘guile-2.0/fixed’, which is the Guile we use in all the > derivations; that one we’ll upgrade in core-updates. Okay. I noticed you pasted a diff rather than a patch. Will you push the patch or should one of us?
python-updates
Hello!
Leo Famulari skribis:
> On Mon, Jul 11, 2016 at 10:29:48AM +0200, Ludovic Courtès wrote:
>> The ‘python-updates’ branch would seem right to me.
>
> The brand new python-updates branch is now ready for more Python-related
> commits!
The build farm is almost idle now, apart from a long list of mips64el
builds. So I think it’s time to merge master in python-updates and get
it built! Thoughts?
I think it’s a good idea to upgrade Guile 2.0 at the same time, since
that’s a safe upgrade. The patch below does that, but note that it does
not change ‘guile-2.0/fixed’, which is the Guile we use in all the
derivations; that one we’ll upgrade in core-updates.
Ludo’.
diff --git a/gnu/packages/guile.scm b/gnu/packages/guile.scm
index f50605a..f39e768 100644
--- a/gnu/packages/guile.scm
+++ b/gnu/packages/guile.scm
@@ -130,14 +130,14 @@ without requiring the source code to be rewritten.")
(define-public guile-2.0
(package
(name "guile")
- (version "2.0.11")
+ (version "2.0.12")
(source (origin
(method url-fetch)
(uri (string-append "mirror://gnu/guile/guile-" version
".tar.xz"))
(sha256
(base32
- "1qh3j7308qvsjgwf7h94yqgckpbgz2k3yqdkzsyhqcafvfka9l5f"))
+ "1sdpjq0jf1h65w29q0zprj4x6kdp5jskkvbnlwphy9lvdxrqg0fy"))
(patches (search-patches "guile-arm-fixes.patch"
(build-system gnu-build-system)
(native-inputs `(("pkgconfig" ,pkg-config)))
@@ -199,7 +199,17 @@ without requiring the source code to be rewritten.")
(define-public guile-2.0/fixed
;; A package of Guile 2.0 that's rarely changed. It is the one used
;; in the `base' module, and thus changing it entails a full rebuild.
- guile-2.0)
+ (package
+(inherit guile-2.0)
+(version "2.0.11")
+(source (origin
+ (method url-fetch)
+ (uri (string-append "mirror://gnu/guile/guile-" version
+ ".tar.xz"))
+ (sha256
+ (base32
+"1qh3j7308qvsjgwf7h94yqgckpbgz2k3yqdkzsyhqcafvfka9l5f"))
+ (patches (search-patches "guile-arm-fixes.patch"))
(define-public guile-next
(package (inherit guile-2.0)
Re: python-updates!
Ludovic Courtès writes: > Leo Famulari skribis: > >> On Mon, Jul 11, 2016 at 10:29:48AM +0200, Ludovic Courtès wrote: >>> The ‘python-updates’ branch would seem right to me. >> >> The brand new python-updates branch is now ready for more Python-related >> commits! > > Excellent. Time to apply the Python updates that Chris and Hartmut (I > think?) submitted a while back! > > Thanks, > Ludo’. Yes, I submitted a patch with support for Python 3.5, built off of Diane's work. There were a couple of smallish things that you (Ludo) asked me to do... unfortunately I haven't gotten to it... but it shouldn't take anyone long, if someone gets to it before I do.
python-updates!
Leo Famulari skribis: > On Mon, Jul 11, 2016 at 10:29:48AM +0200, Ludovic Courtès wrote: >> The ‘python-updates’ branch would seem right to me. > > The brand new python-updates branch is now ready for more Python-related > commits! Excellent. Time to apply the Python updates that Chris and Hartmut (I think?) submitted a while back! Thanks, Ludo’.
Re: Python updates
Andreas Enge skribis: > Backtrace: > In ice-9/boot-9.scm: > 157: 16 [catch #t # ...] > In unknown file: >?: 15 [apply-smob/1 #] > In ice-9/boot-9.scm: > 63: 14 [call-with-prompt prompt0 ...] > In ice-9/eval.scm: > 432: 13 [eval # #] > In ice-9/boot-9.scm: > 2401: 12 [save-module-excursion # ()>] > 4050: 11 [#] > 1724: 10 [%start-stack load-stack # ice-9/boot-9.scm:4041:10 ()>] > 1729: 9 [#] > In unknown file: >?: 8 [primitive-load "/home/privat/Programme/guix/scripts/guix"] > In guix/ui.scm: > 1173: 7 [run-guix-command refresh] > In ice-9/boot-9.scm: > 157: 6 [catch srfi-34 # ...] > 157: 5 [catch system-error ...] > In srfi/srfi-1.scm: > 616: 4 [for-each # (package)> ...] > In guix/scripts/refresh.scm: > 391: 3 [# #] > In guix/upstream.scm: > 136: 2 [package-update-path # #] > In guix/import/pypi.scm: > 237: 1 [latest-release "ansible"] > In unknown file: >?: 0 [scm-error misc-error #f ...] > > ERROR: In procedure scm-error: > ERROR: No source release found for pypi package: "ansible" "2.0.0" We have a bug here; updaters should never fail. Fixed in 85dce71. Ludo’.
Re: Python updates
Ricardo Wurmus writes: >> gnu/packages/python.scm:4221:4: python2-ipython would be upgraded from 3.2.1 >> to 4.0.1 > > I’m working on this but there are still many problems with IPython. > I’ll try to polish and submit the patches tomorrow. Upgrading 'ipython' to version 4.0 will break 'emacs-ob-ipython'. If you upgrade the former, could you please also take care of the latter. We should be careful to check that we don't break dependencies by upgrades... Thanks, Fede
Re: Python updates
> gnu/packages/python.scm:4221:4: python2-ipython would be upgraded from 3.2.1 > to 4.0.1 I’m working on this but there are still many problems with IPython. I’ll try to polish and submit the patches tomorrow. ~~ Ricardo
Re: Python updates
On Mon, 30 Nov 2015 20:19:04 +0100 Andreas Enge wrote: > Hello, > > I just ran "guix refresh", and it seems there are lots of python packages > to be updated, sometimes with version jumps to 2.0.0 or 3.0.0. Avis aux > amateurs! (Translation: If there are python lovers with a bit of time out > there, it would be nice if they could have a look, update the packages and > check whether the dependent packages still build.) > > Andreas > > > PS: The output of "guix refresh": > [...] I was actually thinking of looking at this when I finish my current python project. In case anyone else wants to take a look at it sooner, one of the circular dependencies in the updates is python-mock-1.3.0 depends on python-pbr-0.11, which depends on python-pip, which depends on python-mock (for tests). Also, updating python-urwid doesn't automatically fix the build failures. -- Efraim Flashner אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted pgp4tvWAbaKRo.pgp Description: OpenPGP digital signature
Python updates
Hello, I just ran "guix refresh", and it seems there are lots of python packages to be updated, sometimes with version jumps to 2.0.0 or 3.0.0. Avis aux amateurs! (Translation: If there are python lovers with a bit of time out there, it would be nice if they could have a look, update the packages and check whether the dependent packages still build.) Andreas PS: The output of "guix refresh": gnu/packages/wget.scm:35:13: wget would be upgraded from 1.16.3 to 1.17 gnu/packages/web.scm:2894:13: r-jsonlite would be upgraded from 0.9.17 to 0.9.19 gnu/packages/web.scm:2985:13: r-curl would be upgraded from 0.9.3 to 0.9.4 gnu/packages/tls.scm:43:13: libtasn1 would be upgraded from 4.5 to 4.7 gnu/packages/statistics.scm:948:13: python-patsy would be upgraded from 0.4.0 to 0.4.1 gnu/packages/statistics.scm:725:13: r-microbenchmark would be upgraded from 1.4-2 to 1.4-2.1 gnu/packages/statistics.scm:370:13: r-stringi would be upgraded from 0.5-5 to 1.0-1 gnu/packages/statistics.scm:1147:13: r-roxygen2 would be upgraded from 5.0.0 to 5.0.1 gnu/packages/statistics.scm:986:4: python2-patsy would be upgraded from 0.4.0 to 0.4.1 gnu/packages/statistics.scm:827:13: r-testthat would be upgraded from 0.10.0 to 0.11.0 gnu/packages/rdf.scm:364:4: python2-rdflib would be upgraded from 4.1.2 to 4.2.1 gnu/packages/rdf.scm:333:13: python-rdflib would be upgraded from 4.1.2 to 4.2.1 gnu/packages/python.scm:5557:13: python2-ipaddress would be upgraded from 1.0.14 to 1.0.15 gnu/packages/python.scm:5421:13: python2-monotonic would be upgraded from 0.3 to 0.4 gnu/packages/python.scm:762:13: python-setuptools would be upgraded from 18.3.1 to 18.7 gnu/packages/python.scm:2624:13: python-blinker would be upgraded from 1.3 to 1.4 gnu/packages/python.scm:2164:13: python-jsonschema would be upgraded from 2.4.0 to 2.5.1 gnu/packages/python.scm:2524:13: python2-sphinx would be upgraded from 1.2.3 to 1.3.2 gnu/packages/python.scm:4599:13: python2-networkx would be upgraded from 1.9.1 to 1.10 gnu/packages/python.scm:3738:13: python-xcffib would be upgraded from 0.1.9 to 0.4.0 gnu/packages/python.scm:1944:13: python2-coverage would be upgraded from 3.7.1 to 4.0.3 gnu/packages/python.scm:2082:13: python-certifi would be upgraded from 14.05.14 to 2015.11.20.1 gnu/packages/python.scm:4303:13: python2-urwid would be upgraded from 1.3.0 to 1.3.1 gnu/packages/python.scm:1597:13: python2-pytest would be upgraded from 2.6.1 to 2.8.3 gnu/packages/python.scm:3645:13: python-pycparser would be upgraded from 2.10 to 2.14 gnu/packages/python.scm:1999:13: behave would be upgraded from 1.2.4 to 1.2.5 gnu/packages/python.scm:5421:13: python-monotonic would be upgraded from 0.3 to 0.4 gnu/packages/python.scm:4374:13: python2-apsw would be upgraded from 3.8.7.3-r1 to 3.8.11.1-r1 gnu/packages/python.scm:341:13: python2-psutil would be upgraded from 3.0.1 to 3.3.0 gnu/packages/python.scm:4221:4: python2-ipython would be upgraded from 3.2.1 to 4.0.1 gnu/packages/python.scm:914:13: python2-dateutil would be upgraded from 2.2 to 2.4.2 gnu/packages/python.scm:3837:13: python2-decorator would be upgraded from 3.4.2 to 4.0.4 gnu/packages/python.scm:3980:13: python2-pathpy would be upgraded from 8.1.1 to 8.1.2 gnu/packages/python.scm:1944:13: python-coverage would be upgraded from 3.7.1 to 4.0.3 gnu/packages/python.scm:4303:13: python-urwid would be upgraded from 1.3.0 to 1.3.1 gnu/packages/python.scm:1168:13: python2-simplejson would be upgraded from 3.3.0 to 3.8.1 gnu/packages/python.scm:1597:13: python-pytest would be upgraded from 2.6.1 to 2.8.3 gnu/packages/python.scm:2524:13: python-sphinx would be upgraded from 1.2.3 to 1.3.2 gnu/packages/python.scm:4374:13: python-apsw would be upgraded from 3.8.7.3-r1 to 3.8.11.1-r1 gnu/packages/python.scm:988:13: python2-pandas would be upgraded from 0.16.0 to 0.17.1 gnu/packages/python.scm:2963:13: python2-fastlmm would be upgraded from 0.2.14 to 0.2.21 gnu/packages/python.scm:2441:13: python2-joblib would be upgraded from 0.9.0b4 to 0.9.3 gnu/packages/python.scm:1502:13: python2-nose would be upgraded from 1.3.4 to 1.3.7 gnu/packages/python.scm:341:13: python-psutil would be upgraded from 3.0.1 to 3.3.0 gnu/packages/python.scm:1064:13: python2-pysam would be upgraded from 0.8.1 to 0.8.4 gnu/packages/python.scm:914:13: python-dateutil would be upgraded from 2.2 to 2.4.2 gnu/packages/python.scm:3980:13: python-pathpy would be upgraded from 8.1.1 to 8.1.2 gnu/packages/python.scm:2624:13: python2-blinker would be upgraded from 1.3 to 1.4 gnu/packages/python.scm:3837:13: python-decorator would be upgraded from 3.4.2 to 4.0.4 gnu/packages/python.scm:2391:13: python2-jinja2 would be upgraded from 2.7.3 to 2.8 gnu/packages/python.scm:1168:13: python-simplejson would be upgraded from 3.3.0 to 3.8.1 gnu/packages/python.scm:5039:13: python2-flake8 would be upgraded from 2.4.1 to 2.5.0 gnu/packages/python.scm:988:13: python-pandas would be upgraded from 0.16.0 to 0.17.1 gnu/packages/python.
