On Mon, Apr 14, 2014 at 04:09:23PM +0200, Fabian Raetz wrote:
> On Mon, Apr 14, 2014 at 03:48:03PM +0200, Pierre-Emmanuel André wrote:
> > On Mon, Apr 14, 2014 at 12:46:52PM +0100, Stuart Henderson wrote:
> > > On 2014/04/14 12:58, Fabian Raetz wrote:
> > > > Hi ports@,
> > > >
> > > > I'm working on a update for databases/db/v4 in
> > > > preparation for updating openbsd-wip/net/bitcoin.
> > > >
> > > >
> > > > When running 'make package', i get the following
> > > > Warnings/Errors for all files under /usr/local/share:
> > > >
> > > > +++ Sun Apr 13 22:26:43 CEST 2014
> > > > ===> Building package for db-java-4.8.30p0v0
> > > > Create /usr/packages/amd64/all/db-java-4.8.30p0v0.tgz
> > > > [KError: no @owner for
> > > > /usr/local/share/doc/db4/gsg/JAVA/BerkeleyDB-Core-JAVA-GSG.pdf (mischi)
> > > > Warning: no @group for
> > > > /usr/local/share/doc/db4/gsg/JAVA/BerkeleyDB-Core-JAVA-GSG.pdf (wsrc)
> > > > Error: modes don't match for
> > > > /usr/local/share/doc/db4/gsg/JAVA/BerkeleyDB-Core-JAVA-GSG.pdf
> > > > [KError: no @owner for
> > > > /usr/local/share/doc/db4/gsg/JAVA/CoreEnvUsage.html (mischi)
> > > > Warning: no @group for
> > > > /usr/local/share/doc/db4/gsg/JAVA/CoreEnvUsage.html (wsrc)
> > > > Error: modes don't match for
> > > > /usr/local/share/doc/db4/gsg/JAVA/CoreEnvUsage.html
> > > > ....
> > > > ....
> > > > *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:1890
> > > > '/usr/packages/amd64/all/db-java-4.8.30p0v0.tgz')
> > > > *** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2439
> > > > '_internal-package')
> > > > *** Error 2 in /usr/ports/databases/db/v4
> > > > (/usr/ports/infrastructure/mk/bsd.port.mk:2419 'package')
> > > > --- Sun Apr 13 22:26:47 CEST 2014
> > > >
> > > > Any ideas what's missing or what i messed up on my system?
> > >
> > > These should be owned by ${SHAREOWN}:${SHAREGRP} and check that the modes
> > > are sane.
> > >
> > > I think we could just remove the API and programmer references docs
> > > though, they aren't useful to most users, and those who do find
> > > them useful should be capable of looking in the source distribution
> > > themselves.
> > >
> > > > Here's the diff. But be aware that the diff is not yet
> > > > finished ...
> > >
> > > Other things to think about:
> > >
> > > - what do users need to do for the upgrade - is it just "log file format
> > > change" or also "database format change"? we will need to document the
> > > steps needed, and probably add @ask-update and an faq/current.html
> > > section.
> > >
> > > - db updates are fairly likely to break other ports; fortunately it's
> > > a lot less common dependency than last time it was updated in ports,
> > > so shouldn't be as bad, but definitely needs testing - I can probably
> > > help with build tests etc for this.
> > >
> > > - it will need testing on a wide spread of machine architectures.
> > >
> > >
> >
> > Hi,
> >
> > Last time i tried to upgrade bdb, it was painfull. All my applications
> > using it were broken due to
> > the log format change. A "dump/restore" was needed (i can't remember what i
> > do to fix the upgrade.. let
> > me check my old logs ).
> > IIRC, python < 3 will be broken too because of the py-bsddb module, see
> > https://docs.python.org/2/library/bsddb.html).
> > You can find my work on this update here: http://www.raveland.org/bdb/
> > I don't have retried these diff.. i think a bit of cleaning is needed. But
> > if you need help, i'm volunteer.
>
> Hi,
>
> i will try your diffs. They look a bit more complete than mine
> (SHARED_LIBS / WANTLIB / MODJAVAVER / STL) etc.
>
After a bit of cleaning, it compiles:
http://www.raveland.org/bdb/db-4.8.30_8.diff
--
Pierre-Emmanuel André <pea at raveland.org>
GPG key: 0xBB8D3F0E
