From: Maxime Devos <maximedevos@telenet.be>
To: timflutre@gmail.com, zimoun <zimon.toutoune@gmail.com>
Cc: GNU bug tracker automated control server
<control@debbugs.gnu.org>,
58526@debbugs.gnu.org
Subject: bug#58526: bug report upgrading Guix from 1.0.1 to 1.3
Date: Sun, 16 Oct 2022 18:26:55 +0200 [thread overview]
Message-ID: <f489e6e5-6e08-5d24-4823-c9e76f5cf5f1@telenet.be> (raw)
In-Reply-To: <CAGJVmuJ2WPcm2kuquC_x2KfK40eS1kn2XirrG-attrLj=oB9mw@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 582 bytes --]
merge 58149 58526
thanks
On 16-10-2022 17:25, Timothée Flutre wrote:
> Here is the attachement, sorry for forgetting it the first time.
The 'unsuppported compression scheme lzip' looks like a duplicate of
https://issues.guix.gnu.org/58149, merging.
> Le sam. 15 oct. 2022 à 13:55, zimoun <zimon.toutoune@gmail.com
> <mailto:zimon.toutoune@gmail.com>> a écrit :
> [...]
I recommend against top-posting -- the e-mail clients I know of support
methods for easy navigation to the mail that was replied to, no need to
duplicate that.
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-10-16 16:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 18:08 bug#58526: bug report upgrading Guix from 1.0.1 to 1.3 Timothée Flutre
2022-10-14 20:01 ` Maxime Devos
2022-10-15 11:44 ` zimoun
2022-10-16 15:25 ` Timothée Flutre
2022-10-16 16:26 ` Maxime Devos [this message]
[not found] ` <handler.s.C.166593762226965.transcript@debbugs.gnu.org>
2022-10-16 16:58 ` bug#58149: " Maxime Devos
2022-10-17 18:25 ` Timothée Flutre
2022-10-17 18:56 ` Maxime Devos
2022-10-17 7:58 ` zimoun
2022-10-17 18:23 ` Timothée Flutre
2022-10-17 19:59 ` zimoun
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=f489e6e5-6e08-5d24-4823-c9e76f5cf5f1@telenet.be \
--to=maximedevos@telenet.be \
--cc=58526@debbugs.gnu.org \
--cc=control@debbugs.gnu.org \
--cc=timflutre@gmail.com \
--cc=zimon.toutoune@gmail.com \
/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.