unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: GNU bug tracker automated control server
	<control@debbugs.gnu.org>,
	58526@debbugs.gnu.org, 58149@debbugs.gnu.org
Subject: bug#58149: bug#58526: bug report upgrading Guix from 1.0.1 to 1.3
Date: Sun, 16 Oct 2022 18:58:49 +0200	[thread overview]
Message-ID: <f6352323-be90-74c5-0324-f09268e6002a@telenet.be> (raw)
In-Reply-To: <handler.s.C.166593762226965.transcript@debbugs.gnu.org>


[-- Attachment #1.1.1: Type: text/plain, Size: 355 bytes --]

reopen 58149
merge 58149 58526
thanks

I tried merging 58149 with 58526 because they appear to be essentially 
the same issue (pre-lzip stuff).

As far as I can tell, no fix for that problem was provided, and it's 
still happening (see, e.g., 58526).  As such, I'm reopening.

Feel free to reclose if I missed something.

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 --]

  parent reply	other threads:[~2022-10-16 16:59 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
     [not found]       ` <handler.s.C.166593762226965.transcript@debbugs.gnu.org>
2022-10-16 16:58         ` Maxime Devos [this message]
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

  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=f6352323-be90-74c5-0324-f09268e6002a@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=58149@debbugs.gnu.org \
    --cc=58526@debbugs.gnu.org \
    --cc=control@debbugs.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 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).