[9512] in athena10
Re: [Debathena] #1036: The apt_release clusterinfo tag is Wrong(tm)
daemon@ATHENA.MIT.EDU (Debathena Trac)
Thu Jul 19 09:06:46 2012
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: "Debathena Trac" <debathena@MIT.EDU>
Cc: debathena@MIT.EDU
To: jdreed@MIT.EDU
Date: Thu, 19 Jul 2012 13:06:43 -0000
Reply-To:
Message-ID: <057.ad8006d9d2f3d44dcae9a0d65dffd9ef@mit.edu>
In-Reply-To: <042.d5ee9c56f08b6858542505501effa987@mit.edu>
Content-Transfer-Encoding: 8bit
#1036: The apt_release clusterinfo tag is Wrong(tm)
--------------------+-------------------------------------
Reporter: jdreed | Owner:
Type: defect | Status: new
Priority: normal | Milestone: Quantum Quetzalcoatl
Component: -- | Resolution:
Keywords: | Upstream bug:
--------------------+-------------------------------------
Changes (by jdreed):
* milestone: Precise Release => Quantum Quetzalcoatl
Comment:
-development does in fact imply -proposed, and must continue to do so
unless we change our workflow, and we're not doing _that_.
Here's where we use APT_RELEASE and how we treat it:
- auto-update: development implies proposed
- the installer: queries Hesiod directly, development does not imply
proposed
Possible solutions:
- Punt apt_release in favor of a "sourceslist" tag pointing to a
sources.list file in AFS, though we'd either need one per distro/release
or we'd need to swap in the codename.
- Decide that development does imply proposed, and that bleeding implies
development + proposed
- Something else
--
Ticket URL: <https://athena10.mit.edu/trac/ticket/1036#comment:1>
Debathena <http://debathena.mit.edu>
MIT Debathena Project
