From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13536 invoked by alias); 20 Apr 2008 18:47:00 -0000 Received: (qmail 13524 invoked by uid 22791); 20 Apr 2008 18:46:59 -0000 X-Spam-Check-By: sourceware.org Received: from out1.smtp.messagingengine.com (HELO out1.smtp.messagingengine.com) (66.111.4.25) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 20 Apr 2008 18:46:33 +0000 Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 8BAA5100B3D for ; Sun, 20 Apr 2008 14:46:31 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Sun, 20 Apr 2008 14:46:31 -0400 Received: from [192.168.1.3] (user-0c6suln.cable.mindspring.com [24.110.122.183]) by mail.messagingengine.com (Postfix) with ESMTPSA id 14B753299A; Sun, 20 Apr 2008 14:46:31 -0400 (EDT) Message-ID: <480B8F84.7080304@cwilson.fastmail.fm> Date: Sun, 20 Apr 2008 18:47:00 -0000 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.12) Gecko/20080213 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: Mailing List: CygWin-Apps Subject: Re: [HEADSUP] Let's start a Cygwin 1.7 release area References: <48041AC2.DA789E78@dessent.net> <20080415085515.GW23852@calimero.vinschen.de> <20080415090849.GZ23852@calimero.vinschen.de> <20080415141730.GA21313@ednor.casa.cgf.cx> <20080415154400.GL23852@calimero.vinschen.de> <20080415175923.GA21976@ednor.casa.cgf.cx> <20080415183856.GM23852@calimero.vinschen.de> <4804F929.60401@lapo.it> <20080416093916.GS23852@calimero.vinschen.de> <20080416162446.GB24767@ednor.casa.cgf.cx> <20080420154525.GA5199@ednor.casa.cgf.cx> In-Reply-To: <20080420154525.GA5199@ednor.casa.cgf.cx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com X-SW-Source: 2008-04/txt/msg00253.txt.bz2 Christopher Faylor wrote: > Since most of what I did was automated, I probably ended up deleting too > much. Please take a look at the package directories that you maintain > and verify that the release-2 directory contains something that makes > sense. If we find a problem, how should we fix it? For instance, release(1) inetutils has prev: 1.3.2-37, curr: 1.3.2-40, and test: 1.5-3. release-2 has only 1.5-3, but its setup still specified that 1.5-3 is test (it also specifies the non-existant 1.3.2-40 and 1.3.2-37 packages as curr: and prev:, respectively). I'm not ready to make inetutils-1.5-3 curr: on the release(1) side. However, since ALL of release-2 is test:, I could see doing any of the following: (1) copy over the 1.3.2-40 packages, and remove the prev: entry from setup.hint (2) change the release-2 setup.hint so that on "that side", inetutils-1.5-3 becomes curr: (and remove all references in setup.hint to the "missing" packages). (3) change the release-2 setup.hint by removing all references to the "missing" packages, but otherwise leave things along. That is, on the release-2 side, "inetutils" would ONLY be available as a test release, until I manually promote 1.5-3. But I'm not really sure how union fs works. Can I edit setup.hint in place? Can I "copy" back the "missing" files, or is there some special procedure that makes them "re-appear"? -- Chuck