From: Greg Hogan <code@greghogan.com>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: 65636@debbugs.gnu.org
Subject: [bug#65636] [PATCH] gnu: git: Update to 2.42.0.
Date: Tue, 17 Oct 2023 18:31:04 -0400 [thread overview]
Message-ID: <CA+3U0Z=oFAFPrPgxw0uxwE1E47wadxs_a-q_cWAR=fJ4eVa1vA@mail.gmail.com> (raw)
In-Reply-To: <86r0mq62v1.fsf@gmail.com>
On Fri, Sep 22, 2023 at 4:15 AM Simon Tournier <zimon.toutoune@gmail.com> wrote:
>
> Hi,
>
> On Wed, 30 Aug 2023 at 19:03, Greg Hogan <code@greghogan.com> wrote:
> > * gnu/packages/version-control.scm (git): Update to 2.42.0.
> > ---
> > gnu/packages/version-control.scm | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
>
> This change implies a lot of rebuilds – more than the QA threshold.
>
> So I have applied and rebuilt all the packages (for x86_64 only, which
> is already something for my resources :-)) listed by “guix refresh -l
> git git-minimal”. This update breaks these 9 packages:
>
> conan
> nototools
> python-bash-kernel
> python-clinguin
> python-h3
> python-jwst
> python-keras
> python-poliastro
> python-telingo
>
> Could you give a look?
python-jwst and python-poliastro fail to build for me on master
(c96ea941) due to test failures with floating point precision.
The remaining packages build successfully against this git 2.42 patch:
$ ./pre-inst-env guix build conan nototools python-bash-kernel
python-clinguin python-h3 python-keras python-telingo
/gnu/store/5lpypnafi7akb9yya82l29x4zrkgsw1v-python-telingo-2.1.1
/gnu/store/d7hmxpipghw74v4bdk3gy1xq0k789a8q-python-keras-2.3.1
/gnu/store/rq51438czgcab9d9vp0wl09k4myvbkj8-python-h3-4.0.0b2
/gnu/store/smrfjip766ifrcf3pzsfbjzp4hdsabd1-python-clinguin-1.0.0-beta
/gnu/store/z0fzl2g7pdp94hdpq5llmjlq20v5wfl2-python-bash-kernel-0.7.2
/gnu/store/8xymw6wdw782z35djznx8ssqszfb4lff-nototools-0.2.16
/gnu/store/n8v7xm47cawirwdmll79ismdzlwja54w-conan-2.0.9
> Well, considering the current model for merging, this change could
> directly go to master (and avoid a core-updates cycle) since CI should
> be able to handle the ~800 rebuilds. However, I would prefer to avoid
> the introduction of breakages. :-)
>
> Cheers,
> simon
next prev parent reply other threads:[~2023-10-17 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 19:03 [bug#65636] [PATCH] gnu: git: Update to 2.42.0 Greg Hogan
2023-09-22 8:14 ` Simon Tournier
2023-10-17 22:31 ` Greg Hogan [this message]
2023-11-21 13:14 ` bug#65636: " Greg Hogan
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='CA+3U0Z=oFAFPrPgxw0uxwE1E47wadxs_a-q_cWAR=fJ4eVa1vA@mail.gmail.com' \
--to=code@greghogan.com \
--cc=65636@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).