From atallam@talarian.com  Mon Apr 16 23:35:58 2001
Return-Path: <atallam@talarian.com>
Received: from dargo.talarian.com (dargo.talarian.com [207.5.33.3])
	by hub.freebsd.org (Postfix) with ESMTP id D042D37B43F
	for <FreeBSD-gnats-submit@freebsd.org>; Mon, 16 Apr 2001 23:35:57 -0700 (PDT)
	(envelope-from atallam@talarian.com)
Received: from localhost (localhost [127.0.0.1])
	by dargo.talarian.com (Postfix) with ESMTP id 3B7D922B0B
	for <FreeBSD-gnats-submit@freebsd.org>; Mon, 16 Apr 2001 23:35:30 -0700 (PDT)
Received: from moya.talarian.com (moya.talarian.com [10.4.10.8])
	by dargo.talarian.com (Postfix) with ESMTP id 0606D22B08
	for <FreeBSD-gnats-submit@freebsd.org>; Mon, 16 Apr 2001 23:35:27 -0700 (PDT)
Received: by moya.talarian.com (Postfix, from userid 623)
	id 453B22A4; Mon, 16 Apr 2001 23:35:48 -0700 (PDT)
Message-Id: <20010417063548.453B22A4@moya.talarian.com>
Date: Mon, 16 Apr 2001 23:35:48 -0700 (PDT)
From: atallam@talarian.com
Reply-To: atallam@talarian.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: postfix port is severely broken
X-Send-Pr-Version: 3.2

>Number:         26634
>Category:       ports
>Synopsis:       The postfix port won't build with options
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-ports
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Apr 16 23:40:00 PDT 2001
>Closed-Date:    Sun Apr 22 06:13:46 PDT 2001
>Last-Modified:  Sun Apr 22 13:20:01 PDT 2001
>Originator:     Ajay Tallam
>Release:        FreeBSD 4.2-RELEASE i386
>Organization:
>Environment:

	Running postfix as mta.

>Description:

	The port seems like it is not being updated very well.  Whoever
updated it to -pl01 (and possibly to release-20010228 too, I didn't try that
one), forgot to fix the patch references.  The TLS-patches are old, so they
blow hunks (they were made for release, not -pl01).  Same with the ipv6
patches.

>How-To-Repeat:

	When you go to compile postfix (release), add IPv6 or TLS support to
the configure menu.

>Fix:

	Update the IPv6 patches, I haven't looked much at that part, but the
filename (postfix-20010225snap-v6-20010228a.diff.gz) implies that this
hasn't been updated since before this version of postfix went RELEASE, and
instead somebody just made the postfix-snapshot the postfix (release) port,
and only changed the postfix*.tgz reference.

On the postfix-tls site, you just need to get the new, -pl01 patch:
pfixtls-0.7.1-20010228-pl01-0.9.6a.tar.gz
Simple.  (That of course will end up changing these two lines to match):
DISTFILES+=     ${DISTNAME}.tar.gz pfixtls-0.7.1-20010228-pl01-0.9.6a.tar.gz
EXTRA_PATCHES+= ${WRKDIR}/pfixtls-0.7.1-20010228-pl01-0.9.6a/pfixtls.diff

(There's probably something wrong with something db-related, hard to narrow
down.  I've had enough for today. ;)
>Release-Note:
>Audit-Trail:

From: Blaz Zupan <blaz@amis.net>
To: <atallam@talarian.com>
Cc: <FreeBSD-gnats-submit@freebsd.org>
Subject: Re: ports/26634: postfix port is severely broken
Date: Tue, 17 Apr 2001 08:45:40 +0200 (CEST)

 > 	The port seems like it is not being updated very well.  Whoever
 > updated it to -pl01 (and possibly to release-20010228 too, I didn't try that
 > one), forgot to fix the patch references.  The TLS-patches are old, so they
 > blow hunks (they were made for release, not -pl01).  Same with the ipv6
 > patches.
 
 The TLS patch works just fine, you just can't use both the IPv6 and the TLS
 patch at the same time. Try the one or the other and you'll see it works.
 
 (The postfix port maintainer).
 
 Blaz Zupan,  Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia
 E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325
 
State-Changed-From-To: open->closed 
State-Changed-By: roam 
State-Changed-When: Sun Apr 22 06:13:46 PDT 2001 
State-Changed-Why:  
The port maintainer reports pilot error. 

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

From: "David W. Chapman Jr." <dwcjr@inethouston.net>
To: <FreeBSD-gnats-submit@freebsd.org>, <atallam@talarian.com>
Cc:  
Subject: Re: ports/26634: The postfix port won't build with options
Date: Sun, 22 Apr 2001 12:16:35 -0500

 The TLS patches don't get updated when a new version of them isn't required
 (i.e. when the code that the diffs modify hasn't changed).  Same with ipv6.
 They don't mix because they are separate patches from two different vendors
 that modify the same code in some places.
 

From: Ajay 'Hyperreductionist' T <atallam@gcast.com>
To: "David W. Chapman Jr." <dwcjr@inethouston.net>
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: ports/26634: The postfix port won't build with options
Date: Sun, 22 Apr 2001 13:08:27 -0700

 * David W. Chapman Jr. <dwcjr@inethouston.net> [010422 10:16], about 
 > Re: ports/26634: The postfix port won't build with options:
 :The TLS patches don't get updated when a new version of them isn't required
 :(i.e. when the code that the diffs modify hasn't changed).  Same with ipv6.
 :They don't mix because they are separate patches from two different vendors
 :that modify the same code in some places.
 :
 >-- End of excerpt from David W. Chapman Jr.
 
 	I already agreed with you on that (I thought that was the problem
 originally because the port had been updated to the release's pl01 and there
 were new tls patches available for pl1).
 But that's a non-issue already, since the port apparently does build
 cleanly/fine as-is, all I stated was that the port should be fixed so that
 either both patches can apply (a TLS+IPv6 combo patch/option), or the port
 be fixed, so that it doesn't allow a user to choose incompatible options.
 (It's only, you know, logical.)  Again, short-term this can be done by
 modifying the description of the options (TLS and IPv6, to state this.)
 
 Anywho..
>Unformatted:
