all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: 54611@debbugs.gnu.org
Subject: [bug#54611] [WIP PATCH] gnu: Update libgit2 to 1.4.2
Date: Fri, 01 Apr 2022 16:57:59 +0200	[thread overview]
Message-ID: <9dae39b36075035aec8f2eb2d61a3f70575d38c8.camel@telenet.be> (raw)
In-Reply-To: <e27cb0a8f0f19970fd0440df16b49634d1dbf989.camel@telenet.be>

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

Maxime Devos schreef op do 31-03-2022 om 19:11 [+0200]:
* [ ] verify it builds on a 32-bit arch (maybe i686-linux)

It does:

$ /pre-inst-env guix build libgit2 --system=i686-linux --cores=16 --no-grafts
> /gnu/store/gc6f6zkmh5sj2a9gpdp8xf2xqmd7dsdy-libgit2-1.4.2-debug
> /gnu/store/lx1p75x2ljj5f2g6v8ya8pqccr9kgcbn-libgit2-1.4.2
# reproducibility check
$ ./pre-inst-env guix hash -rx /gnu/store/lx1p75x2ljj5f2g6v8ya8pqccr9kgcbn-libgit2-1.4.2
> 05ilpjik1cw1aqnf1i2mnc4ja91p0glr19r2bag2p424l0zbwh9g

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  parent reply	other threads:[~2022-04-01 14:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-28 13:12 [bug#54611] [WIP PATCH] gnu: Update libgit2 to 1.4.2 Maxime Devos
2022-03-29 20:30 ` Maxime Devos
2022-03-31 17:11   ` Maxime Devos
2022-04-01 14:43     ` Maxime Devos
2022-04-01 14:57     ` Maxime Devos [this message]
2022-04-02  4:23       ` Thiago Jung Bauermann via Guix-patches via
2022-04-01 15:05     ` Maxime Devos
2022-04-01 15:09     ` Maxime Devos
2022-04-02  4:07     ` Thiago Jung Bauermann via Guix-patches via
2022-05-11 21:56     ` bug#54611: " Ludovic Courtès
2022-05-12  6:44       ` [bug#54611] " Maxime Devos
2022-04-02  1:59 ` Reviewing the diff when updating a package? Thiago Jung Bauermann
2022-04-02  8:27   ` Maxime Devos
2022-04-02 21:48     ` Thiago Jung Bauermann
2022-04-05 12:34     ` Ludovic Courtès

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=9dae39b36075035aec8f2eb2d61a3f70575d38c8.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=54611@debbugs.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.