unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: bokr@bokr.com
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 56847@debbugs.gnu.org
Subject: bug#56847: [CI] ‘Build output’ artefact download links are broken
Date: Sun, 31 Jul 2022 12:03:31 +0200	[thread overview]
Message-ID: <20220731095951.GA3731@LionPure> (raw)
In-Reply-To: <87mtcqxive@nckx>

Hi Tobias,

On +2022-07-31 01:46:07 +0200, Tobias Geerinckx-Rice via Bug reports for GNU Guix wrote:
> 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

Works for me now, (2022-07-31T11:56:53+02:00)  BUT:

If you take a screen shot of [0] and look at it a year from now,
you will not have a clue as to what year the dates refer to, and
even looking with stat at the screen shot file is not going to
be 100% unless you were careful not to copy it somewhere without cp -a.

So, I would really like to see that date style deprecated,
in favor of date '+%F %T' or date -Is or date -Ins depending
on need to avoid spaces.

At a minimum, put the base year someplace on the page, so
the other dates can be interpreted unambigously.

2¢ ;-)
--
Regards,
Bengt Richter




  reply	other threads:[~2022-07-31 10:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-30 23:46 bug#56847: [CI] ‘Build output’ artefact download links are broken Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-07-31 10:03 ` bokr [this message]
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

  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=20220731095951.GA3731@LionPure \
    --to=bokr@bokr.com \
    --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 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).