Date: Thu, 13 May 2004 22:38:29 -0700 From: Ben Bangert <ben@knowledgetap.com> To: =?ISO-8859-1?Q?Lars_K=F6ller?= <lars.koeller@uni-bielefeld.de> Cc: ports@FreeBSD.org Subject: Re: FreeBSD Port: bacula-1.32f5 -> 1.3.4 updating destroys prior bacula conf files Message-ID: <EDE92EFE-A568-11D8-ACE0-0003937C4014@knowledgetap.com> In-Reply-To: <200405140511.i4E5BJ402784@rayadm.hrz.uni-bielefeld.de> References: <200405140511.i4E5BJ402784@rayadm.hrz.uni-bielefeld.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On May 13, 2004, at 10:11 PM, Lars K=F6ller wrote: > There is a problem in the portssystem and portupdate to handle conf > files with a different MD5 sum correctly. > > I miss to bypass this in the port of bacula up to 1.32f5. No a > workaround is implemented. > > The problem only occur with portupdrade, not make deinstall and > pkg_delete! The last one are my way to upgrade such an complex thing > like bacula, which holds all by important data ..... > > But I think after this nice email of you it's time to give the > maintainership over to you to make it much better. Can you imagine how > much work it is to stay with current versions of bacula and test the > various possible configurations basically? Sorry Lars. I was rather frustrated by having the files removed. Since=20= it had never happened before with any other port, during any other=20 portupgrade I've ever encountered, I assumed there was a standard port=20= template that took care of this. I'm also wondering about the version=20 issue. Portupgrade upped me to 1.3.4, not 1.32f5 as you mentioned. Is=20 1.3.4 maintained by you? It isn't so much that the files were wiped, I just was expecting a=20 notification of it. I've been using ports for years, and portupgrade=20 for quite awhile too, never had a portupgrade wipe a file. Many people=20= use portupgrade, so I was under the assumption it would be tested with=20= it. It took me several hours to rebuild my bacula catalog so I could=20 restore my old config files. Many assumptions involved, obviously some weren't warranted. Sorry again Lars, Ben=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EDE92EFE-A568-11D8-ACE0-0003937C4014>