about the Berkeley DB 4 "cleanup"

2013-12-16 Thread Robert Huff

[Ref: ports/UPDATING 20131214]

I am an indirect user of BDB (currently ver 4.3); "pkg version
-r" reports

redland-1.0.16
ruby19-bdb43-0.6.6_1
webalizer-geoip-2.23.8
php5-5.4.21
xmms-1.2.11_20
libreoffice-4.0.6_1
gramps-3.3.0_2
docproj-2.0_1
librcc-0.2.12
apr-1.4.8.1.5.3
apache24-2.4.6_1
subversion-1.8.5
py27-bsddb-2.7.6_3
portupgrade-2.4.11.3,2


as being dependant, and I suspect the list will be longer with
each passing day.
While I appreciate the work done to move the universe along,
the upgrade instructions included (by reference) are partially past
my understanding and _way_ beyond my comfort zone.  (And I suspect
I'm not alone.)
So: what explodes if I simply set "WITH_BDB_VER=5", shutdown my
services, and rebuild?
Alternately: does someone whose comfort zone this is well
within) have a script that will take care of things?


Respectfully,



Robert Huff


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: about the Berkeley DB 4 "cleanup"

2013-12-16 Thread Randy Pratt
On Mon, 16 Dec 2013 07:51:54 -0500
Robert Huff  wrote:

> 
>   [Ref: ports/UPDATING 20131214]
> 
>   I am an indirect user of BDB (currently ver 4.3); "pkg version
> -r" reports
> 
>   redland-1.0.16
>   ruby19-bdb43-0.6.6_1
>   webalizer-geoip-2.23.8
>   php5-5.4.21
>   xmms-1.2.11_20
>   libreoffice-4.0.6_1
>   gramps-3.3.0_2
>   docproj-2.0_1
>   librcc-0.2.12
>   apr-1.4.8.1.5.3
>   apache24-2.4.6_1
>   subversion-1.8.5
>   py27-bsddb-2.7.6_3
>   portupgrade-2.4.11.3,2
> 
> 
>   as being dependant, and I suspect the list will be longer with
> each passing day.
>   While I appreciate the work done to move the universe along,
> the upgrade instructions included (by reference) are partially past
> my understanding and _way_ beyond my comfort zone.  (And I suspect
> I'm not alone.)
>   So: what explodes if I simply set "WITH_BDB_VER=5", shutdown my
> services, and rebuild?
>   Alternately: does someone whose comfort zone this is well
> within) have a script that will take care of things?

I've got a similar list of dependencies but only subversion and
apr actually use BDB.  The rest seem to be dependencies on apr.

I went a step further and set "WITH_BDB_VER=5" in /etc/make.conf and
proceeded to update.  At the end, I still had db42-4.2.52_5.  I
suspect it was because that neither apr or subversion needed updated.

I'm not sure if I should switch the origin of BDB for involved ports,
do forced rebuild of a few ports or if doing a recursive update is
needed.  Some additional direction would be much appreciated.

My eyes glazed over trying to read the Wiki link to updating since
I don't know database vocabulary so you're not alone ;-)

Randy




___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: about the Berkeley DB 4 "cleanup"

2013-12-16 Thread Matthias Andree
Am 16.12.2013 13:51, schrieb Robert Huff:
> 
>   [Ref: ports/UPDATING 20131214]
> 
>   I am an indirect user of BDB (currently ver 4.3); "pkg version
> -r" reports
> 
>   redland-1.0.16
>   ruby19-bdb43-0.6.6_1
>   webalizer-geoip-2.23.8
>   php5-5.4.21
>   xmms-1.2.11_20
>   libreoffice-4.0.6_1
>   gramps-3.3.0_2
>   docproj-2.0_1
>   librcc-0.2.12
>   apr-1.4.8.1.5.3
>   apache24-2.4.6_1
>   subversion-1.8.5
>   py27-bsddb-2.7.6_3
>   portupgrade-2.4.11.3,2
> 
> 
>   as being dependant, and I suspect the list will be longer with
> each passing day.
>   While I appreciate the work done to move the universe along,
> the upgrade instructions included (by reference) are partially past
> my understanding and _way_ beyond my comfort zone.  (And I suspect
> I'm not alone.)
>   So: what explodes if I simply set "WITH_BDB_VER=5", shutdown my
> services, and rebuild?
>   Alternately: does someone whose comfort zone this is well
> within) have a script that will take care of things?

Sorry for not providing clearer instructions.

One of the difficulties that anyone will face in writing instructions is
that I have no viable approach of telling which port uses Berkeley DB in
which ways, directly or indirectly.
  That would mean having to become acquainted with each and every port
that uses Berkeley DB in some way, figure out what it does, and how it
uses that, and explore all options.

For me, that is beyond my resources and also beyond my interest.

And, unfortunately, it will also be beyond the capabilities of a script.

So my approach was to write general instructions that look at what's in
the database directories.

I am currently investigating failures that have been reported and that I
cannot reproduce and hope to come up with refinements to the
instructions later.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: about the Berkeley DB 4 "cleanup"

2013-12-17 Thread Marko Cupać
I had db42 and db47. I checked dependant ports (pkg info -r), pasted
the list to mousepad, installed db5 with portmaster, deinstalled db42
and db47 forcefully (pkg delete -f), and recompiled ports from the list
with portmaster. Some of them failed this way, so I deinstalled them
and consequently compiled them traditional way (make install clean),
which went well. I did this on 8 different servers and I didn't
encounter any problems so far.

I feared a bit when I saw amavisd-new on the list of dependant ports on
one of my production mail servers, but I had no problem after the
upgrade.
-- 
Marko Cupać
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"