From sunpoet@sunpoet.net  Sun Feb 21 18:20:44 2010
Return-Path: <sunpoet@sunpoet.net>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 4AEE4106566B
	for <FreeBSD-gnats-submit@freebsd.org>; Sun, 21 Feb 2010 18:20:44 +0000 (UTC)
	(envelope-from sunpoet@sunpoet.net)
Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54])
	by mx1.freebsd.org (Postfix) with ESMTP id 0D0E48FC0C
	for <FreeBSD-gnats-submit@freebsd.org>; Sun, 21 Feb 2010 18:20:43 +0000 (UTC)
Received: by vws14 with SMTP id 14so824230vws.13
        for <FreeBSD-gnats-submit@freebsd.org>; Sun, 21 Feb 2010 10:20:36 -0800 (PST)
Received: by 10.220.125.103 with SMTP id x39mr6633298vcr.130.1266776435853;
        Sun, 21 Feb 2010 10:20:35 -0800 (PST)
Received: from sunpoet.net (sunpoet.net [220.133.12.240])
        by mx.google.com with ESMTPS id 35sm24303791vws.0.2010.02.21.10.20.34
        (version=TLSv1/SSLv3 cipher=RC4-MD5);
        Sun, 21 Feb 2010 10:20:35 -0800 (PST)
Received: by sunpoet.net (Postfix, from userid 1000)
	id 59DAA2AEC55D; Mon, 22 Feb 2010 02:20:18 +0800 (CST)
Message-Id: <20100221182018.59DAA2AEC55D@sunpoet.net>
Date: Mon, 22 Feb 2010 02:20:18 +0800 (CST)
From: Sunpoet Po-Chuan Hsieh <sunpoet@sunpoet.net>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: [REPOCOPY] security/libassuan -> security/libassuan2
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         144186
>Category:       ports
>Synopsis:       [REPOCOPY] security/libassuan -> security/libassuan2
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kuriyama
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Sun Feb 21 18:30:05 UTC 2010
>Closed-Date:    Tue Jun 15 01:16:16 UTC 2010
>Last-Modified:  Tue Jun 15 01:16:16 UTC 2010
>Originator:     Sunpoet Po-Chuan Hsieh
>Release:        FreeBSD 8.0-STABLE amd64
>Organization:
SUNPOET.net
>Environment:
System: FreeBSD bonjour.sunpoet.net 8.0-STABLE FreeBSD 8.0-STABLE #0: Fri Feb 12 20:20:34 CST 2010
>Description:
This is the IPC library used by GnuPG 2, GPGME and a few other
packages.

The primary FTP site is ftp://ftp.gnupg.org/gcrypt/libassuan.

Generated with FreeBSD Port Tools 0.99
>How-To-Repeat:
>Fix:

--- libassuan-2.0.0.shar begins here ---
# This is a shell archive.  Save it in a file, remove anything before
# this line, and then unpack it by entering "sh file".  Note, it may
# create directories; files and directories will be owned by you and
# have default permissions.
#
# This archive contains:
#
#	libassuan2
#	libassuan2/pkg-descr
#	libassuan2/Makefile
#	libassuan2/distinfo
#
echo c - libassuan2
mkdir -p libassuan2 > /dev/null 2>&1
echo x - libassuan2/pkg-descr
sed 's/^X//' >libassuan2/pkg-descr << 'bd936f8e06a1612d63231207d1db5565'
XThis is the IPC library used by GnuPG 2, GPGME and a few other
Xpackages.
X
XThe primary FTP site is ftp://ftp.gnupg.org/gcrypt/libassuan.
bd936f8e06a1612d63231207d1db5565
echo x - libassuan2/Makefile
sed 's/^X//' >libassuan2/Makefile << 'b76c3ad95736daab605a25185acae8d9'
X# New ports collection makefile for:	libassuan2
X# Date created:		2010-02-22
X# Whom:			Sunpoet Po-Chuan Hsieh <sunpoet@sunpoet.net>
X#
X# $FreeBSD$
X#
X
XPORTNAME=		libassuan
XPORTVERSION=		2.0.0
XCATEGORIES=		security devel
XMASTER_SITES=		${MASTER_SITE_GNUPG}
XMASTER_SITE_SUBDIR=	${PORTNAME}
X
XMAINTAINER=		sunpoet@sunpoet.net
XCOMMENT=		IPC library used by GnuPG 2, GPGME and a few other packages
X
XGNU_CONFIGURE=		yes
XINFO=			assuan
XUSE_BZIP2=		yes
XUSE_LDCONFIG=		yes
XPLIST=			bin/libassuan-config include/assuan.h lib/libassuan.la \
X			lib/libassuan.so.0 share/aclocal/libassuan.m4
X
X.include <bsd.port.pre.mk>
X
X.if ${ARCH} == "amd64"
XCFLAGS+=		-fPIC
X.endif
X
X.include <bsd.port.post.mk>
b76c3ad95736daab605a25185acae8d9
echo x - libassuan2/distinfo
sed 's/^X//' >libassuan2/distinfo << 'e31990c595a6c02faef858b1c00b595e'
XMD5 (libassuan-2.0.0.tar.bz2) = 59bc0ae7194c412d7a522029005684b2
XSHA256 (libassuan-2.0.0.tar.bz2) = fd2a04b0d14b1097248a2b97c33087c095e52cc7978ff6f9d4d432dd25d17f8f
XSIZE (libassuan-2.0.0.tar.bz2) = 449563
e31990c595a6c02faef858b1c00b595e
exit
--- libassuan-2.0.0.shar ends here ---

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-ports-bugs->miwi 
Responsible-Changed-By: miwi 
Responsible-Changed-When: Mon Feb 22 10:58:49 UTC 2010 
Responsible-Changed-Why:  
I'll take it. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=144186 
State-Changed-From-To: open->repocopy 
State-Changed-By: miwi 
State-Changed-When: Fri Mar 19 14:26:16 UTC 2010 
State-Changed-Why:  
Please repocoy security/libassuan -> security/libassuan2 




Responsible-Changed-From-To: miwi->portmgr 
Responsible-Changed-By: miwi 
Responsible-Changed-When: Fri Mar 19 14:26:16 UTC 2010 
Responsible-Changed-Why:  
Please repocoy security/libassuan -> security/libassuan2 



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

From: "Jason E. Hale" <bsdkaffee@gmail.com>
To: bug-followup@freebsd.org
Cc: sunpoet@sunpoet.net,
 Martin Wilke <miwi@freebsd.org>
Subject: Re: ports/144186: [REPOCOPY] security/libassuan
Date: Sat, 20 Mar 2010 02:36:16 -0500

 Hi,
 
 I maintain security/gpa and security/gpgme, both use libassuan in some form.  
 I think we should wait on this and update the existing security/libassuan when 
 all of its dependent ports are ready for update.  libassuan 2.x will conflict 
 with 1.x.  According to the gnupg mailing list 
 http://lists.gnupg.org/pipermail/gnupg-announce/2010q1/000297.html these two 
 versions should not be installed together.
 
 These ports use libassuan:
 deskutils/kdepim4 -> updated for libassuan 2.x in svn
 security/dirmngr -> RC out now with update for libassuan 2.x, release should 
 be soon
 security/gnupg -> version 2.0.15 needs 2.x
 security/gpgme -> version 1.3.0 needs 2.x (current version uses internal 1.x 
 copy)
 security/gpa -> update for 2.x in cvs (backport would be trival)
 
 The only thing we would really have to wait for would be KDE.  Sorry I didn't 
 see this sooner, but I think it is worth waiting just a bit longer instead of 
 causing library conflicts.  Most of these ports are tightly woven together 
 anyways and will need to be updated together.
 
 - Jason

From: Martin Wilke <miwi@FreeBSD.org>
To: "Jason E. Hale" <bsdkaffee@gmail.com>
Cc: bug-followup@freebsd.org, sunpoet@sunpoet.net
Subject: Re: ports/144186: [REPOCOPY] security/libassuan
Date: Sat, 20 Mar 2010 10:20:52 +0100

 -----BEGIN PGP SIGNED MESSAGE-----
 Hash: SHA1
 
 On Sat, Mar 20, 2010 at 02:36:16AM -0500, Jason E. Hale wrote:
 > Hi,
 >=20
 > I maintain security/gpa and security/gpgme, both use libassuan in some fo=
 rm. =20
 > I think we should wait on this and update the existing security/libassuan=
  when=20
 > all of its dependent ports are ready for update.  libassuan 2.x will conf=
 lict=20
 > with 1.x.  According to the gnupg mailing list=20
 > http://lists.gnupg.org/pipermail/gnupg-announce/2010q1/000297.html these =
 two=20
 > versions should not be installed together.
 >=20
 > These ports use libassuan:
 > deskutils/kdepim4 -> updated for libassuan 2.x in svn
 > security/dirmngr -> RC out now with update for libassuan 2.x, release sho=
 uld=20
 > be soon
 > security/gnupg -> version 2.0.15 needs 2.x
 > security/gpgme -> version 1.3.0 needs 2.x (current version uses internal =
 1.x=20
 > copy)
 > security/gpa -> update for 2.x in cvs (backport would be trival)
 >=20
 > The only thing we would really have to wait for would be KDE.  Sorry I di=
 dn't=20
 > see this sooner, but I think it is worth waiting just a bit longer instea=
 d of=20
 > causing library conflicts.  Most of these ports are tightly woven togethe=
 r=20
 > anyways and will need to be updated together.
 
 the problem is security/libassuan2 is needed for a gnupgpg and the maintain=
 er
 poked me to make the repocopy.
 
 
 >=20
 > - Jason
 >=20
 
 - --=20
 
                       \ || /
                      ( * * )
 +-----------------oOO--(_)--OOo-------------------------+
 |  PGP    : 0xB1E6FCE9  |				|
 |  Skype  : splash_111  |  Mail   : miwi(at)FreeBSD.org |
 +-----------------------+-------------------------------+
 |	Mess with the Best, Die like the Rest!		|
 +-----------------------+-------------------------------+
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2.0.14 (FreeBSD)
 
 iEYEARECAAYFAkukk3QACgkQdLJIhLHm/OlQcwCfRfwFRIF290PkkPsBFphCSQjs
 9IgAoItyFE2lZzTTQ4k8qG5msHiqvcqY
 =3DMF7P
 -----END PGP SIGNATURE-----

From: Sunpoet Po-Chuan Hsieh <sunpoet@sunpoet.net>
To: Martin Wilke <miwi@FreeBSD.org>
Cc: "Jason E. Hale" <bsdkaffee@gmail.com>, bug-followup@freebsd.org
Subject: Re: ports/144186: [REPOCOPY] security/libassuan
Date: Sat, 20 Mar 2010 17:30:01 +0800

 On Sat, Mar 20, 2010 at 10:20:52AM +0100, Martin Wilke wrote:
 > On Sat, Mar 20, 2010 at 02:36:16AM -0500, Jason E. Hale wrote:
 > > Hi,
 > > 
 > > I maintain security/gpa and security/gpgme, both use libassuan in some form.  
 > > I think we should wait on this and update the existing security/libassuan when 
 > > all of its dependent ports are ready for update.  libassuan 2.x will conflict 
 > > with 1.x.  According to the gnupg mailing list 
 > > http://lists.gnupg.org/pipermail/gnupg-announce/2010q1/000297.html these two 
 > > versions should not be installed together.
 > > 
 > > These ports use libassuan:
 > > deskutils/kdepim4 -> updated for libassuan 2.x in svn
 > > security/dirmngr -> RC out now with update for libassuan 2.x, release should 
 > > be soon
 > > security/gnupg -> version 2.0.15 needs 2.x
 > > security/gpgme -> version 1.3.0 needs 2.x (current version uses internal 1.x 
 > > copy)
 > > security/gpa -> update for 2.x in cvs (backport would be trival)
 > > 
 > > The only thing we would really have to wait for would be KDE.  Sorry I didn't 
 > > see this sooner, but I think it is worth waiting just a bit longer instead of 
 > > causing library conflicts.  Most of these ports are tightly woven together 
 > > anyways and will need to be updated together.
 > 
 > the problem is security/libassuan2 is needed for a gnupgpg and the maintainer
 > poked me to make the repocopy.
 > 
 
 I think the library conflicts can be avoided by adding appropriate CONCLICTS
 to both security/libassuan and security/libassuan2. Apologize for missing 
 that in this PR. The port maintainers may choose to use libassuan 1.x or 2.x.
 
 > > 
 > > - Jason
 > > 
 > 
 > -- 
 > 
 >                       \ || /
 >                      ( * * )
 > +-----------------oOO--(_)--OOo-------------------------+
 > |  PGP    : 0xB1E6FCE9  |				|
 > |  Skype  : splash_111  |  Mail   : miwi(at)FreeBSD.org |
 > +-----------------------+-------------------------------+
 > |	Mess with the Best, Die like the Rest!		|
 > +-----------------------+-------------------------------+
 
 -- 
                               Sunpoet Po-Chuan Hsieh <sunpoet@sunpoet.net>

From: "Jason E. Hale" <bsdkaffee@gmail.com>
To: "Sunpoet Po-Chuan Hsieh" <sunpoet@sunpoet.net>
Cc: Martin Wilke <miwi@freebsd.org>,
 bug-followup@freebsd.org,
 portmgr@freebsd.org,
 kuriyama@freebsd.org
Subject: Re: ports/144186: [REPOCOPY] security/libassuan
Date: Sat, 20 Mar 2010 06:01:56 -0400

 On Saturday 20 March 2010 05:30:01 Sunpoet Po-Chuan Hsieh wrote:
 > On Sat, Mar 20, 2010 at 10:20:52AM +0100, Martin Wilke wrote:
 > > On Sat, Mar 20, 2010 at 02:36:16AM -0500, Jason E. Hale wrote:
 > > > Hi,
 > > >
 > > > I maintain security/gpa and security/gpgme, both use libassuan in some
 > > > form. I think we should wait on this and update the existing
 > > > security/libassuan when all of its dependent ports are ready for
 > > > update.  libassuan 2.x will conflict with 1.x.  According to the gnupg
 > > > mailing list
 > > > http://lists.gnupg.org/pipermail/gnupg-announce/2010q1/000297.html
 > > > these two versions should not be installed together.
 > > >
 > > > These ports use libassuan:
 > > > deskutils/kdepim4 -> updated for libassuan 2.x in svn
 > > > security/dirmngr -> RC out now with update for libassuan 2.x, release
 > > > should be soon
 > > > security/gnupg -> version 2.0.15 needs 2.x
 > > > security/gpgme -> version 1.3.0 needs 2.x (current version uses
 > > > internal 1.x copy)
 > > > security/gpa -> update for 2.x in cvs (backport would be trival)
 > > >
 > > > The only thing we would really have to wait for would be KDE.  Sorry I
 > > > didn't see this sooner, but I think it is worth waiting just a bit
 > > > longer instead of causing library conflicts.  Most of these ports are
 > > > tightly woven together anyways and will need to be updated together.
 > >
 > > the problem is security/libassuan2 is needed for a gnupgpg and the
 > > maintainer poked me to make the repocopy.
 > 
 > I think the library conflicts can be avoided by adding appropriate
 >  CONCLICTS to both security/libassuan and security/libassuan2. Apologize
 >  for missing that in this PR. The port maintainers may choose to use
 >  libassuan 1.x or 2.x.
 > 
 > > > - Jason
 > 
 
 I don't think that is going to work because if security/gnupg is updated to 
 use libassuan 2.x, then the build of security/gpa is going to fail because it 
 currently requires security/libassuan (1.x) and security/gnupg.  
 security/gnupg will register a libdepends on security/libassuan2, then when 
 building, security/gpa will try to pull in security/libassuan which will 
 conflict and the build will fail.
 
 I would also then have to update security/gpgme to use libassuan2, but kdepim4 
 requires both libassuan 1.x and gpgme.  I don't really see how all of this is 
 going to play nicely.
 
 - Jason

From: Jun Kuriyama <kuriyama@FreeBSD.org>
To: "Jason E. Hale" <bsdkaffee@gmail.com>
Cc: Sunpoet Po-Chuan Hsieh <sunpoet@sunpoet.net>, Martin Wilke <miwi@freebsd.org>, bug-followup@freebsd.org, 
	portmgr@freebsd.org, Jun Kuriyama <kuriyama@freebsd.org>
Subject: Re: ports/144186: [REPOCOPY] security/libassuan
Date: Sat, 20 Mar 2010 20:19:22 +0900

 2010/3/20 Jason E. Hale <bsdkaffee@gmail.com>:
 >> > > security/gpa -> update for 2.x in cvs (backport would be trival)
 
 If you provide this patch, I'd like to go this way:
 
 1.  Request repocopy from libassuan to libassuan1 (this will be cvs
 removed after transition)
 2.  Modify dependents to point libassuan1 for now.
 3.  Update libassuan to 2.x.
 4.  Update gnupg to use 2.x (change libdepends from libassuan1 to
 libassuan) and gpgme to use libassuan (2.x) with your patch.
 
 Is this work for security/gpgme?
 
 
 -- 
 Jun Kuriyama <kuriyama@FreeBSD.org> // FreeBSD Project
          <kuriyama@s2factory.co.jp> // S2 Factory, Inc.

From: "Jason E. Hale" <bsdkaffee@gmail.com>
To: Jun Kuriyama <kuriyama@freebsd.org>
Cc: "Sunpoet Po-Chuan Hsieh" <sunpoet@sunpoet.net>,
 Martin Wilke <miwi@freebsd.org>,
 bug-followup@freebsd.org,
 portmgr@freebsd.org
Subject: Re: ports/144186: [REPOCOPY] security/libassuan
Date: Sat, 20 Mar 2010 16:13:40 -0400

 On Saturday 20 March 2010 07:19:22 Jun Kuriyama wrote:
 > 2010/3/20 Jason E. Hale <bsdkaffee@gmail.com>:
 > >> > > security/gpa -> update for 2.x in cvs (backport would be trival)
 > 
 > If you provide this patch, I'd like to go this way:
 > 
 > 1.  Request repocopy from libassuan to libassuan1 (this will be cvs
 > removed after transition)
 > 2.  Modify dependents to point libassuan1 for now.
 > 3.  Update libassuan to 2.x.
 > 4.  Update gnupg to use 2.x (change libdepends from libassuan1 to
 > libassuan) and gpgme to use libassuan (2.x) with your patch.
 > 
 > Is this work for security/gpgme?
 > 
 I could update gpgme, but libassuan 1.x and libassuan 2.x install conflicting 
 files.  How is this going to be resolved?
 
 security/gpa and deskutils/kdepim4 both depend on gpgme and libassuan 1.x, so 
 we can't use CONFLICTS.  I would be willing to backport changes to 
 security/gpa to get it to work with libassuan 2.x.  The only remaining issue 
 would be deskutils/kdepim4.  Once that is updated, we can remove libassuan 
 1.x.
State-Changed-From-To: repocopy->open 
State-Changed-By: marcus 
State-Changed-When: Mon Mar 22 16:30:10 UTC 2010 
State-Changed-Why:  
I am not doing the repocopy until everything gets sorted out between various 
maintainers.  When a consensus is reached, please assign it back to portmgr. 


Responsible-Changed-From-To: portmgr->miwi 
Responsible-Changed-By: marcus 
Responsible-Changed-When: Mon Mar 22 16:30:10 UTC 2010 
Responsible-Changed-Why:  
I am not doing the repocopy until everything gets sorted out between various 
maintainers.  When a consensus is reached, please assign it back to portmgr. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=144186 
Responsible-Changed-From-To: miwi->kuriyama 
Responsible-Changed-By: miwi 
Responsible-Changed-When: Fri Apr 2 17:28:24 UTC 2010 
Responsible-Changed-Why:  
kuriyama want to deal with that. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=144186 
State-Changed-From-To: open->suspended 
State-Changed-By: linimon 
State-Changed-When: Thu Jun 3 02:28:53 UTC 2010 
State-Changed-Why:  
Apparently consensus has not yet been reached. 

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

From: Sunpoet Hsieh <sunpoet@sunpoet.net>
To: linimon@freebsd.org
Cc: kuriyama@freebsd.org, bug-followup@freebsd.org
Subject: Re: ports/144186: [REPOCOPY] security/libassuan -> 
	security/libassuan2
Date: Mon, 14 Jun 2010 12:07:10 +0800

 Hi,
 
 dougb@ has committed the update from 1.0.5 to 2.0.0 and modifications
 to libassuan-related ports.
 Please close this PR.
 Thanks.
 
 - Sunpoet
State-Changed-From-To: suspended->closed 
State-Changed-By: linimon 
State-Changed-When: Tue Jun 15 01:15:55 UTC 2010 
State-Changed-Why:  
Submitter says that this has already been committed. 

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