GNU bug report logs - #72333
Magit/Transient error message

Previous Next

Full log

Message #64 received at 72333 <at> debbugs.gnu.org (full text, mbox):

From: Liliana Marie Prikler <liliana.prikler <at> gmail.com>
To: Rutherther <rutherther <at> protonmail.com>, 72333 <at> debbugs.gnu.org
Cc: Alvin Hsu <alvinhsu2002 <at> gmail.com>, aurtzy <aurtzy <at> gmail.com>,
 Simon Tournier <zimon.toutoune <at> gmail.com>, Tomas Volf <~@wolfsden.cz>,
 daniel szmulewicz <daniel.szmulewicz <at> gmail.com>,
 gemmaro <gemmaro.dev <at> gmail.com>, Richard Sent <richard <at> freakingpenguin.com>
Subject: Re: Magit/Transient error message
Date: Sat, 14 Sep 2024 21:12:57 +0200

Am Samstag, dem 14.09.2024 um 17:53 +0000 schrieb Rutherther:
> 
> From Liliana dmarie Prikler:
> > It is a bug unique to our handling in Guix – upstream uses hashes
> > to guard against it, but those break grafts.
> 
> Do we need to remove the whole hash? The path hash would definitely
> break grafts, but why should the content hash break grafts? Having
> the content hash would also solve this issue.
> 
> Here is the upstream explanation for the hash
> https://git.savannah.gnu.org/cgit/emacs.git/tree/src/comp.c?h=194a8f5c1406dd7e762376bdfde78d1b7d01b6b1#n4433
> having two parts, path and content hash.
Because the content hash also refers to stuff that we're grafting, e.g.
program names that get compiled to store paths.  It's sadly not that
easy.

Cheers

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.