all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Brice Waegeneire <brice@waegenei.re>
Cc: h.goebel@crazy-compilers.com, 28159-done@debbugs.gnu.org
Subject: bug#28159: Closing bug #28159? Updater needs to support HTTP(S) servers
Date: Thu, 30 Apr 2020 23:14:59 +0200	[thread overview]
Message-ID: <87lfmcoeuk.fsf@gnu.org> (raw)
In-Reply-To: <07e7317fe16fc58790cd99c0a712fcf5@waegenei.re> (Brice Waegeneire's message of "Wed, 29 Apr 2020 08:21:56 +0000")

Hi Brice,

Brice Waegeneire <brice@waegenei.re> skribis:

> It looks like now most of the major updaters that relied on FTP (GNU,
> kernel.org, KDE and Gnbome) now support HTTP(S). I think we can close
> this
> bug.

Yup.  There’s still the ‘gnu-ftp’ and the ‘xorg’ updaters which,
according to ‘guix refresh --list-updaters’, account for 2.2% of the
packages.  We can change them later when it becomes necessary.

Closing, thank you!

Ludo’.




      reply	other threads:[~2020-04-30 21:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <RT-Ticket-1238656@rt.gnu.org>
2017-08-20 12:06 ` bug#28159: Updater needs to support HTTP(S) servers Hartmut Goebel
2017-08-22  8:57   ` Ludovic Courtès
2017-08-23 10:20     ` Hartmut Goebel
2017-08-23 21:30       ` Ludovic Courtès
2017-08-26  9:54       ` Ludovic Courtès
2017-08-26 10:33         ` Hartmut Goebel
2017-09-03 21:40           ` Ludovic Courtès
2017-09-08  8:30             ` Ludovic Courtès
2017-09-14 16:50               ` bug#28159: [gnu.org #1238656] " Rubén Rodríguez Pérez via RT
2017-09-14 16:50               ` =?UTF-8?B?UnViw6luIFJvZHLDrWd1ZXogUMOpcmV6?= via RT
2017-09-15  7:50                 ` Ludovic Courtès
2017-09-25 22:39             ` Ludovic Courtès
2018-11-10 22:38               ` Ludovic Courtès
2019-09-10 17:25     ` Hartmut Goebel
2020-04-29  8:21   ` bug#28159: Closing bug #28159? " Brice Waegeneire
2020-04-30 21:14     ` Ludovic Courtès [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=87lfmcoeuk.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=28159-done@debbugs.gnu.org \
    --cc=brice@waegenei.re \
    --cc=h.goebel@crazy-compilers.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.