[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: RFS: dbxml



Hi Jeroen,

> Dear Mentors,
> 
> I am looking for a sponsor for my package "dbxml".
> 
> * Package name    : dbxml
>   Version         : 2.5.16-1
>   Upstream Author : Oracle
> * URL             : http://www.oracle.com/technology/software/products/berkeley-db/db/index.html
> * License         : BSD and Apache 1.1
>   Section         : unknown
> 

[...]

Thank you for tackling this large piece of software.  I just did a review of the
most basic Debian packaging stuff, I did not check proper function.

- debian/changelog: "squeeze" is not a valid upload destination, you want
  unstable or even experimental.
- debian/control: Section: unknown is no good. Current Standards-Version would
  be 3.9.1. You want default-jdk, not default-jdk-builddep. All description are
  extremly short. Maybe a common text describing what "Oracle Berkeley DB XML"
  is, how it differs from other libraries, etc.  would be good for all packages.
  The current descriptions would then serve as second stanza.
- debian/copyright: You have no give the license of your packaging. It might
  also make sense to go for DEP-5 format (http://dep.debian.net/deps/dep5/)
- debian/dbxml-doc.{docs,install}: What does #DOCS# stand for?
- libdbxml-java-gcj.post{inst,rm}: You must handle the various arguments that
  the post{inst,rm} might be called with. See
  http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html
- debian/README.{Debian,source}: Read their contents and act accordingly.

Package does not build:

cd dbxml && /usr/bin/make clean
make[1]: Entering directory `/home/tautschnig/debian/dbxml/dbxml-2.5.16/dbxml'
make[1]: *** No rule to make target `clean'.  Stop.
make[1]: Leaving directory `/home/tautschnig/debian/dbxml/dbxml-2.5.16/dbxml'
make: *** [clean] Error 2

You probably want to ignore errors in this step - a fresh download must be
configured before doing the make clean.

Hope this helps,
Michael

Attachment: pgpMZ02boWsL4.pgp
Description: PGP signature


Reply to: