[needs-packaging] sphinxbase

Thank you for your report. I'm marking this as triaged.

The package is uploaded to REVU [1].

[1] http://revu.tauware.de/details.py?upid=106

Jonathan: do you think you could please review the package?

Checking it out myself.

W: sphinxbase source: debian-rules-ignores-make-clean-error line 54
N:
N: A rule in the debian/rules file for this package calls the package's
N: clean or distclean target with a line like:
N:
N: -$(MAKE) distclean
N:
N: The leading - tells make to ignore all errors. Normally this is done
N: for packages using Autoconf since Makefile may not exist. However,
N: this line ignores all other error messages, not just the missing
N: Makefile error. It's better to use:
N:
N: [ ! -f Makefile ] || $(MAKE) distclean
N:
N: so that other error messages from the clean or distclean rule will
N: still be caught.
N:
W: sphinxbase source: substvar-source-version-is-deprecated libsphinxbase0-dev
N:
N: The package uses the now deprecated ${Source-Version} substvar, which
N: has misleading semantics. Please switch to ${binary:Version} or
N: ${source:Version} as appropriate. Support for ${Source-Version} may be
N: removed from dpkg-dev in the future.
N:
W: sphinxbase source: substvar-source-version-is-deprecated sphinxbase-utils
W: sphinxbase-utils: binary-without-manpage usr/bin/sphinx_cepview
N:
N: Each binary in /usr/bin, /usr/sbin, /bin, /sbin or /usr/games should
N: have a manual page
N:
N: Note, that though the `man' program has the capability to check for
N: several program names in the NAMES section, each of these programs
N: should have its own manual page (a symbolic link to the appropriate
N: manual page is sufficient) because other manual page viewers such as
N: xman or tkman don't support this.
N:
N: Refer to Policy Manual, section 12.1 for details.
N:
W: sphinxbase-utils: binary-without-manpage usr/bin/sphinx_fe
W: libsphinxbase0-dev: zero-byte-file-in-doc-directory usr/share/doc/libsphinxbase0-dev/NEWS.gz
N:
N: Package contains a file which is empty.
N:
W: libsphinxbase0: package-name-doesnt-match-sonames libsphinxad0 libsphinxfe0 libsphinxfeat0 libsphinxutil0
N:
N: The package name of a library package should usually reflect the
N: soname of the included library. The package name can determined from
N: the library file name with the following code snippet:
N:
N: $ objdump -p /path/to/libfoo-bar.so.1.2.3 | sed -n -e's/^[[:space:]]*SONAME[[:space:]]*//p' | sed -e's/\([0-9]\)\.so\./\1-/; s/\.so\.//'
N:
N: Refer to Library Packaging guide 5 for details.
N:

Also: couldn't libsphinxbase0-dev be libsphinxbase-dev? I see no reason why it should be versioned.

Thanks for the comments! I do believe lintian complained about library-version-does-not-match-soname or something like that, so I versioned it. But I also don't believe there's any good reason to version it since it isn't widely used. I will re-upload to REVU at some point today.

Also, should the priority be Extra or Optional?

Hi, I've fixed the libsphinxbase-dev problem and some of the other lintian warnings reported above. Feel free to review the packages again if you like.

New URL: http://revu.tauware.de/details.py?package=sphinxbase

From REVU:

"Please update for Hardy.

Looks like you might be missing some copyright holders in debian/copyright? As an example:
src/libsphinxad/ringbuffer.h: * Copyright (c) 1999-2000 Ross Bencina and Phil Burk

Again, the packaging looks clean."

Hi, it seems as if this package never got accepted into Ubuntu.

In the meantime, I released a new upstream version, and I have packaged it and put it into REVU:

http://revu.tauware.de/details.py?upid=2767

Hi, I came across this bug report and the REVU page after making
a sphinxbase package for 0.4.1.

I've uploaded it to my PPA (http://launchpad.net/~abhidg/+archive),
but I expect it has quite a few lintian warnings (no manpages, etc.)

The package I built does not have the python module though, never
could figure out how to make it build properly with that.

Sphinxbase is now in the Karmic repository, hence I am closing this bug.