From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4331 invoked by alias); 29 Nov 2013 18:13:41 -0000 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 Received: (qmail 4310 invoked by uid 89); 29 Nov 2013 18:13:40 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.8 required=5.0 tests=AWL,BAYES_50,RDNS_NONE,URIBL_BLOCKED autolearn=no version=3.3.2 X-HELO: mho-02-ewr.mailhop.org Received: from Unknown (HELO mho-02-ewr.mailhop.org) (204.13.248.72) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Fri, 29 Nov 2013 18:13:39 +0000 Received: from pool-71-126-240-25.bstnma.fios.verizon.net ([71.126.240.25] helo=cgf.cx) by mho-02-ewr.mailhop.org with esmtpa (Exim 4.72) (envelope-from ) id 1VmSZH-00033K-3S for cygwin-apps@cygwin.com; Fri, 29 Nov 2013 18:13:31 +0000 Received: from cgf.cx (ednor.casa.cgf.cx [192.168.187.5]) by cgf.cx (Postfix) with ESMTP id 5206060129 for ; Fri, 29 Nov 2013 13:13:30 -0500 (EST) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+uAthf/LX35ldKZLyCGcMB Date: Fri, 29 Nov 2013 18:13:00 -0000 From: Christopher Faylor To: cygwin-apps@cygwin.com Subject: Re: two questions about new upload method Message-ID: <20131129181330.GA4823@ednor.casa.cgf.cx> Reply-To: cygwin-apps@cygwin.com Mail-Followup-To: cygwin-apps@cygwin.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-SW-Source: 2013-11/txt/msg00107.txt.bz2 On Fri, Nov 29, 2013 at 12:27:17PM -0500, Andrew Schulman wrote: >(1) Is there something I should sould be doing to tell upset which package >versions are old and should be purged? There was a long thread about how to delete packages in cygwin-apps. http://cygwin.com/ml/cygwin-apps/2013-10/threads.html#00184 It also went into November. >I uploaded lftp, and the new >version was added to the archive, but the old one (4.4.7-1) is still there. >Do I need to add curr: and prev: lines to setup.hint? Or will upset figure >that out and remove the old versions at some point? > >(2) I uploaded the unison packages for x86_64 in subdirectories of >x86_64/release/unison: > >x86_64/release/unison/unison2.27 >x86_64/release/unison/unison2.32 >x86_64/release/unison/unison2.40 >x86_64/release/unison/unison2.45 > >because that's how they're organized in x86/release. Will upset pick them >up when they're organized that way? I only ask because it's been about 18 >hours and they haven't appeared in any of the mirrors yet, although upset >seems to be running every hour. Guess I need to add a FAQ. Q) Why aren't my files being transferred to the release area? I've waited several days and don't see any movement. A) The package updater runs every 10 minutes so, if you don't see any movement in, e.g., 20 minutes, then your package is not going to be updated. The main reason that this could happen is if you uploaded a package that you are not actually responsible for. The updater only knows what you are responsible for based on http://cygwin.com/cygwin-pkg-maint so if you aren't listed as an owner there your packages won't be updated. I added you as the owner for "unison" and "unison2.45". cgf