From owner-freebsd-ports-bugs@FreeBSD.ORG Sat Mar 30 11:50:01 2013 Return-Path: Delivered-To: freebsd-ports-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A3319634 for ; Sat, 30 Mar 2013 11:50:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 94DF4EA0 for ; Sat, 30 Mar 2013 11:50:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r2UBo1tL016749 for ; Sat, 30 Mar 2013 11:50:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r2UBo1rB016748; Sat, 30 Mar 2013 11:50:01 GMT (envelope-from gnats) Date: Sat, 30 Mar 2013 11:50:01 GMT Message-Id: <201303301150.r2UBo1rB016748@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org Cc: From: Andriy Syrovenko Subject: Re: ports/175523: pkgng: mail/dovecot2-pigeonhole conflicts with mail/dovecot2 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Andriy Syrovenko List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Mar 2013 11:50:01 -0000 The following reply was made to PR ports/175523; it has been noted by GNATS. From: Andriy Syrovenko To: Harlan Stenn , bug-followup@freebsd.org, mazhe@alkumuna.eu Cc: Subject: Re: ports/175523: pkgng: mail/dovecot2-pigeonhole conflicts with mail/dovecot2 Date: Sat, 30 Mar 2013 13:41:00 +0200 The mail/dovecot2 port is (IMO) broken, and should eventually be fixed. I've just shared a (temporary) solution that worked for me. We have a dedicated VM where we incrementally updating our packages using portmaster, rebuilding the repo using 'pkg repo' and then deploying the resulting packages using pkgng on a number of production machines, so (temporarily) removing dovecot2-pigeonhole while rebuilding dovecot2 was acceptable for us. Alternatively, you can try to do the following before the upgrade, but I haven't checked this solution myself: # rm -r /usr/local/share/doc/dovecot # rm -r /usr/local/share/examples/dovecot When you do this, make sure you upgrade mail/dovecot2 first before upgrading mail/dovecot2-pigeonhole. 2013/3/30 Harlan Stenn > > So this seems to mean that we will have to stop dovecot, uninstall > pigeonhole, upgrade dovect, reinstall pigeonhole, and then restart > dovecot each time we have to upgade dovecot?