[1817] in athena10
[Debathena] #164: installer should know about apt-release
daemon@ATHENA.MIT.EDU (Debathena Trac)
Mon Mar 23 04:25:36 2009
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: "Debathena Trac" <debathena@MIT.EDU>
Cc: debathena@mit.edu
To: broder@mit.edu
Date: Mon, 23 Mar 2009 08:25:22 -0000
Reply-To:
Message-ID: <043.a1625a3ddd7e90b18bb3f28a4ab01855@mit.edu>
Content-Transfer-Encoding: 8bit
#164: installer should know about apt-release clusterinfo-------------------+--------------------------------------------------------
Reporter: broder | Owner:
Type: defect | Status: new
Priority: major | Keywords:
-------------------+-------------------------------------------------------- Soon, hopefully, machines in various Moira clusters around campus will
have "production", "proposed", and/or "development" values for the "apt-
release" key in clusterinfo.
The Debathena installer script should somehow know about this field, and
should use it to frob /etc/apt/sources.list.d/debathena.list appropriately
at install time.
This allows us to test how a system handles being installed with the
packages in -proposed (or -development).
This one is a little trickier than #163 because we don't have debathena-
clusterinfo or debathena-getcluster installed when
/etc/apt/sources.list.d/debathena.list is written.
It may be that we want to install debathena-getcluster, find out the
clusterinfo, and then re-generate /etc/apt/sources.list.d/debathena.list,
but even this seems slightly non-ideal, as for a small period packages
will only be pulled from production.
-- Ticket URL: <http://debathena.mit.edu/trac/ticket/164>Debathena <http://debathena.mit.edu/>MIT Debian-Athena Project
