unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Zacchaeus Scheffer <Zacchaeus.Scheffer@synaptics.com>
To: zimoun <zimon.toutoune@gmail.com>,
	"60545@debbugs.gnu.org" <60545@debbugs.gnu.org>
Subject: bug#60545: Keras h5py Version Mismatch
Date: Tue, 31 Jan 2023 23:01:16 +0000	[thread overview]
Message-ID: <CY4PR03MB27599F8ABE114B8822E4ABFF98D09@CY4PR03MB2759.namprd03.prod.outlook.com> (raw)
In-Reply-To: <87o7rbiv4m.fsf@gmail.com>

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

Hi,

I should probably mention that I am not looking into this.  I want to learn more guix, but keras and the additional dependencies required for later versions is kind of a monster to me at the moment.

Thanks,
Zacchae
________________________________
From: zimoun <zimon.toutoune@gmail.com>
Sent: Friday, January 6, 2023 6:40 AM
To: Zacchaeus Scheffer <Zacchaeus.Scheffer@synaptics.com>; 60545@debbugs.gnu.org <60545@debbugs.gnu.org>
Subject: Re: bug#60545: Keras h5py Version Mismatch

CAUTION: Email originated externally, do not click links or open attachments unless you recognize the sender and know the content is safe.


Hi,

On Wed, 04 Jan 2023 at 01:37, Zacchaeus Scheffer <Zacchaeus.Scheffer@synaptics.com> wrote:

> working (pip): keras 2.10.0, h5py 3.7.0
> not working (current guix): keras 2.2.4, h5py 3.6.0

Indeed, it is collateral to ea403bf290f4bf8c7bae314e32dbb90653f92996

--8<---------------cut here---------------start------------->8---
gnu: python-h5py: Update to 3.6.0.

* gnu/packages/python-xyz.scm (python-h5py): Update to 3.6.0.
[arguments]: Set HDF5_DIR variable instead of patching files.
--8<---------------cut here---------------end--------------->8---

Well, the update of Keras to 2.11.0 (the current latest) requires some
work.  First, fetch from Github instead of PyPI because the sources are
not available after v2.6.0; e.g.,

    https://urldefense.proofpoint.com/v2/url?u=https-3A__pypi.org_project_keras_2.11.0_-23files&d=DwIBAg&c=7dfBJ8cXbWjhc0BhImu8wVIoUFmBzj1s88r8EGyM0UY&r=1moyBSYvgSFmdTYHNEHEwakZGFkPl3pixLezH1qWWXFZPpSXOvpoeGr4XIg6G8V0&m=NqD4egq46utBpoyT-8Gr6A3lESGvdg2j7CIMrB0r_y4I-pFRV2Gxn2-Lb7s7tsyD&s=Ro23h-Sd5x7VKOXeIYl4j5KGqDMAyZprruKUgdacbCo&e=

Then, second adapt the recipe.  Do you want to give a try?


Cheers,
simon


[-- Attachment #2: Type: text/html, Size: 4052 bytes --]

      reply	other threads:[~2023-02-01  1:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04  1:37 bug#60545: Keras h5py Version Mismatch Zacchaeus Scheffer
2023-01-06 14:40 ` zimoun
2023-01-31 23:01   ` Zacchaeus Scheffer [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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=CY4PR03MB27599F8ABE114B8822E4ABFF98D09@CY4PR03MB2759.namprd03.prod.outlook.com \
    --to=zacchaeus.scheffer@synaptics.com \
    --cc=60545@debbugs.gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).