From owner-freebsd-ports@FreeBSD.ORG  Thu May 13 17:27:52 2004
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 5D73616A4CE
	for <ports@FreeBSD.org>; Thu, 13 May 2004 17:27:52 -0700 (PDT)
Received: from groovie.org (groovie.org [65.200.24.56])
	by mx1.FreeBSD.org (Postfix) with ESMTP id EE9A943D31
	for <ports@FreeBSD.org>; Thu, 13 May 2004 17:27:51 -0700 (PDT)
	(envelope-from ben@knowledgetap.com)
Received: from c-24-5-160-61.client.comcast.net ([24.5.160.61]
	helo=[192.168.2.4])	by groovie.org with asmtp (Exim 4.32; FreeBSD)
	id 1BOQY6-0008fW-AJ; Thu, 13 May 2004 17:27:51 -0700
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <7DEC7598-A53D-11D8-AFB0-0003937C4014@knowledgetap.com>
Content-Transfer-Encoding: 7bit
From: Ben Bangert <ben@knowledgetap.com>
Date: Thu, 13 May 2004 17:27:33 -0700
To: Lars.Koeller@Uni-Bielefeld.DE
X-Mailer: Apple Mail (2.613)
X-Spam-Score: -1.9 (-)
cc: ports@FreeBSD.org
Subject: FreeBSD Port: bacula-1.32f5 updating destroys prior bacula conf
	files
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 14 May 2004 00:27:52 -0000

Ummmmm

I ran portupgrade the other day on bacula. Christ was that a mistake. I 
had the absurd idea that as portupgrade has always done with every port 
thus upgraded, it would save a copy of the conf files for the port. 
Prolly to .old or something.

Hah! No, instead it completely obliterated my configuration files. 
Who's bright idea was that? Lucky I had all my conf files backed up... 
to a bacula volume... so now I need to reconfigure bacula enough to 
gain access to the volume to restore my config files.

The most braindead part of the whole thing, is that there was 
absolutely no reason to completely destroy the old bacula config files, 
since the port didn't install any .conf files, only .sample files.

At least I haven't lost anything other than my faith in FreeBSD 
ports....

-Ben

PS: Someone might consider making a note of this rather drastic action 
bacula does in the /usr/ports/UPDATING file.