From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 56847@debbugs.gnu.org
Subject: bug#56847: [CI] ‘Build output’ artefact download links are broken
Date: Sun, 31 Jul 2022 01:46:07 +0200 [thread overview]
Message-ID: <87mtcqxive@nckx> (raw)
[-- Attachment #1: Type: text/plain, Size: 171 bytes --]
After the server migration, the ‘Build outputs’ links on pages
like [0] return 502.
Kind regards,
T G-R
[0]: https://ci.guix.gnu.org/build/1123838/details
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next reply other threads:[~2022-07-30 23:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-30 23:46 Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2022-07-31 10:03 ` bug#56847: [CI] ‘Build output’ artefact download links are broken bokr
2022-08-01 1:20 ` Maxim Cournoyer
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=87mtcqxive@nckx \
--to=bug-guix@gnu.org \
--cc=56847@debbugs.gnu.org \
--cc=me@tobias.gr \
/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.