unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Gabriel Wicki <gabriel@erlikon.ch>
Cc: 59160@debbugs.gnu.org
Subject: bug#59160: Acknowledgement (Fritzing parts are missing)
Date: Sun, 20 Nov 2022 15:21:30 +0100	[thread overview]
Message-ID: <87leo5hfhb.fsf@nckx> (raw)
In-Reply-To: <87wn83k39i.fsf@erlikon.ch>

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

Gabriel,

Thanks for the patch!

Gabriel Wicki 写道：
> I've come up with the following patch.  It is not optimal 
> (there's still
> some warnings and it makes use of an ugly hack to get rid of a 
> certain
> "Unable to find parts git repository" message) but with that 
> patch
> Fritzing is in a usable state.

[…]

> +             (substitute* "src/version/partschecker.cpp"
> +               ((".*git_libgit2_init.*")
> +                "return 
> \"083nz7vj7a334575smjry6257535h68gglh8a381xxa36dw96aqs\";"))

It doesn't really matter *what* this returns, right?  At least I 
can't find any observable difference.  And as noted on IRC, this 
‘base32’ format is unique to Guix and Nix.

Could you explain the mechanism behind this, er, mechanism?

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2022-11-20 14:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10  1:06 bug#59160: Fritzing parts are missing Gabriel Wicki
     [not found] ` <handler.59160.B.1668042432436.ack@debbugs.gnu.org>
2022-11-10  1:27   ` bug#59160: Acknowledgement (Fritzing parts are missing) Gabriel Wicki
2022-11-20 14:21     ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
     [not found]       ` <87y1s3an08.fsf@erlikon.ch>
2022-12-02 11:20         ` Gabriel Wicki

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=87leo5hfhb.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=59160@debbugs.gnu.org \
    --cc=gabriel@erlikon.ch \
    --cc=me@tobias.gr \
    /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).