I have uploaded the corrected package to close this RC bug.

Matthias:

In the future, if you have the package and need sponsoring, in order to
close an RC bug, it's a good idea to:
        * Include the URL of the package that needs sponsoring in your
          messages (It took me a lot of googling to find it).
        * If your sponsor does not reply in a week or so, use debian-mentors
          list to seek someone else who would sponsor the package.
        * If you still don't find a sponsor, you might need to ask
          debian-release to help you out.

Letting a RC bug sit in the BTS unsolved because your usual sponsor is busy
with something else is really not a good thing.

On a different matter, I decided to upload the package because it did
indeed close an RC bug that had been open for quite a long time.  In
another situation, I would not have uploaded this package, because it
includes a number of packaging errors.

It is not lintian nor linda clean.  Both give errors about the library
soname.

Also, you are copying "config.sub" and "config.guess", but the package's
configure script is not even reading those files, because it looks for them
in the build_tools dir.  So, either you remove those lines from your
debian/rules, or you copy the files to the correct location.

Also, I noticed the lintian overrides about the CVS dir.  Have you talked
with upstream about this?

You should always try to keep your packages lintian and linda clean.  The
warnings are there for a reason.

-- 
 Besitos,   {o_
     Marga. (')_

Attachment: signature.asc
Description: Digital signature

Reply via email to