unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 28240@debbugs.gnu.org
Subject: bug#28240: bad backtrace on “guix archive -x”
Date: Wed, 26 Oct 2022 22:29:27 +0200	[thread overview]
Message-ID: <86k04mba6w.fsf@gmail.com> (raw)
In-Reply-To: <86czwpknzk.fsf@gmail.com> (zimoun's message of "Thu, 25 Feb 2021 01:08:47 +0100")

Hi,

On Thu, 25 Feb 2021 at 01:08, zimoun <zimon.toutoune@gmail.com> wrote:

> On Sat, 26 Aug 2017 at 14:23, Ricardo Wurmus <rekado@elephly.net> wrote:
>
>> wget -q -O - https://mirror.hydra.gnu.org/guix/nar/gzip/ykpfif2wzabhnn0a88sw3f96paa33k2z-r-minimal-3.4.0 | guix archive -x /tmp/hydra
>> Backtrace:
>
> This example is not relevant anymore.  Instead,
>
> wget -O - https://ci.guix.gnu.org/nar/gzip/bhdixzi1c7x4jyh93zx5aqgwzzw3i182-r-minimal-4.0.4 | guix archive -x /tmp/ci
>
>
> still returns the ugly backtrace with…
>
> [...]
>
>> ERROR: Throw to key `decoding-error' with args `("scm_from_utf8_stringn"
>> "input locale conversion error" 0 #vu8(2 3 236 189 11 116 92 213 149 32 122
>> 37 99 35 93 140 100 136 1 135 132 230 32 4 37 9 85 233 227 15 178 141 140 74
>> 82 217 85 65 150 148 146 100 96 97 35 223 170 186 85 186 168 126 169 91 165
>> 143 177 19 51 134 4 45 183 50 76 122 186 87 207 116 214 123 204 91 157 76
>> 122 77 86 154 158 204 155 16 186 131 237 5 193 73 175 204 132 204 234 78 210
>> 157 188 78 79 186 211 145 67 62 116 39 33 36 233 224 183 247 62 159 251 169
>> 42 27 99 32 153 181 82 96 221 123 207 103 159 115 246 217 103 239 125 246
>> 217 231 156 171 53 254 203 91 75 65 163 148 156 179 22 204 96 31 124 55 136
>> 240 14 241 188 66 60 203 203 69 19 159 205 226 59 101 149 204 100 185 80 90
>> 22 223 235 197 211 204 151 41 172 30 156 188 145 35 56 235 196 119 194 202
>> 123 227 11 41 138 127 187 234 33 227 227 254 248 215 89 143 43 197 119 201
>> 204 84 178 70 73 211 101 249 75 102 178 82 54 18 89 83 243 252 154 196 51 89
>> 200 151 161 142 246 31 183 243 239 91 111 233 201 228 43 61 54 52 197 236
>> 153 191 179 183 127 231 252 246 5 99 199 64 118 222 40 38 142 36 151 147 169
>> 35 15 221 153 219 158 120 40 177 45 49 16 76 24 246 92 112 91 104 91 168 175
>> 191 7 48 216 131 223 250 173 108 106 206 204 102 2
>> …
>> [pages upon pages of numbers]
>> …
>
> …pages of numbers.

This is still relevant.  However, is it still worth to keep it open
because of:

<https://guix.gnu.org/en/blog/2022/sunsetting-gzip-substitutes-availability/>

?


>
> Moreover, the lzip returns something more comprehensive.
>
> $ wget -O - https://ci.guix.gnu.org/nar/lzip/…-r-minimal-4.0.4 | guix archive -x /tmp/ci
> --2021-02-25 01:02:04--  https://ci.guix.gnu.org/nar/lzip/…-r-minimal-4.0.4
> Resolving ci.guix.gnu.org (ci.guix.gnu.org)... 141.80.181.40
> Connecting to ci.guix.gnu.org (ci.guix.gnu.org)|141.80.181.40|:443... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 24343298 (23M) [application/octet-stream]
> Saving to: ‘STDOUT’
>
> -                         100%[=====================================>]  23.21M   486KB/s    in 56s
>
> 2021-02-25 01:03:01 (424 KB/s) - written to stdout [24343298/24343298]
>
> guix archive: error: corrupt input while restoring '/tmp/ci' from #<input: file 0>

The situation is still the same.  Well, is the “guix archive” error the
point of this bug report?


Cheers,
simon




  reply	other threads:[~2022-10-26 22:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-26 12:23 bug#28240: bad backtrace on “guix archive -x” Ricardo Wurmus
2021-02-25  0:08 ` zimoun
2022-10-26 20:29   ` zimoun [this message]
2022-10-27 11:30     ` Ricardo Wurmus
2022-10-28  8:08       ` 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=86k04mba6w.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=28240@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    /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).