From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20361 invoked by alias); 7 Aug 2012 12:01:44 -0000 Received: (qmail 20352 invoked by uid 22791); 7 Aug 2012 12:01:43 -0000 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 Received: from mail-pb0-f43.google.com (HELO mail-pb0-f43.google.com) (209.85.160.43) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 07 Aug 2012 12:01:31 +0000 Received: by pbcwz7 with SMTP id wz7so6986740pbc.2 for ; Tue, 07 Aug 2012 05:01:30 -0700 (PDT) Received: by 10.68.227.37 with SMTP id rx5mr27156591pbc.47.1344340889134; Tue, 07 Aug 2012 05:01:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.51.98 with HTTP; Tue, 7 Aug 2012 05:01:08 -0700 (PDT) In-Reply-To: <50207BAC.7030306@etr-usa.com> References: <50206AE0.90101@etr-usa.com> <50207BAC.7030306@etr-usa.com> From: Michael Gundlach Date: Tue, 07 Aug 2012 12:16:00 -0000 Message-ID: Subject: Re: cygwin 1.7.15: svn disk I/O error To: cygwin@cygwin.com Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2012-08/txt/msg00159.txt.bz2 On Mon, Aug 6, 2012 at 10:21 PM, Warren Young 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