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 16:50:23 -0300	[thread overview]
Message-ID: <orbo5ycosg.fsf@livre.home> (raw)
In-Reply-To: <8761w6hhtq.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 19 Jul 2013 14:09:37 +0200")

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

> What do you mean by “multiple GBs of builds per week”?  Linux{,-Libre}
> releases are not that frequent, are they?

They are.  ATM there are 4 active stable releases that each get one new
release per week.  There are 3 other LTS stable branches that get
releases less often.  And then, there are the weekly development -rcs
for the next release, that I seldom start tracking long before the
release is out.  This is just for sources, and it adds up to almost 1GB
per week.

Adding binaries to the picture grows the entire size by a little bit
when it comes to the freesh and planet .debs, and to a larger extent
when it comes to gnewsense/yeeloong (that gets one build per source
release we put out, with a total deb+tar size about the same size of the
source release subdir), and the freed-ora builds (that involve 1-4 rpm
builds per active Fedora release per week, each one weighting some 2GB
total; for most of the time there are 2 or 3 active releases; sometimes
there are 4, depending on whether or not I've already cleaned up the -rc
series for the upcoming release that gets built for the rawhide tree).

> If size turns out to be a problem, we could choose to keep only LTS
> releases on ftp.gnu.org, for instance.

Keeping only LTS wouldn't help guix, though, since you're not using an
LTS release.

-- 
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

  reply	other threads:[~2013-07-19 19:52 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
2013-07-19 12:09     ` Ludovic Courtès
2013-07-19 19:50       ` Alexandre Oliva [this message]
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=orbo5ycosg.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).