From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Simon Tournier <zimon.toutoune@gmail.com>, ludo@gnu.org
Cc: gnu@gnu.org, 55933@debbugs.gnu.org,
Thomas C Kosvic <tckosvic@ix.netcom.com>
Subject: bug#55933: Fails download of quix 1.3 virtual machine
Date: Wed, 11 Sep 2024 21:13:14 +0000 [thread overview]
Message-ID: <6FAEF87B-0C5C-4071-BCE4-C076DD88E65E@tobias.gr> (raw)
In-Reply-To: <87y13za3zf.fsf@gmail.com>
Hi Simon,
Thanks for hunting.
On 10 September 2024 16:05:40 UTC, Simon Tournier <zimon.toutoune@gmail.com> wrote:
>I get:
>
>--8<---------------cut here---------------start------------->8---
>$ curl -LI https://ftp.gnu.org/gnu/guix/guix-system-install-1.3.0.x86_64-linux.qcow2 | grep Content-Type
>Content-Type: text/html; charset=iso-8859-1
>--8<---------------cut here---------------end--------------->8---
>
>Does it mean the issue is gone?
Nope.
I mean, if the server were now "actively* serving a gigabyte-plus VM image as HTML, the issue would be much worse...
However, it's serving HTML because that URL is now a 404 status page. The qcow2 image has been deleted.
I'm a bit surprised by that. I somewhat assumed that releases were kept forever.
Anyway, the original issue is unchanged:
$ curl -LI https://ftp.gnu.org/gnu/guix/guix-system-vm-image-1.3.0.x86_64-linux.qcow2 | grep Content-Type
X-Content-Type-Options: nosniff
Kind regards,
T G-R
Sent on the go. Excuse or enjoy my brevity.
prev parent reply other threads:[~2024-09-11 21:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 19:16 bug#55933: Fails download of quix 1.3 virtual machine Thomas C Kosvic
2022-06-12 21:14 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2024-09-10 16:05 ` Simon Tournier
2024-09-11 21:13 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
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=6FAEF87B-0C5C-4071-BCE4-C076DD88E65E@tobias.gr \
--to=bug-guix@gnu.org \
--cc=55933@debbugs.gnu.org \
--cc=gnu@gnu.org \
--cc=ludo@gnu.org \
--cc=me@tobias.gr \
--cc=tckosvic@ix.netcom.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.