From: zimoun <zimon.toutoune@gmail.com>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: 39575@debbugs.gnu.org
Subject: bug#39575: guix time-machine fails when a tarball was modified in-place
Date: Fri, 14 Feb 2020 11:56:18 +0100 [thread overview]
Message-ID: <CAJ3okZ1X_AHLCOJ3z3fd91Kz_S1aOVvSnge2VKkeHrk90sAiNA@mail.gmail.com> (raw)
In-Reply-To: <87y2t5a3ks.fsf@roquette.mug.biscuolo.net>
Hi Giovanni,
On Fri, 14 Feb 2020 at 11:07, Giovanni Biscuolo <g@xelera.eu> wrote:
> Ludovic Courtès <ludo@gnu.org> writes:
> > The problem here is really that we fall back to content-addressed
> > mirrors instead of using them directly:
> >
> > https://issues.guix.gnu.org/issue/28659
>
> Given the natute (AFAIU) of this issue is the very same of the bug you
> mention, shouldn't this bug be merged (forcemerged?) whith #28659?
AFAIU, there is 2 issues:
1. how to do with the particular case of harfbuzz -- bug#39575
2. how to solve the general case of unreliable sources -- bug#28659
So instead of merging the bugs (case 2.), I would like to solve 1.,
mark it as done and report to bug#28659. It will ease to follow
because the thread in bug#28659 is already heavy. :-)
All the best,
simon
next prev parent reply other threads:[~2020-02-14 10:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 13:40 bug#39575: guix time-machine fails when a tarball was modified in-place Jan Nieuwenhuizen
2020-02-12 14:55 ` zimoun
2020-02-13 21:34 ` Ludovic Courtès
2020-02-14 1:05 ` zimoun
2020-02-14 10:03 ` Giovanni Biscuolo
2020-02-14 10:56 ` zimoun [this message]
2020-02-14 10:47 ` zimoun
2020-02-14 12:26 ` Ludovic Courtès
2020-02-14 13:24 ` Jan Nieuwenhuizen
2020-02-14 13:51 ` Ludovic Courtès
2020-02-15 15:32 ` zimoun
2020-02-15 20:01 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-02-15 23:57 ` Bengt Richter
2020-02-17 8:47 ` zimoun
2020-02-17 13:26 ` Efraim Flashner
2020-02-17 15:02 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-02-17 18:32 ` zimoun
2020-02-19 11:58 ` Jan Nieuwenhuizen
2020-02-21 15:58 ` zimoun
2020-02-21 20:48 ` Ludovic Courtès
2020-02-14 12:45 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-02-14 13:14 ` Ludovic Courtès
2020-02-15 15:51 ` zimoun
2020-02-14 13:45 ` Jan Nieuwenhuizen
2020-02-14 21:34 ` Ludovic Courtès
2020-02-15 15:43 ` bug#28659: " zimoun
2020-02-16 10:59 ` Ludovic Courtès
2020-02-17 10:18 ` zimoun
2020-02-17 14:40 ` bug#28659: " Ludovic Courtès
2020-02-17 15:04 ` zimoun
2020-09-09 14:31 ` bug#28659: Content-addressed mirror is not used upon invalid hash zimoun
2020-09-10 8:14 ` 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
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=CAJ3okZ1X_AHLCOJ3z3fd91Kz_S1aOVvSnge2VKkeHrk90sAiNA@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=39575@debbugs.gnu.org \
--cc=g@xelera.eu \
/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).