[980] in athena10

home help back first fref pref prev next nref lref last post

Beta repo layout

daemon@ATHENA.MIT.EDU (Evan Broder)
Sun Jan 25 12:41:22 2009

Message-ID: <497CA403.6000005@mit.edu>
Date: Sun, 25 Jan 2009 12:40:19 -0500
From: Evan Broder <broder@MIT.EDU>
MIME-Version: 1.0
To: debathena@mit.edu
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

I'd like to switch from having a completely separate apt-beta repo to
having a single apt repo with {etch,lenny,dapper,etc}-beta releases.

Since the terminology is a little unclear on this sort of thing, I'll
re-express my desires in terms of changes to sources.list :)
  Old:
    deb http://debathena.mit.edu/apt-beta hardy debathena debathena-config
    deb-src http://debathena.mit.edu/apt-beta hardy debathena
debathena-config

  New:
    deb http://debathena.mit.edu/apt hardy-beta debathena debathena-config
    deb-src http://debathena.mit.edu/apt hardy-beta debathena
debathena-config

This will make it substantially easier to move packages from beta to
production, which I think is important.

Once we do that, I think it wouldn't hurt to have a standing policy of
letting any non-emergency updates sit in beta for a day or so before
going live.

Anders, Tim - do you guys have any thoughts on this? Any reason it
wasn't done this way initially?

- Evan

home help back first fref pref prev next nref lref last post