all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "André Batista" <nandre@riseup.net>
To: "Clément Lassieur" <clement@lassieur.org>
Cc: 71156@debbugs.gnu.org, guix-devel@gnu.org
Subject: Re: [PATCH] gnu: torbrowser: Update to 13.0.15 [security fixes].
Date: Fri, 31 May 2024 18:49:46 -0300	[thread overview]
Message-ID: <ZlpF-ikbkC8Q_8W_@andel> (raw)
In-Reply-To: <5a936497-2828-407d-842c-a89ccbe6e075@app.fastmail.com>

Hi Clément,

qui 30 mai 2024 às 12:07:58 (1717081678), clement@lassieur.org enviou:
> Hi André,
> 
> I'm currently struggling against a cancer, so it's hard for me to work.  I hope to be better in a few months.  Meanwhile I'll do my best but I'll be slow to react and work.

I'm terribly sorry for you and I do hope you can find the inner strenght
and will to fight it and beat it. I also hope you are well supported
during this hard times.

> I've updated torbrowser and mullvadbrowser but I'm not able to understand how to fix "unknown introductory commit and signer" at the moment.  So I can't push them, they are attached.  I tested my updates.  Please if someone can push them that would be great.

I'll review and test you mullvadbrowser patch and open a new issue in
your place then.

I'll also try to keep this browsers up to date on a more timely manner
whilst you take time to cure yourself. So as to not disturb or pressure
you any longer, I won't be Cc'ing you any longer.

Take care


  parent reply	other threads:[~2024-05-31 21:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-23 23:10 [bug#71156] [PATCH] gnu: torbrowser: Update to 13.0.15 [security fixes] André Batista
2024-05-28 18:33 ` André Batista
2024-05-30 12:07   ` Clément Lassieur
2024-05-30 13:25     ` [bug#71156] " Maxim Cournoyer
2024-05-31 21:49     ` André Batista [this message]
2024-05-29 14:14 ` [bug#71156] [PATCH v2] " André Batista

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=ZlpF-ikbkC8Q_8W_@andel \
    --to=nandre@riseup.net \
    --cc=71156@debbugs.gnu.org \
    --cc=clement@lassieur.org \
    --cc=guix-devel@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.