all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Alex Vong <alexvong1995@gmail.com>,
	Ben Woodcroft <b.woodcroft@uq.edu.au>
Cc: guix-devel@gnu.org
Subject: Re: 03/03: gnu: python-dateutil: Update to 2.6.1.
Date: Thu, 01 Feb 2018 12:21:00 +0100	[thread overview]
Message-ID: <87lggdot0j.fsf@fastmail.com> (raw)
In-Reply-To: <87607iw8xg.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1781 bytes --]

Alex Vong <alexvong1995@gmail.com> writes:

> Ben Woodcroft <b.woodcroft@uq.edu.au> writes:
>
>> On 31/01/18 16:18, Alex Vong wrote:
>>> Ben Woodcroft <b.woodcroft@uq.edu.au> writes:
>>>
>>>> Hi Mark, Marius,
>>>>
>>>>
>>>> On 31/01/18 12:52, Mark H Weaver wrote:
>>>>> Hi,
>>>>>
>>>>> mbakke@fastmail.com (Marius Bakke) writes:
>>>>>
>>>>>> mbakke pushed a commit to branch master
>>>>>> in repository guix.
>>>>>>
>>>>>> commit b94502bed69c0fb5033d702fd0308209efb8815c
>>>>>> Author: Alex Vong <alexvong1995@gmail.com>
>>>>>> Date:   Sat Jan 27 22:58:58 2018 +0800
>>>>>>
>>>>>>       gnu: python-dateutil: Update to 2.6.1.
>>>>>>            * gnu/packages/python.scm (python-dateutil,
>>>>>> python2-dateutil): Update to
>>>>>>       2.6.1.
>>>>> This seems to have broken 'python-pandas'.
>>>> 'python-pandas' on master needs to be updated to 0.22, but testing the
>>>> updated version requires adding further packages and doing a few
>>>> updates. I have been working on this (slowly) on 'core-updates' since
>>>> it requires updates to some of the more core python testing
>>>> packages. I have a draft set of packages
>>>>
>>>> WDYT about updating it on the master branch but disabling automated
>>>> tests until 'core-updates' is merged?
>>>>
>>> or maybe revert the python-dateutil commit for now? I don't think there
>>> is a package relying on the latest version of python-dateutil. I am
>>> going to package something depending on python-dateutil, but I think it
>>> should work on the older version of python-dateutil as well. WDYT?
>>
>> Sure, if you like.
>>  ben
>
> Oh, I forget to mention: to apply it to core-updates instead.

I reverted it on 'master' and will merge it to core-updates and add it
there shortly.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

      reply	other threads:[~2018-02-01 11:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180127175208.8250.59896@vcs0.savannah.gnu.org>
     [not found] ` <20180127175209.C391220B05@vcs0.savannah.gnu.org>
2018-01-31  2:52   ` 03/03: gnu: python-dateutil: Update to 2.6.1 Mark H Weaver
2018-01-31  6:03     ` Ben Woodcroft
2018-01-31  6:18       ` Alex Vong
2018-01-31  6:34         ` Ben Woodcroft
2018-01-31 11:43           ` Alex Vong
2018-02-01 11:21             ` Marius Bakke [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lggdot0j.fsf@fastmail.com \
    --to=mbakke@fastmail.com \
    --cc=alexvong1995@gmail.com \
    --cc=b.woodcroft@uq.edu.au \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.