From: Roel Janssen <roel@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 39990-done@debbugs.gnu.org
Subject: bug#39990: [PATCH] gnu: Update python-statsmodels to 0.11.1.
Date: Mon, 09 Mar 2020 13:04:59 +0100 [thread overview]
Message-ID: <652eb7e6c92ce135560f96d5681a16d64336b131.camel@gnu.org> (raw)
In-Reply-To: <20200309114749.GM1423@E5400>
On Mon, 2020-03-09 at 13:47 +0200, Efraim Flashner wrote:
> On Mon, Mar 09, 2020 at 12:20:47PM +0100, Roel Janssen wrote:
> > On Mon, 2020-03-09 at 12:45 +0200, Efraim Flashner wrote:
> > > On Sun, Mar 08, 2020 at 11:19:06PM +0100, Roel Janssen wrote:
> > > > Dear Guix,
> > > >
> > > > I'd like to update python-statsmodels because I'm packaging
> > > > something
> > > > that requires a newer version.
> > > >
> > > > The patch is trivial, but I'm unsure whether it would trigger
> > > > too
> > > > many
> > > > rebuilds. How do I check this?
> > >
> > > 'guix refresh --list-dependent python-statsmodels' will give you
> > > a
> > > list of leaf
> > > packages affected by this package. As a python package, you
> > > should
> > > also
> > > check the python2- variant, so 'guix refresh -l python-
> > > statsmodels
> > > python2-statsmodels'
> > >
> >
> > Thanks! Is my conclusion correct that, by updating python-
> > statsmodels
> > (and thus python2-statsmodels), only "ribodiff" will be
> > rebuilt? And
> > therefore, the update can be pushed to master directly?
>
> Yep, straight to master. Although if ribodiff builds before your
> patch
> and then doesn't after you're on the hook to fix it :)
Hehe. Well, it ribodiff seems to fail even with the older python-
statsmodels. I am looking into it right away.
Thanks for your help! I pushed the update in b6574660e3.
Kind regards,
Roel Janssen
prev parent reply other threads:[~2020-03-09 12:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-08 22:19 [bug#39990] [PATCH] gnu: Update python-statsmodels to 0.11.1 Roel Janssen
2020-03-09 10:45 ` Efraim Flashner
2020-03-09 11:20 ` Roel Janssen
2020-03-09 11:47 ` Efraim Flashner
2020-03-09 12:04 ` Roel Janssen [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=652eb7e6c92ce135560f96d5681a16d64336b131.camel@gnu.org \
--to=roel@gnu.org \
--cc=39990-done@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
/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.