From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sa-prd-fep-040.btinternet.com (mailomta19-sa.btinternet.com [213.120.69.25]) by sourceware.org (Postfix) with ESMTPS id 291643857C4E for ; Sun, 30 Aug 2020 15:00:04 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 291643857C4E Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=dronecode.org.uk Authentication-Results: sourceware.org; spf=none smtp.mailfrom=jon.turney@dronecode.org.uk Received: from sa-prd-rgout-005.btmx-prd.synchronoss.net ([10.2.38.8]) by sa-prd-fep-040.btinternet.com with ESMTP id <20200830150003.VBOH5290.sa-prd-fep-040.btinternet.com@sa-prd-rgout-005.btmx-prd.synchronoss.net>; Sun, 30 Aug 2020 16:00:03 +0100 Authentication-Results: btinternet.com; auth=pass (PLAIN) smtp.auth=jonturney@btinternet.com X-Originating-IP: [31.51.206.212] X-OWM-Source-IP: 31.51.206.212 (GB) X-OWM-Env-Sender: jonturney@btinternet.com X-VadeSecure-score: verdict=clean score=0/300, class=clean X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgeduiedrudeffedgkeefucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuueftkffvkffujffvgffngfevqffopdfqfgfvnecuuegrihhlohhuthemuceftddunecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefufhfhvffkffgfgggjtgfgsehtkeertddtfeejnecuhfhrohhmpeflohhnucfvuhhrnhgvhicuoehjohhnrdhtuhhrnhgvhiesughrohhnvggtohguvgdrohhrghdruhhkqeenucggtffrrghtthgvrhhnpeeljeejuefhtdekheefvdejffejteektddvvdevudffveekhfdvgeejtdelleejueenucfkphepfedurdehuddrvddtiedrvdduvdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhephhgvlhhopegludelvddrudeikedruddrudduudgnpdhinhgvthepfedurdehuddrvddtiedrvdduvddpmhgrihhlfhhrohhmpeeojhhonhdrthhurhhnvgihsegurhhonhgvtghouggvrdhorhhgrdhukhequceuqfffjgepkeeukffvoffkoffgpdhrtghpthhtohepoegthihgfihinhdqrghpphhssegthihgfihinhdrtghomheqpdhrtghpthhtohepoehksghrohifnhestghorhhnvghllhdrvgguuheq X-RazorGate-Vade-Verdict: clean 0 X-RazorGate-Vade-Classification: clean Received: from [192.168.1.111] (31.51.206.212) by sa-prd-rgout-005.btmx-prd.synchronoss.net (5.8.340) (authenticated as jonturney@btinternet.com) id 5ED9B8A70E74A360; Sun, 30 Aug 2020 16:00:03 +0100 Subject: Re: git repositories for cygwin packaging - please test References: <20e2f046-af24-14b8-b6c4-263f859042b8@dronecode.org.uk> <181ea3fa-1a50-7db4-0009-47ea9af77cdc@dronecode.org.uk> <5ff5073b-03a7-95e5-6d8b-fbd6436fe1c4@dronecode.org.uk> <63d64107-f2d5-e8b8-b724-20b21eaf9e16@cornell.edu> From: Jon Turney To: "cygwin-apps@cygwin.com" , Ken Brown Message-ID: Date: Sun, 30 Aug 2020 16:00:02 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: <63d64107-f2d5-e8b8-b724-20b21eaf9e16@cornell.edu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00, FORGED_SPF_HELO, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_PASS, SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin-apps@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin package maintainer discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Aug 2020 15:00:06 -0000 On 26/08/2020 23:00, Ken Brown via Cygwin-apps wrote: > On 8/23/2020 5:01 PM, Jon Turney wrote: >> >> I now have built an (opt-in) system which fetches the packages built >> by this into your upload area and triggers calm to process them, which >> I'm looking for a volunteer to test. > > I'd be willing to give it a try the next time I have something to > upload.  I'm actually almost ready for a test release of doxygen. > Unfortunately, the 32-bit scallywag build of doxygen consistently fails > with an ld crash, even though I can build it locally.  So I can't use it > for this test. > > How does the opt-in process work?  Is it per package?  Is it easy to > opt-out again temporarily? We can arrange the details however you like. A specific package might be a good idea for a first try. Only pushes to master are considered. You can opt-out by adding 'SCALLYWAG=nodeploy' to the cygport. >> Currently, these packages are built using 'cygport all-test', and so >> will always be marked test: >> >> One possible issue is that a git commit doesn't have to change VERSION >> or RELEASE, so this can build packages which are then immediately >> rejected by calm, as that PVR already exists. > > Does calm delete them after rejecting them or does the maintainer have > to do that? I've actually recently made a change to calm so that packages rejected as duplicates of existing PVR are discarded rather than retained, as this was just an inconvenience with no benefit. >> I'm not sure if that's a real problem, or what the workflow should >> look like in regards to that. > > I don't see it as a real problem, as long as all it means is that I get > an email from calm.  But if I also have to manually delete the packages > from my upload area, that could be annoying.