From nobody@FreeBSD.org  Sun Jul  3 14:50:22 2011
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 23872106567D
	for <freebsd-gnats-submit@FreeBSD.org>; Sun,  3 Jul 2011 14:50:22 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22])
	by mx1.freebsd.org (Postfix) with ESMTP id 12E248FC08
	for <freebsd-gnats-submit@FreeBSD.org>; Sun,  3 Jul 2011 14:50:22 +0000 (UTC)
Received: from red.freebsd.org (localhost [127.0.0.1])
	by red.freebsd.org (8.14.4/8.14.4) with ESMTP id p63EoLjA045982
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 3 Jul 2011 14:50:21 GMT
	(envelope-from nobody@red.freebsd.org)
Received: (from nobody@localhost)
	by red.freebsd.org (8.14.4/8.14.4/Submit) id p63EoLow045973;
	Sun, 3 Jul 2011 14:50:21 GMT
	(envelope-from nobody)
Message-Id: <201107031450.p63EoLow045973@red.freebsd.org>
Date: Sun, 3 Jul 2011 14:50:21 GMT
From: "Hartmann, O." <ohartman@zedat.fu-berlin.de>
To: freebsd-gnats-submit@FreeBSD.org
Subject: security/libcrypt: Update from libgcrypt-1.4.6 to libgcrypt-1.5.0 implies dependend ports to be rebuild
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         158611
>Category:       ports
>Synopsis:       security/libcrypt: Update from libgcrypt-1.4.6 to libgcrypt-1.5.0 implies dependend ports to be rebuild
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    swills
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Jul 03 15:00:21 UTC 2011
>Closed-Date:    Sun Aug 14 00:37:44 UTC 2011
>Last-Modified:  Sun Aug 14 00:37:44 UTC 2011
>Originator:     Hartmann, O.
>Release:        FreeBSD 9.0-CURRENT/amd64 FreeBSD 8.2-STABLE/amd64
>Organization:
FU Berlin
>Environment:
>Description:
Update from libgcrypt-1.4.6 to libgcrypt-1.5.0 implies dependend ports to be rebuild, but this is not reflected in /usr/ports/UPDATE. Some ports fail to start after the update has been performed, like Anjuta (devel/anjuta).
>How-To-Repeat:

>Fix:
Rebuild everything that is dependend on devel/libcrypt.

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-ports-bugs->swills 
Responsible-Changed-By: swills 
Responsible-Changed-When: Sun Jul 3 16:26:01 UTC 2011 
Responsible-Changed-Why:  
I'll take it. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=158611 

From: Steve Wills <swills@FreeBSD.org>
To: bug-followup@FreeBSD.org, "Hartmann, O." <ohartman@zedat.fu-berlin.de>
Cc:  
Subject: Re: ports/158611: security/libcrypt: Update from libgcrypt-1.4.6
 to libgcrypt-1.5.0 implies dependend ports to be rebuild
Date: Sun, 03 Jul 2011 12:47:02 -0400

 This is a multi-part message in MIME format.
 --------------030306060607040600080402
 Content-Type: text/plain; charset=ISO-8859-1
 Content-Transfer-Encoding: 7bit
 
 -----BEGIN PGP SIGNED MESSAGE-----
 Hash: SHA1
 
 I'm not sure this is necessary. The PORTREVISION bumps of the dependent
 ports should take care of this. If you run portmaster -a or portupgrade
 - -a, everything should be upgraded as necessary. This also doesn't seem
 to meet the criteria set in the Porters Handbook for an UPDATING entry:
 
 http://www.freebsd.org/doc/en/books/porters-handbook/moved-and-updating-files.html
 
 However, if it becomes enough of a problem for users, I will add an
 entry to UPDATING. A proposed entry is attached.
 
 Steve
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2.0.17 (FreeBSD)
 
 iQEcBAEBAgAGBQJOEJ0GAAoJEPXPYrMgexuh2ugH/20j98wgtwbvvabKCCt4egew
 MRUJEMGPEEiu3BanlJTnqQk/QOsAOab7t3YQNE4mxTPg8NoHQ4PylKnjAlRhmyrY
 gK4uqM4btuvySIPwB+dbEsANGaRqhLG8iU0AGPmuB1r/7twbrNtvFdeYhRoE6+cY
 +mEHcKdFVgGQSt739VN2T6K8A/TeqwXi3crED+54wx9FoH0p99hqfOQCz7YtxYOy
 7IQr979lxQvkMMt6yDru/g2MqdOtNB9GemQ/nFijujs1k4o1T66I0NfLhabRVpPA
 m72t9bLiMeamfkWytho80lXrlmX/ayHZhmsQyyPDNbi0OhEUHhOF7m6FeXbLlIs=
 =bUNC
 -----END PGP SIGNATURE-----
 
 --------------030306060607040600080402
 Content-Type: text/plain;
  name="UPDATING_libgcrypt_diff.txt"
 Content-Transfer-Encoding: 7bit
 Content-Disposition: attachment;
  filename="UPDATING_libgcrypt_diff.txt"
 
 Index: UPDATING
 ===================================================================
 RCS file: /home/ncvs/ports/UPDATING,v
 retrieving revision 1.1093
 diff -u -r1.1093 UPDATING
 --- UPDATING	30 Jun 2011 21:53:46 -0000	1.1093
 +++ UPDATING	3 Jul 2011 16:35:04 -0000
 @@ -5,6 +5,15 @@
  You should get into the habit of checking this file for changes each time
  you update your ports collection, before attempting any port upgrades.
  
 +20110703:
 +  AFFECTS: users of security/libgcrypt
 +  AUTHOR: swills@FreeBSD.org
 +  
 +  The libgcrypt port has been updated. Ports depending on libgcrypt will
 +  need to be rebuilt. Please run:
 +
 +  portmaster -r security/libgcrypt
 +
  20110630:
    AFFECTS: users of math/octave-forge* and benchmarks/octave-forge-benchmark
    AUTHOR: stephen@FreeBSD.org
 
 --------------030306060607040600080402
 Content-Type: application/octet-stream;
  name="UPDATING_libgcrypt_diff.txt.sig"
 Content-Transfer-Encoding: base64
 Content-Disposition: attachment;
  filename="UPDATING_libgcrypt_diff.txt.sig"
 
 iQEcBAABAgAGBQJOEJ0GAAoJEPXPYrMgexuhWoYH/1Cpux/mrzaHyXRNILa4kRLp/ucXF1vm
 zG6g/Rz4k1xiTTfymGbSkUBRVJkAXiBAtWZHNOyQNVcRZQyfRypfuuIRbiU6a5ACWMGXSdic
 bG271i+Z3/vmQMu8QS6bTVv7I09sWOvcpXY1/WxqR30h2pbejEXdAcPbSJgGKuVjVQvYeB9M
 c1xNZcYSN7jVZMcamoELluZs2vpybVae+QvvxySqCJNZUCh2y8SLGiHICej08SbkO/jYSp7/
 5cio9niF6QCnOli9OMgXcZCHT90ONCh62F5tE98W/zlDVzKPyqXQdg52yON0OU+rAoOH63pF
 menSdLMOKDWCL5MR3BrTkU8=
 --------------030306060607040600080402--

From: "O. Hartmann" <ohartman@zedat.fu-berlin.de>
To: Steve Wills <swills@FreeBSD.org>
Cc: bug-followup@FreeBSD.org
Subject: Re: ports/158611: security/libcrypt: Update from libgcrypt-1.4.6
 to libgcrypt-1.5.0 implies dependend ports to be rebuild
Date: Mon, 04 Jul 2011 16:16:58 +0200

 On 07/03/11 18:47, Steve Wills wrote:
 > -----BEGIN PGP SIGNED MESSAGE-----
 > Hash: SHA1
 >
 > I'm not sure this is necessary. The PORTREVISION bumps of the dependent
 > ports should take care of this. If you run portmaster -a or portupgrade
 > - -a, everything should be upgraded as necessary. This also doesn't seem
 > to meet the criteria set in the Porters Handbook for an UPDATING entry:
 >
 > http://www.freebsd.org/doc/en/books/porters-handbook/moved-and-updating-files.html
 >
 > However, if it becomes enough of a problem for users, I will add an
 > entry to UPDATING. A proposed entry is attached.
 >
 > Steve
 > -----BEGIN PGP SIGNATURE-----
 > Version: GnuPG v2.0.17 (FreeBSD)
 >
 > iQEcBAEBAgAGBQJOEJ0GAAoJEPXPYrMgexuh2ugH/20j98wgtwbvvabKCCt4egew
 > MRUJEMGPEEiu3BanlJTnqQk/QOsAOab7t3YQNE4mxTPg8NoHQ4PylKnjAlRhmyrY
 > gK4uqM4btuvySIPwB+dbEsANGaRqhLG8iU0AGPmuB1r/7twbrNtvFdeYhRoE6+cY
 > +mEHcKdFVgGQSt739VN2T6K8A/TeqwXi3crED+54wx9FoH0p99hqfOQCz7YtxYOy
 > 7IQr979lxQvkMMt6yDru/g2MqdOtNB9GemQ/nFijujs1k4o1T66I0NfLhabRVpPA
 > m72t9bLiMeamfkWytho80lXrlmX/ayHZhmsQyyPDNbi0OhEUHhOF7m6FeXbLlIs=
 > =bUNC
 > -----END PGP SIGNATURE-----
 
 For devel/anjuta, the ports in question to be rebuild are
 
 devel/devhelp
 www/webkit-gtk2
 
 This is for devel/devhelp dependend on what plugin one selects.

From: "O. Hartmann" <ohartman@zedat.fu-berlin.de>
To: Cc: bug-followup@FreeBSD.org
Subject: Re: ports/158611: security/libcrypt: Update from libgcrypt-1.4.6
 to libgcrypt-1.5.0 implies dependend ports to be rebuild
Date: Mon, 04 Jul 2011 16:52:40 +0200

 Also
 
 devel/libsoup
 devel/libsoup-gnome
 

From: Steve Wills <swills@FreeBSD.org>
To: bug-followup@FreeBSD.org, "Hartmann, O." <ohartman@zedat.fu-berlin.de>
Cc:  
Subject: Re: ports/158611: security/libcrypt: Update from libgcrypt-1.4.6
 to libgcrypt-1.5.0 implies dependend ports to be rebuild
Date: Mon, 04 Jul 2011 15:23:35 -0400

 -----BEGIN PGP SIGNED MESSAGE-----
 Hash: SHA1
 
 Hi,
 
 Please update your ports tree and try again. I've added an explicit
 dependnecy on libgcrypt to libsoup and libsoup-gnome and bumped the
 PORTREVISION, so portupgrade/portmaster should catch the need to rebuild
 now.
 
 Steve
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2.0.17 (FreeBSD)
 
 iQEcBAEBAgAGBQJOEhM3AAoJEPXPYrMgexuhfCYH/R1PqL6RuezL7Oq3ewXK8fZy
 Z+wzszGaKQxYp6tFodqDgb3JQpz8vZipd5bJWFsdnd97hxlYQ1e5JKK7Px/j4C2g
 oBoCt6HjHMtw83TKuOX5TUCJ1nqJJOS3iXSJHmtrLK7YqCAD3lq+I/uJERL7xlF/
 AolcA+BTNEQXr2J2tU8Dvg8cVdFSVVKdMLVS/8u05s/BmIgd7U5Waf5jq4mw4Uds
 QbnHR5ENXW9RuRB68JIDJfAJ7LWaUdNoy2ggReOPMXNoh0jO4lxibETzDjyOHUuy
 H9rWfkYsCucDXBQ5tbr6DRfGkaUL5tdM2fa3/8Pfl1ErNMrnwQAOA0LkVDtuND0=
 =OvIM
 -----END PGP SIGNATURE-----
State-Changed-From-To: open->closed 
State-Changed-By: swills 
State-Changed-When: Sun Aug 14 00:37:43 UTC 2011 
State-Changed-Why:  
An entry was added to UPDATING for this. Issue should be resolved, 
reopen if not. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=158611 
>Unformatted:
