From: ludo@gnu.org (Ludovic Courtès)
To: Lasse Collin <lasse.collin@tukaani.org>
Cc: 21784@debbugs.gnu.org
Subject: bug#21784: Old XZ tarballs
Date: Sun, 01 Nov 2015 11:20:07 +0100 [thread overview]
Message-ID: <87y4ei58dk.fsf@gnu.org> (raw)
In-Reply-To: <20151031202908.5548817d@tukaani.org> (Lasse Collin's message of "Sat, 31 Oct 2015 20:29:08 +0200")
Lasse Collin <lasse.collin@tukaani.org> skribis:
> On 2015-10-30 Ludovic Courtès wrote:
[...]
>> Guix does automatically mirror tarballs via its “substitute”
>> mechanism. However, users can turn it off, in which case they end up
>> downloading the tarball from the upstream URL specified in the
>> package recipe.
>
> OK. :-) Why would users turn it off though?
The substitute mechanism is very generic; it’s not just about mirroring
tarballs:
http://www.gnu.org/software/guix/manual/html_node/Substitutes.html
Some people might prefer to build things locally rather than download
pre-built items.
> I would guess that one good mirror would be more reliable than dozens
> of upstream sites of which just one needs to be down to be a problem
> for a user. A package manager should know the hash or signature of the
> file, so from security point of view it doesn't matter where the file
> comes.
Yes exactly, all we need is to mirror it somewhere.
>> > By the way, is there a reason why you use 5.0.4 instead of 5.0.8 (or
>> > even 5.2.2)?
>>
>> No good reason! We’ll upgrade it as soon as this can be done without
>> triggering too much rebuild/redownloads for users.
>
> API/ABI is backward compatible so one shouldn't need to rebuild other
> packages. There's a mailing list "xz-announce" in case you want a
> notification when a new version is released:
> <http://tukaani.org/xz/lists.html>
Noted, thanks!
Ludo’.
next prev parent reply other threads:[~2015-11-01 10:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 7:30 bug#21784: cannot install icecat! -=}\*/{=-
2015-10-29 19:20 ` Efraim Flashner
2015-10-29 19:23 ` Efraim Flashner
2015-10-29 19:30 ` -=}\*/{=-
2015-10-29 19:39 ` -=}\*/{=-
2015-10-29 19:51 ` Efraim Flashner
2015-10-30 17:06 ` bug#21784: Alternate xz-5.0.4.tar.gz URL Ludovic Courtès
2015-10-30 17:12 ` Andreas Enge
2015-10-31 10:41 ` Ludovic Courtès
2015-10-31 21:20 ` Andreas Enge
2015-11-01 10:20 ` Ludovic Courtès
2015-11-01 12:06 ` Andreas Enge
2015-11-01 20:05 ` Ludovic Courtès
2015-10-29 20:27 ` bug#21784: cannot install icecat! Ludovic Courtès
2015-10-29 23:07 ` -=}\*/{=-
2015-10-29 23:20 ` -=}\*/{=-
2015-10-30 7:53 ` -=}\*/{=-
2015-10-30 8:02 ` Efraim Flashner
2015-10-30 8:14 ` -=}\*/{=-
2015-10-30 15:45 ` -=}\*/{=-
2015-10-30 17:47 ` Lasse Collin
2015-10-30 19:58 ` bug#21784: Old XZ tarballs Ludovic Courtès
2015-10-31 18:29 ` Lasse Collin
2015-11-01 10:20 ` Ludovic Courtès [this message]
2015-11-02 12:07 ` Lasse Collin
2015-11-02 13:37 ` Ludovic Courtès
2015-11-02 14:24 ` Lasse Collin
2015-11-02 15:07 ` Ludovic Courtès
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=87y4ei58dk.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=21784@debbugs.gnu.org \
--cc=lasse.collin@tukaani.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).