X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <493ABDB2.6010506@cornell.edu> Date: Sat, 06 Dec 2008 13:00:18 -0500 From: Ken Brown User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: cygport and gpg References: <493AAA81 DOT 2070108 AT cornell DOT edu> <493AB42B DOT A6733CDB AT dessent DOT net> In-Reply-To: <493AB42B.A6733CDB@dessent.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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 12/6/2008 12:19 PM, Brian Dessent wrote: > It appears that in recent versions (0.9.1 and on) of cygport, failure to > verify has been made informational and not fatal. But trunk versions of > cygport are for cygwin 1.7 only so it looks like 1.5 will only ever see > 0.4.x. > > Anyway, it's just a script. You can edit the line in __gpg_verify where > it invokes gpg --verify to add "|| true" on the end if you can't import > the key. Thanks, Brian. gpg --search-keys didn't find the key, but editing the script is a simple solution. Ken -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/