X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.7 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,TW_SV
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <50207BAC.7030306@etr-usa.com>
References: <CABVhxxKw8i96668GgHmMyPXCn+nBS8S874Q7wSSHgoer8iiSsw AT mail DOT gmail DOT com> <CABVhxxLOce9dV0EgtYeqPPwrEfMj=993rOgtVqfQ5L4sY-Qq=g AT mail DOT gmail DOT com> <50206AE0 DOT 90101 AT etr-usa DOT com> <CABVhxxJV6FgPZOgf3+ydSbkrb8rg_byk4PPaUV+HAVBwwf8cjQ AT mail DOT gmail DOT com> <50207BAC DOT 7030306 AT etr-usa DOT com>
From: Michael Gundlach <adblockforchrome AT gmail DOT com>
Date: Tue, 7 Aug 2012 08:01:08 -0400
Message-ID: <CABVhxxKA9oDn8KEwgVjpxL2Qke+TzpjteoJRFuiXHk13URV64A@mail.gmail.com>
Subject: Re: cygwin 1.7.15: svn disk I/O error
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Mon, Aug 6, 2012 at 10:21 PM, Warren Young <warren AT etr-usa DOT com> wrote:
>>> What reason could there be for a new Cygwin DLL to be accompanied by a
>>> new
>>> version of SQLite?  Their maintainerships are entirely decoupled.
>>
>> Pardon my ignorance; I'm not familiar with the release process.
>
> Well, to a first approximation, it's entirely asynchronous.  Every package
> maintainer releases versions on whatever schedule they wish. There are
> probably dozens of active Cygwin package maintainers.

Got it; I had somehow gotten the impression that there was one big
synchronized release-to-production of the Cygwin binary and all
packages.

> You have to enter the Cygwin Time Machine to do that:
>         http://www.fruitbat.org/Cygwin/index.html#cygwincirca

Thanks!

> Bottom line: it's going to take at least a few days if you want to wait,
> maybe a week, maybe more.  If you have to have a fix today, use the Time
> Machine.

Thanks for the insight into the package release process.  Given that
branch reintegration is so dicey that I've ended up doing
  while [ 1 ]; do
    cleanup && revert && reintegrate && break;
  done
, I think I'll use the Time Machine :)

Michael

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple