all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Vinicius Monego <monego@posteo.net>
Cc: 70089@debbugs.gnu.org
Subject: [bug#70089] [PATCH] gnu: python-scikit-optimize: Update to 0.10.1.
Date: Sun, 02 Jun 2024 11:48:14 +0200	[thread overview]
Message-ID: <875xurn09t.fsf@gnu.org> (raw)
In-Reply-To: <c78a963290cf00cd8b42d51615e38bbe737105a8.1711801711.git.monego@posteo.net> (Vinicius Monego's message of "Sat, 30 Mar 2024 12:30:52 +0000")

Hi Vinicius,

Vinicius Monego <monego@posteo.net> skribis:

> * gnu/packages/python-science.scm (python-scikit-optimize): Update to 0.10.1.
> [source]: Switch to maintained repository. Remove compatibility patches and
> snippet.
> * gnu/packages/patches/python-scikit-optimize-1148.patch,
> gnu/packages/patches/python-scikit-optimize-1148.patch: Remove files.
> * gnu/local.mk (dist_patch_DATA): Remove them.
>
> Change-Id: I6c23c93d3c256b0b97166f80eaeab7f2c7282c5f

qa.guix hasn’t caught up but if it builds and so does python-deepxde,
you should go a head and push it.

Quoth the manual (info "(guix) Commit Access"):

     If you’re committing and pushing your own changes, try and wait at
  least one week (two weeks for more significant changes) after you send
  them for review.  After this, if no one else is available to review them
  and if you’re confident about the changes, it’s OK to commit.

Thanks,
Ludo’.




  reply	other threads:[~2024-06-02  9:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-30 12:30 [bug#70089] [PATCH] gnu: python-scikit-optimize: Update to 0.10.1 Vinicius Monego
2024-06-02  9:48 ` Ludovic Courtès [this message]
2024-07-07  2:20   ` bug#70089: " Vinicius Monego

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=875xurn09t.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=70089@debbugs.gnu.org \
    --cc=monego@posteo.net \
    /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.