Re: RFS: hivex

2010-05-10 Thread TJ 
On Sun, 2010-05-09 at 12:35 +0800, Paul Wise wrote:
 
 Looks like some symbols dissappeared from libhivex0, which now causes
 the package to FTBFS because dpkg-gensymbols fails. I'm assuming they
 were the private symbols that are now hidden. I'd suggest removing
 them from the symbols file in that case.

Yes, done. I think I was asleep at the wheel because I totally neglected
to do any build tests for some reason - sorry for wasting your time on
that!

 Apart from that, the package looks fairly good. I'm unable to commit
 to sponsoring it though, hopefully you'll find someone else with the
 ongoing time to do so.

Thanks, I'll work on that.


 Remaining minor stuff:
 
 lintian:
 
 W: libwin-hivex-perl: maintainer-not-full-name TJ
 I: libwin-hivex-perl: unused-override libhivex-perl binary:
 maintainer-not-full-name

Aha! I forgot to change the specified library name when making the Perl
package-name adjustments.

 I: libwin-hivex-perl: spelling-error-in-manpage
 usr/share/man/man3/Win::Hivex::Regedit.3pm.gz reencode re-encode

Looks like this one escaped upstream when they patched. I'll chase that
up and add a manual patch for now.

 E: libwin-hivex-perl: binary-or-shlib-defines-rpath
 ./usr/lib/perl5/auto/Win/Hivex/Hivex.so
 /tmp/buildd/hivex-1.2.2/perl/../lib/.libs

Hmmm, another rpath issue. Don't recall seeing that in previous reports.
I'll ask upstream about it. Hope I don't have to re-implement the
chrpath workaround again.

As a matter of interest, would you mind sharing the lintian commands you
use since it is still something of a mystery to me. I use one command
against the source package but I'm guessing now you're running it
against each binary package too? In fact, it'd help me a great deal to
understand the entire process you go through in doing the review - if I
can do that before uploading it'd probably make for cleaner, better,
uploads and less iterations.

 dpkg-gencontrol: warning: package hivex: unused substitution variable
 ${perl:Depends}

I recall removing this from debian/control and it resulting in a bunch
of other messages so I put it back in. I'll remove it again and look
more closely at the build log this time.

 You may want to look at debhelper 7 instead of cdbs:
 
 https://penta.debconf.org/dc9_schedule/events/418.en.html

I feel more comfortable with CDBS since I like simple-patchsys, although
now upstream has incorporated my patches it is no longer used. Reading
those slides didn't really help and I don't have time to listen to the
presentation but it mostly made my eyes glaze over :p

 You may want to look at DEP-5 for the copyright file:

 http://dep.debian.net/deps/dep5/

Crikey, another format to master :p

I've started on it but it looks to be slightly involved for hivex since
the current copyright is different for Makefiles and programs and
libraries and language bindings - figuring out the patterns for the
File specifications is going to be 'fun'.

 
 debian/libhivex0.install can be reduced to one line: usr/lib/libhivex.so.*

Ahh yes, that list of libraries was a leftover from getting the split
between the -dev and library packages correct.

 
 Is it nessecary to ship the static library? and the .la file?

Probably not, but which would be preferred in the -dev package? Looking
at other -dev packages there doesn't seem to be a clear preference.

 README probably isn't nessecary to ship in libhivex0, possibly the
 same for libhivex-ocaml and perl packages.

I think I was enjoying the easy life of not having to figure out/write
the rules to prevent the installation. I'm finding after a certain point
the need to find yet more documentation on how to fine-tune the package
becomes tiresome.

 It would be nice if the package descriptions were less template-like
 and describe the individual packages instead of the whole hivex
 project. Consider the audience for each package description when
 writing them. For example libhivex0 will almost always be
 auto-installed, so it can have a minimal description.

I see your point - changed.

I'll upload the changes in the next day or so. Thanks for the great
feedback.


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1273501743.10980.81.ca...@hephaestion

Re: RFS: hivex

2010-05-10 Thread Paul Wise 
On Mon, May 10, 2010 at 10:29 PM, TJ deb...@tjworld.net wrote:

 As a matter of interest, would you mind sharing the lintian commands you
 use since it is still something of a mystery to me. I use one command
 against the source package but I'm guessing now you're running it
 against each binary package too? In fact, it'd help me a great deal to
 understand the entire process you go through in doing the review - if I
 can do that before uploading it'd probably make for cleaner, better,
 uploads and less iterations.

I have a pbuilder hook that runs this:

#!/bin/sh
echo -n 'Installing lintian: '
apt-get install -y --force-yes --no-install-recommends lintian libwww-perl
lintian --info --display-info --display-experimental --pedantic
--show-overrides --checksums --color auto /tmp/buildd/*_amd64.changes
exit 0

Notice I run lintian against the .changes file, which checks
everything, binary and source packages.

As far as review process, usually I use mc to look at each individual
file in the debian/ dir and open another terminal with mc to refer to
other files during that. At the same time I have an email open where I
list issues as I find them. Once I've reviewed the debian/ dir I'll
look at debian/copyright and compare it with the output of
licensecheck --copyright -r ., if that doesn't find any issues then
I'll review the upstream code for license/copyright stuff as well as
embedded code copies and other stuff. Somewhere in there I'll run a
build through pbuilder, grab any warnings I can see and build it again
to check for double-build errors. As well as debian-policy 
developers-reference, some things I try to take into account are at
the links below:

http://wiki.debian.org/GettingPackaged
http://wiki.debian.org/SponsorChecklist
http://ftp-master.debian.org/REJECT-FAQ.html

A lot of this stuff can be automated or semi-automated by asking
people questions during the mentors.d.n upload process, but isn't yet.
When I find time, I'd like to change that with debexpo, the new code
for mentors.d.n:

http://wiki.debian.org/DebianMentorsNet

As I've hinted in #576184, I'd also like to expand the scope of
lintian with a package of extra tests that can rely on external
packages, access the network and so on. This would form a useful part
of debexpo too. Unfortunately I need to learn perl before I can make
any progress on that.

 You may want to look at debhelper 7 instead of cdbs:

 https://penta.debconf.org/dc9_schedule/events/418.en.html

 I feel more comfortable with CDBS since I like simple-patchsys, although
 now upstream has incorporated my patches it is no longer used. Reading
 those slides didn't really help and I don't have time to listen to the
 presentation but it mostly made my eyes glaze over :p

:)

The dh manual page is probably a significantly quicker way to get
started with debhelper 7, the video is what convinced me to start
using it though.

 You may want to look at DEP-5 for the copyright file:

 http://dep.debian.net/deps/dep5/

 Crikey, another format to master :p

 I've started on it but it looks to be slightly involved for hivex since
 the current copyright is different for Makefiles and programs and
 libraries and language bindings - figuring out the patterns for the
 File specifications is going to be 'fun'.

Note that it is only a proposal, not a requirement.

 Is it nessecary to ship the static library? and the .la file?

 Probably not, but which would be preferred in the -dev package? Looking
 at other -dev packages there doesn't seem to be a clear preference.

In Debian we seem to be moving towards not shipping the static library
and not shipping the .la file.

 README probably isn't nessecary to ship in libhivex0, possibly the
 same for libhivex-ocaml and perl packages.

 I think I was enjoying the easy life of not having to figure out/write
 the rules to prevent the installation. I'm finding after a certain point
 the need to find yet more documentation on how to fine-tune the package
 becomes tiresome.

Just use packagename.docs instead of docs. You can check out the
debhelper manual pages for stuff like dh_installdocs / dh_install.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktilji7hjbq4dlbrizv36oxzvagehfx50qg_qd...@mail.gmail.com

Re: RFS: hivex

2010-05-08 Thread TJ 

I've uploaded 1.2.2-1 to mentors. This version is based on the new
upstream release that incorporates various changes to fix issues
discovered during Debian packaging.

This version still contains my packaging tracking notes in debian/. If
this version is considered ready I'll remove those notes and upload a
final 1.2.2-2 ready for the archive.

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/h/hivex
- Source repository: deb-src http://mentors.debian.net/debian unstable main 
contrib non-free
- dget http://mentors.debian.net/debian/pool/main/h/hivex/hivex_1.2.2-1.dsc

Summary of actions for this iteration:

  * ACTION: Add quilt debian/patches/series with current patch listed.
  * ACTION: Added project mailing-list posting URL to patch according to DEP-3.
  * ACTION: Add *.lintian-overrides for binary packages.
  * ACTION: Run automake to update various Makefile.in.
  * ACTION: Moved hivex man-page to libhivex-dev.
  * ACTION: removed some ${shlibs:Depends} to quiet build warnings.
  * PENDING: Reported RPATH issue to project mailing-list.
 UPDATE: upstream accept this is a bug but not sure how to fix as yet.
 UPDATE: fixed upstream.
  * PENDING: man-page spelling errors reported to project mailing-list.
 UPDATE: upstream applied corrected spelling.
  * PENDING: Reported internal/foreign exported symbols issue to project 
mailing-list.
 UPDATE: upstream accepted this and will correct.
  * PENDING: Asked on project mailing list about hivexsh dependency on 
libncurses.
 UPDATE: upstream has offered a patch for testing which resolves this.
  * PENDING: Asked on debian-perl mailing list about correct naming of 
libhivex-perl.
UPDATE: Binary package name *should* be libwin-hivex-perl. Changed.
  * TODO: wait for upstream to release new tarball incorporating accepted fixes 
and rebuild
  with new version number.
UPDATE: New upstream release 1.2.2
  * TODO: remove build-depend on chrpath and debian/rules statement after 
upstream publish new release.
UPDATE: Done.



-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1273312259.10980.15.ca...@hephaestion

Re: RFS: hivex

2010-05-08 Thread Paul Wise 
On Sat, May 8, 2010 at 5:50 PM, TJ deb...@tjworld.net wrote:

 I've uploaded 1.2.2-1 to mentors. This version is based on the new
 upstream release that incorporates various changes to fix issues
 discovered during Debian packaging.

Looks like some symbols dissappeared from libhivex0, which now causes
the package to FTBFS because dpkg-gensymbols fails. I'm assuming they
were the private symbols that are now hidden. I'd suggest removing
them from the symbols file in that case.

Apart from that, the package looks fairly good. I'm unable to commit
to sponsoring it though, hopefully you'll find someone else with the
ongoing time to do so.

Remaining minor stuff:

lintian:

W: libwin-hivex-perl: maintainer-not-full-name TJ
I: libwin-hivex-perl: unused-override libhivex-perl binary:
maintainer-not-full-name
I: libwin-hivex-perl: spelling-error-in-manpage
usr/share/man/man3/Win::Hivex::Regedit.3pm.gz reencode re-encode
E: libwin-hivex-perl: binary-or-shlib-defines-rpath
./usr/lib/perl5/auto/Win/Hivex/Hivex.so
/tmp/buildd/hivex-1.2.2/perl/../lib/.libs

dpkg-gencontrol: warning: package hivex: unused substitution variable
${perl:Depends}

You may want to look at debhelper 7 instead of cdbs:

https://penta.debconf.org/dc9_schedule/events/418.en.html

You may want to look at DEP-5 for the copyright file:

http://dep.debian.net/deps/dep5/

debian/libhivex0.install can be reduced to one line: usr/lib/libhivex.so.*

Is it nessecary to ship the static library? and the .la file?

README probably isn't nessecary to ship in libhivex0, possibly the
same for libhivex-ocaml and perl packages.

It would be nice if the package descriptions were less template-like
and describe the individual packages instead of the whole hivex
project. Consider the audience for each package description when
writing them. For example libhivex0 will almost always be
auto-installed, so it can have a minimal description.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/j2ie13a36b31005082135xa70f97eby80c44f5747119...@mail.gmail.com

Re: RFS: hivex

2010-04-02 Thread TJ 
On Fri, 2010-04-02 at 12:00 +0800, Paul Wise wrote:
 A review of your package:

Great, thanks. As a result I've learned a lot about areas of Debian
packaging I've never really needed to master before, but I've got a
headache and vacant expression to go with it :)

I've uploaded 1.2.1-2 to mentors for further review.

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/h/hivex
- Source repository: deb-src http://mentors.debian.net/debian unstable main 
contrib non-free
- dget http://mentors.debian.net/debian/pool/main/h/hivex/hivex_1.2.1-2.dsc

I'm keeping track of RFS responses and my actions in the file
debian/Debian-Mentor-RFS-Feedback.txt. This and other superfluous text
files will be removed once the package is ready.

I've figured out how to use lintian now - beforehand I was quite hazy on
it. Aside from some trivial issues (documented in my feedback) none of
the warnings or errors you revealed occur for this build.

Here's a summary of my actions:

  * INFO: debian/copyright-questions.txt, 
debian/ubuntu-bug-report-needs-packaging.txt and 
debian/Debian-Mentor-RFS-Feedback.txt
 and other text files are being kept as working notes and records of 
actions whilst doing the packaging
 and will be removed once the package is ready for the 'real' world.
  * INFO: lintian override maintainer-not-full-name is to make clear I *am* 
using my *full name* and don't want
 to be told don't use initials when I'm not (had that several times in 
past few years with Ubuntu).
  * ACTION: Removed comments and blank lines from debian/watch.
  * ACTION: Removed debian/patches/02_Do_not_clean_pkg-config_script.patch: 
It is the debian/rules clean that is removing
./hivex.pc by doing a make distclean on the source. As ./configure 
rebuilds it this isn't a real problem except
when building the debian source package.
  * TODO:  removal of hivex.pc by packaging distclean needs investigating and 
fixing.
  * PENDING: Have mailed the libguestfs list regarding the Makefile patches to 
fully clean up, and regarding the pod2html
 complaints.
 UPDATE: upstream replied accepting my Makefile patch once their git repo 
is working (hardware problems). pod2html issues
 are caused by a bug in pod2html; upstream author is happy with the output 
(which is primarily for the libguestfs web-site,
 not the binary packages).
  * ACTION: Have added Forwarded and Last-Update to 
debian/patches/01_Makefiles_clean_all_built_files.patch
  * ACTION: Finally understand what 3.0 (quilt) means: that there is now an 
additional package-version-debian.tar.gz
 that contains the debian/ directory. Removed CDBS simplepatchsys rule from 
debian/rules.
  * ACTION: Have mailed the libguestfs list questioning the copyrights: whether 
the use of GPL v2 is intentional or the result of
 template files. Will await a reply before making changes.
 UPDATE: reply received: GPL applies to build scripts and programs, LGPL to 
libraries and bindings. Updated debian/copyright.
  * ACTION: rename lib package to libhivex0 to match SO-name of library.
  * ACTION: move .a .la static libraries .install rules to -dev package.
  * ACTION: remove hard-coded Depends: from binary packages in debian/control.
  * ACTION: modified debian/control to avoid lintian 
duplicate-short-description warnings.
  * ACTION: added Section: libdevel to libhivex-dev.
  * ACTION: corrected debian/changelog Closes: to Debian bug. (originally 
package for my Ubuntu PPA, hence the LP reference).
  * ACTION: moved libhivex.so.0 symlink to -dev package.
  * ACTION: generated debian/libhivex0.symbols (relaxed version to 1.2.1 from 
1.2.1-1).
  * ACTION: changed libhivex-perl to Section: perl.
  * ACTION: Debian Perl Policy section 2.3 
(http://www.debian.org/doc/packaging-manuals/perl-policy/ch-perl.html#s-paths) 
seems to
 require that perl-module-in-core-directory be resolved by installing these 
files to the vendor location.
  * ACTION: added ${perl:Depends} to -perl package as recommended in Perl 
Policy 4.4.3.
  * ACTION: added dh_install excludes for unwanted Perl library files 
perllocal.pod and .packlist.
  * ACTION: added libhivex-ocaml-dev package to contain development files.
  * ACTION: added usr/share/locale to debian/hivex.install to install missing 
translations.
  * QUESTION: I'm not clear what the expected 'fix' is for libhivex-perl: 
binary-or-shlib-defines-rpath? I've read about RPATH
 issues (http://wiki.debian.org/RpathIssue) but can't see how it applies in 
this case. I'm presuming upstream know what they're
 doing setting installation targets for the Perl bindings.
 RESOLVED: Build-depend on chrpath and add override to debian/rules.
  * QUESTION: Perl Policy 4.2 suggests package name convention ...for module 
Foo::Bar is libfoo-bar-perl. That suggests 
 the package name here should be libwin-hivex-perl, which doesn't 'feel' 
correct. Is libhivex-perl acceptable?
  *

Re: RFS: hivex

2010-04-02 Thread Paul Wise 
The patches do not get applied when unpacking the source package, you
are missing a debian/patches/series file.

Since you are patching Makefile.am files, you need to run automake and
clean up afterwards.

In addition, if you can, please be more specific with the forwarded
field in patches. I imagine upstream has mailing list archives, so you
could add the URL to that (or to gmane/etc) in the forwarded field.

On Sat, Apr 3, 2010 at 4:23 AM, TJ deb...@tjworld.net wrote:

  * INFO: debian/copyright-questions.txt, 
 debian/ubuntu-bug-report-needs-packaging.txt and 
 debian/Debian-Mentor-RFS-Feedback.txt
     and other text files are being kept as working notes and records of 
 actions whilst doing the packaging
     and will be removed once the package is ready for the 'real' world.

Fair enough.

  * INFO: lintian override maintainer-not-full-name is to make clear I *am* 
 using my *full name* and don't want
     to be told don't use initials when I'm not (had that several times in 
 past few years with Ubuntu).

My apologies, I don't come across many folks with a two-letter first
name and no last name, so I thought you were just trying to hide your
real name.

Please add overrides for the binary package warnings too. dh_lintian
can help install them appropriately.

  * ACTION: added dh_install excludes for unwanted Perl library files 
 perllocal.pod and .packlist.

Might be appropriate to send upstream a patch for this.

  * QUESTION: I'm not clear what the expected 'fix' is for libhivex-perl: 
 binary-or-shlib-defines-rpath? I've read about RPATH
     issues (http://wiki.debian.org/RpathIssue) but can't see how it applies 
 in this case. I'm presuming upstream know what they're
     doing setting installation targets for the Perl bindings.
     RESOLVED: Build-depend on chrpath and add override to debian/rules.

Given that the rpath that is added to the perl lib is an absolute path
to the build directory of the library, I'd suggest this is an upstream
bug. rpath is a runtime thing so it never makes sense to set it to a
build directory.

  * QUESTION: Perl Policy 4.2 suggests package name convention ...for module 
 Foo::Bar is libfoo-bar-perl. That suggests
     the package name here should be libwin-hivex-perl, which doesn't 'feel' 
 correct. Is libhivex-perl acceptable?

I'm not sure here, you might want to contact the debian-perl list about it.

  * QUESTION: mis-spelling reencode in man files by upstream. I would feel 
 extremely pedantic to raise that with the authors on
     top of the other queries I've been sending their way. Is this something 
 that can be ignored (maybe with an override) ?

As a pedantic-level lintian complaint, it is fine to ignore it.
Overriding it would not be appropriate since it isn't a false positive
that cannot be fixed in lintian. I personally send upstream a patch
and then ignore it on the Debian side. I've never had a problem with
upstream not accepting spelling fixes.

You're installing the hivex manual page in the shared library package.
I'd suggest moving that to the -dev package.

About the symbols file, it looks like upstream is exporting some of
the library's internal and helper functions, I would have thought they
should only be exporting the hivex_* functions. Please point them at
this document:

http://gcc.gnu.org/wiki/Visibility

The package FTBFS when building twice in a row:

dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: building hivex using existing ./hivex_1.2.1.orig.tar.gz
dpkg-source: error: cannot represent change to
hivex-1.2.1/images/large: binary file contents changed
dpkg-source: error: add images/large in debian/source/include-binaries
if you want to store the modified binary in the debian tarball
dpkg-source: warning: ignoring deletion of file hivex.pc
dpkg-source: error: unrepresentable changes to source
dpkg-buildpackage: error: dpkg-source -b hivex-1.2.1 gave error exit status 2

This is probably to do with your patches not applying or not running automake.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/v2je13a36b31004021903oe24852dds4fb28011cdb5f...@mail.gmail.com

RFS: hivex

2010-04-01 Thread TJ 
Dear mentors,

I am looking for a sponsor for my package hivex.

* Package name: hivex
  Version : 1.2.1-1
  Upstream Author : Richard W.M. Jones rjo...@redhat.com
* URL : http://libguestfs.org/
* License : LGPL 2.1
  Section : utils

It builds these binary packages:
hivex  - Tools for reading and writing Windows Registry hive files
libhivex   - Tools for reading and writing Windows Registry hive files
libhivex-dev - Tools for reading and writing Windows Registry hive files
libhivex-ocaml - Tools for reading and writing Windows Registry hive files
libhivex-perl - Tools for reading and writing Windows Registry hive files

The package appears to be lintian clean.

My motivation for maintaining this package is: The library and tools
provide a useful facility for os-probe tools to accurately determine the
name of the default boot entry in Windows partitions of dual+ boot PCs
that can be used by GRUB to correctly name boot entries.
The library and tools can also be used by Linux-based
diagnostic/repair/configuration tools for Wine and native Windows
installations in virtual machine images or on bare hardware.

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/h/hivex
- Source repository: deb-src http://mentors.debian.net/debian unstable main 
contrib non-free
- dget http://mentors.debian.net/debian/pool/main/h/hivex/hivex_1.2.1-1.dsc

I would be glad if someone uploaded this package for me.

Kind regards
 TJ


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1270169894.2595.19.ca...@hephaestion

Re: RFS: hivex

2010-04-01 Thread Paul Wise 
A review of your package:

copyright-questions.txt and ubuntu-bug-report-needs-packaging.txt
probably aren't needed in the source package

Why do you override the maintainer-not-full-name lintian complaint?

Please send the patches upstream. If you've already done that, please
document that using DEP-3:

http://dep.debian.net/deps/dep3/

4 of the lines in debian/watch are unnessecary and can be removed.

You are using dpkg-source v3 but still include simple-patchsys.mk from
cdbs, please drop that.

libhivex (but not libhivex-dev) needs to include the ABI number in the
package name. Please read libpkg-guide and its two bug reports:

http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html
http://bugs.debian.org/libpkg-guide

You added several hardcoded library dependencies, please leave it to
the shlibs mechanism to resolve them at build time.

You Depend on Perl, I think you meant perl?

debian/changelog does not close an ITP bug, only a LaunchPad bug.

debian/copyright misses some information, some files are GPL not LGPL.

You might want to adopt DEP-5 for debian/copyright:

http://dep.debian.net/deps/dep5/

pod2html complaints:

/usr/bin/pod2html: sh/hivexsh.pod: unknown pod directive 'encoding' in
paragraph 1.  ignoring.
/usr/bin/pod2html: sh/hivexsh.pod: cannot resolve Lhivex(3) in paragraph 8.
/usr/bin/pod2html: sh/hivexsh.pod: cannot resolve Lvirt-cat(1) in paragraph 8.
/usr/bin/pod2html: sh/hivexsh.pod: cannot resolve Lguestfish(1) in
paragraph 8.
/usr/bin/pod2html: sh/hivexsh.pod: cannot resolve Lhivex(3)/WRITING
TO HIVE FILES in paragraph 22.
/usr/bin/pod2html: sh/hivexsh.pod: cannot resolve Lhivex(3) in paragraph 73.
/usr/bin/pod2html: sh/hivexsh.pod: cannot resolve Lhivexget(1) in
paragraph 73.
/usr/bin/pod2html: sh/hivexsh.pod: cannot resolve Lhivexml(1) in paragraph 73.
/usr/bin/pod2html: sh/hivexsh.pod: cannot resolve Lvirt-win-reg(1)
in paragraph 73.
/usr/bin/pod2html: sh/hivexsh.pod: cannot resolve Lguestfs(3) in paragraph 73.
/usr/bin/pod2html: sh/hivexsh.pod: cannot resolve Lvirt-cat(1) in
paragraph 73.
/usr/bin/pod2html: sh/hivexsh.pod: cannot resolve Lvirt-edit(1) in
paragraph 73.

dpkg-shlibdeps complaint:

dpkg-shlibdeps: warning: dependency on libncurses.so.5 could be
avoided if debian/hivex/usr/bin/hivexsh were not uselessly linked
against it (they use none of its symbols).

dpkg-gencontrol complaints:

dpkg-gencontrol: warning: unused substitution variable ${cdbs:Enhances}
dpkg-gencontrol: warning: unused substitution variable ${cdbs:Provides}
dpkg-gencontrol: warning: unused substitution variable ${cdbs:Conflicts}
dpkg-gencontrol: warning: unused substitution variable ${cdbs:Pre-Depends}
dpkg-gencontrol: warning: unused substitution variable ${cdbs:Replaces}
dpkg-gencontrol: warning: unused substitution variable ${cdbs:Depends}
dpkg-gencontrol: warning: unused substitution variable ${cdbs:Recommends}
dpkg-gencontrol: warning: unused substitution variable ${cdbs:Suggests}
dpkg-gencontrol: warning: unused substitution variable ${cdbs:Breaks}
dpkg-gencontrol: warning: unknown substitution variable ${shlibs:Depends}
dpkg-gencontrol: warning: unused substitution variable ${perl:Depends}

lintian complaints:

lintian --info --display-info --display-experimental --pedantic
--show-overrides --checksums --color auto
I: hivex source: duplicate-short-description libhivex libhivex-dev
hivex libhivex-perl libhivex-ocaml
O: hivex source: maintainer-not-full-name TJ
W: libhivex-dev: new-package-should-close-itp-bug
W: libhivex-dev: maintainer-not-full-name TJ
W: libhivex-dev: wrong-section-according-to-package-name libhivex-dev
= libdevel
W: libhivex: package-name-doesnt-match-sonames libhivex0
W: libhivex: new-package-should-close-itp-bug
W: libhivex: maintainer-not-full-name TJ
W: libhivex: non-dev-pkg-with-shlib-symlink usr/lib/libhivex.so.0.0.0
usr/lib/libhivex.so
I: libhivex: no-symbols-control-file usr/lib/libhivex.so.0.0.0
W: libhivex-ocaml: new-package-should-close-itp-bug
W: libhivex-ocaml: maintainer-not-full-name TJ
P: libhivex-ocaml: ocaml-dev-file-in-nondev-package 3 files in /usr/lib/ocaml
W: hivex: new-package-should-close-itp-bug
W: hivex: maintainer-not-full-name TJ
I: hivex: spelling-error-in-manpage
usr/share/man/man1/hivexregedit.1.gz reencode re-encode
I: hivex: spelling-error-in-manpage
usr/share/man/man1/hivexregedit.1.gz reencode re-encode
E: libhivex-perl: binary-or-shlib-defines-rpath
./usr/lib/perl/5.10.1/auto/Win/Hivex/Hivex.so
/tmp/buildd/hivex-1.2.1/perl/../lib/.libs
W: libhivex-perl: new-package-should-close-itp-bug
W: libhivex-perl: maintainer-not-full-name TJ
W: libhivex-perl: wrong-section-according-to-package-name libhivex-perl = perl
E: libhivex-perl: perl-module-in-core-directory usr/lib/perl/5.10.1/
: libhivex-perl: perl-module-in-core-directory usr/lib/perl/5.10.1/Win/
E: libhivex-perl: perl-module-in-core-directory usr/lib/perl/5.10.1/Win/Hivex.pm
E: libhivex-perl: perl-module-in-core-directory usr/lib/perl/5.10.1/Win/Hivex/
E: