all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Libreoffice source disappeared
Date: Sun, 20 May 2018 12:42:55 +0200	[thread overview]
Message-ID: <878t8ewqts.fsf@elephly.net> (raw)
In-Reply-To: <874lj6daa3.fsf@gmail.com>


Chris Marusich <cmmarusich@gmail.com> writes:

> * For a given version X.Y.Z, the release cycle behaves like this:
>
>   * Before the release is announced, any number of X.Y.Z.N release
>     candidates may be published.  Based on what we saw just recently, as
>     new releases are added, the old ones will be removed from the main
>     download location.
>
>   * Once the release is announced, no further X.Y.Z.N release candidates
>     will be published, and the last "N" is used as the X.Y.Z release.
>
> So, the reason 5.4.7.2 replaced 5.4.7.1 when it came out is because the
> 5.4.7 release hasn't been announced yet.  Until the 5.4.7 release has
> been announced, we might see more release candidates (e.g., 5.4.7.3).

Oh, that’s counter intuitive.  I would have thought that 5.4.7.3 would
be more recent than 5.4.7, and I think that the Guix version comparator
would agree.

Does this mean we should avoid release candidates?

>>> FYI, when I asked on the LibreOffice IRC channel, they told me that old
>>> releases can be found here:
>>> 
>>> http://downloadarchive.documentfoundation.org/libreoffice/old/5.4.7.1/src/libreoffice-5.4.7.1.tar.xz
>>> 
>>> Maybe we should add the "old" archives (and mirrors thereof, if any
>>> exist) to the list of mirrors, so that when they remove a published
>>> release, we have a chance of automatically fetching it from the "old"
>>> archives.  What do you think?
>>
>> Yes, we should add this alternate address.
>
> Actually, today they told me that the "old" location contains
> everything, even the new releases.  To simplify things, perhaps we
> should always just use the "old" location.  What do you think?

It’s fine to use both.

-- 
Ricardo

  reply	other threads:[~2018-05-21 10:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-17  5:22 Libreoffice source disappeared Chris Marusich
2018-05-17  5:31 ` Leo Famulari
2018-05-17  7:13   ` Chris Marusich
2018-05-20 10:42     ` Ricardo Wurmus [this message]
2018-05-21 17:18     ` Leo Famulari

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=878t8ewqts.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=cmmarusich@gmail.com \
    --cc=guix-devel@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 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.