From owner-svn-ports-head@freebsd.org Fri Feb 19 11:12:55 2016 Return-Path: Delivered-To: svn-ports-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 241E3AAD18A; Fri, 19 Feb 2016 11:12:55 +0000 (UTC) (envelope-from rakuco@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EC7771E36; Fri, 19 Feb 2016 11:12:54 +0000 (UTC) (envelope-from rakuco@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id u1JBCsmJ059175; Fri, 19 Feb 2016 11:12:54 GMT (envelope-from rakuco@FreeBSD.org) Received: (from rakuco@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id u1JBCsGj059174; Fri, 19 Feb 2016 11:12:54 GMT (envelope-from rakuco@FreeBSD.org) Message-Id: <201602191112.u1JBCsGj059174@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: rakuco set sender to rakuco@FreeBSD.org using -f From: Raphael Kubo da Costa Date: Fri, 19 Feb 2016 11:12:54 +0000 (UTC) To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r409166 - head/security/gnupg X-SVN-Group: ports-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Feb 2016 11:12:55 -0000 Author: rakuco Date: Fri Feb 19 11:12:53 2016 New Revision: 409166 URL: https://svnweb.freebsd.org/changeset/ports/409166 Log: Regenerate distinfo information for gnupg-2.1.11.tar.bz2.sig. This fixes `make fetch'. The actual hash and sizes are different, as mentioned in the associated PR. I have also checked it manually, and verified the tarball's signature with `gpg --verify gnupg-2.1.11.tar.bz2.sig gnupg-2.1.11.tar.bz2'. I don't understand how this happened, but it looks similar to bug 202312. PR: 207327 Submitted by: Trond.Endrestol@ximalas.info Modified: head/security/gnupg/distinfo Modified: head/security/gnupg/distinfo ============================================================================== --- head/security/gnupg/distinfo Fri Feb 19 09:15:55 2016 (r409165) +++ head/security/gnupg/distinfo Fri Feb 19 11:12:53 2016 (r409166) @@ -1,4 +1,4 @@ SHA256 (gnupg-2.1.11.tar.bz2) = b7b0fb2c8c5d47d7ec916d4a1097c0ddcb94a12bb1c0ac424ad86b1ee316b61a SIZE (gnupg-2.1.11.tar.bz2) = 5224007 -SHA256 (gnupg-2.1.11.tar.bz2.sig) = 058fddcf04cf538712938f4229d8fc7292901e5f235c18dc5b52e98e23b00b0b -SIZE (gnupg-2.1.11.tar.bz2.sig) = 287 +SHA256 (gnupg-2.1.11.tar.bz2.sig) = cf2ca28205a479ceac1fa5b6ac3d855c9461814c9cd231e4da2cf4f156f738f0 +SIZE (gnupg-2.1.11.tar.bz2.sig) = 574