unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Alexandre Oliva <lxoliva@fsfla.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 14851@debbugs.gnu.org
Subject: bug#14851: linux-libre-3.3.8-gnu disappeared
Date: Fri, 19 Jul 2013 08:08:43 -0300	[thread overview]
Message-ID: <orzjtin6x0.fsf@livre.home> (raw)
In-Reply-To: <87zjtrfm39.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sat, 13 Jul 2013 00:30:02 +0200")

On Jul 12, 2013, ludo@gnu.org (Ludovic Courtès) wrote:

> Since we’re about to release a new version of Guix, I’d rather keep
> using 3.3.8.

> Alexandre: could you reinstate the original
> http://linux-libre.fsfla.org/pub/linux-libre/releases/3.3.8-gnu/linux-libre-3.3.8-gnu.tar.xz?

I suppose you don't want to prevent users of guix from using ath9k wifi
cards, so I strongly suggest switching to 3.3.8-gnu1.  Indeed, I think
you'd be better off with some LTS version of GNU Linux-libre, rather
than the dead 3.3 branch.  But that's your call.

> It would be ideal if the tarballs were on ftp.gnu.org.  I could do it if
> you don’t want to bother, provided the FTP admins allow it.  WDYT?

I'd be glad with such an arrangement.  I keep on failing to figure out
how to fit the weekly publishing of multiple releases into a workflow
that includes collecting information and sending it to ftp.gnu.org
without keeping another local copy of stuff that was published before.
That's one of the hold-up factors for me.  As for the tarballs, they're
all signed, so figuring out a way to upload just the bits created since
the last push, and pushing them to live, is what's missing.

Now, another possibility that I think would make more sense for guix is
to have its sources consolidated in a single place, rather than
scattered all over and at risk of having them pulled from under you.  At
the very least, you ought to keep a copy of sources you use to build
binaries you publish, so that you can satisfy your obligation to offer
the corresponding source, be it a legal (copyleft) or moral (software in
gnu ought to be free) obligation.

When we get GNU Linux-libre at ftp.gnu.org, it could then be hard links,
so that if we remove some tarball it won't go away from your “copy”, but
until then, you might be better off holding your own copy rather than
assuming our primary repository has infinite space.  Unfortunately it
doesn't, and I have to clean things up quite often.  For sources, I at
least keep enough bits around that the tarballs can be reconstructed in
a bit-exact fashion, but for binaries, when they're gone, they're gone
forever.  However, considering we put out multiple GBs of builds per
week, I don't think it's realistic to keep them all forever.  Not in our
own server, not at ftp.gnu.org.

-- 
Alexandre Oliva, freedom fighter    http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/   FSF Latin America board member
Free Software Evangelist      Red Hat Brazil Compiler Engineer

  parent reply	other threads:[~2013-07-19 15:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-12 11:02 bug#14851: linux-libre-3.3.8-gnu disappeared Andreas Enge
2013-07-12 22:30 ` Ludovic Courtès
2013-07-14  4:28   ` Jason Self
2013-07-14 13:55     ` Ludovic Courtès
2013-07-17 13:31     ` Ludovic Courtès
2013-07-19 11:08   ` Alexandre Oliva [this message]
2013-07-19 12:09     ` Ludovic Courtès
2013-07-19 19:50       ` Alexandre Oliva
2013-07-19 20:30         ` Ludovic Courtès
2013-07-19 16:51     ` Andreas Enge
2013-07-19 19:40       ` Alexandre Oliva
2017-04-03 10:53 ` bug#14851: #14851 - " ng0
2017-05-05 18:56   ` 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=orzjtin6x0.fsf@livre.home \
    --to=lxoliva@fsfla.org \
    --cc=14851@debbugs.gnu.org \
    --cc=ludo@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).