[9303] in athena10
Re: [Debathena] #673: Rebuild for Squeeze
daemon@ATHENA.MIT.EDU (Debathena Trac)
Fri Jun 29 21:15:02 2012
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: "Debathena Trac" <debathena@MIT.EDU>
Cc: debathena@MIT.EDU
To: geofft@MIT.EDU, jdreed@MIT.EDU
Date: Sat, 30 Jun 2012 01:14:58 -0000
Reply-To:
Message-ID: <057.432ac75afc7ddc8b81c9e90f8c894d22@mit.edu>
In-Reply-To: <042.78eb80de9ba558fe586de5b2dcb90b04@mit.edu>
Content-Transfer-Encoding: 8bit
#673: Rebuild for Squeeze
--------------------+-----------------------------------
Reporter: geofft | Owner: jdreed
Type: task | Status: accepted
Priority: low | Milestone: The Distant Future
Component: -- | Resolution:
Keywords: | Upstream bug:
--------------------+-----------------------------------
Comment (by jdreed):
Done. The new do-build and gen-build-deps work fine.
Squeeze is currently in squeeze-staging. Someone who actually runs
squeeze should test it, particularly the "upgrade" path, or I can probably
do so in a VM at some point.
Now that we have -staging, we should think about a workflow? Should it
just get moved to -development upon a successful build? Or should it
require testing in -staging, then -dev, then -proposed. Or -staging to
production?
--
Ticket URL: <https://athena10.mit.edu/trac/ticket/673#comment:4>
Debathena <http://debathena.mit.edu>
MIT Debathena Project
