From: Vinicius Monego <monego@posteo.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 70089-done@debbugs.gnu.org
Subject: bug#70089: [PATCH] gnu: python-scikit-optimize: Update to 0.10.1.
Date: Sun, 07 Jul 2024 02:20:17 +0000 [thread overview]
Message-ID: <0730be2ba79963bd8e226b3d3fbb513bc9e5aff7.camel@posteo.net> (raw)
In-Reply-To: <875xurn09t.fsf@gnu.org>
Em dom, 2024-06-02 às 11:48 +0200, Ludovic Courtès escreveu:
> 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’.
Done, thanks.
Vinicius
prev parent reply other threads:[~2024-07-07 2:22 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
2024-07-07 2:20 ` Vinicius Monego [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=0730be2ba79963bd8e226b3d3fbb513bc9e5aff7.camel@posteo.net \
--to=monego@posteo.net \
--cc=70089-done@debbugs.gnu.org \
--cc=ludo@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.