unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maxime.devos@student.kuleuven.be>
To: 44696@debbugs.gnu.org
Subject: bug#44696: https://issues.guix.gnu.org doesn't point to IRC logs
Date: Mon, 16 Nov 2020 20:41:33 +0100	[thread overview]
Message-ID: <b808b3454942a9bf34e8559d9055d0550913627a.camel@student.kuleuven.be> (raw)

[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]

Dear Guix,

The contents of logs.guix.gnu.org differs with the access method used
(HTTP / HTTPS). In case of HTTPS, Cuirass is displayed, and in case of
HTTP, the IRC logs are displayed. This is rather counter-intuitive.

Snippet of relevant #guix IRC logs:

(16:13:36) mdevos: https://logs.guix.gnu.org/ and 
https://logs.guix.info/ point to Cuirass. Is this a known issue?
(16:14:30) civodul: mdevos: not that i know of; could you email that to
bug-guix@gnu.org?
(16:14:55) mdevos: civodul: will do
(16:15:33) civodul: thanks
(16:18:05) nckx: mdevos: Yes, there's no HTTPS support for
logs.guix.gnu.org so it hasn't really ‘mattered’ that there's a missing
server block.  It should of course be fixed, thanks for reporting it ☺
(16:18:21) nckx: I had to resort to curl -k to see what you mean.
(16:20:25) mdevos: I disabled ‘Encrypt All Sites Eligible’ in HTTPS
Everywhere, and now I can see the logs again
(16:20:45) mdevos: (when using http: URL)

Greetings,
Maxime

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 273 bytes --]

             reply	other threads:[~2020-11-16 20:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-16 19:41 Maxime Devos [this message]
2020-11-16 20:50 ` bug#44696: https://issues.guix.gnu.org doesn't point to IRC logs Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-11-16 21:31 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-11-17  7:25   ` Maxime Devos

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=b808b3454942a9bf34e8559d9055d0550913627a.camel@student.kuleuven.be \
    --to=maxime.devos@student.kuleuven.be \
    --cc=44696@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).