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

Bug#883611:



Paolo Gigante kirjoitti 06.12.2017 klo 20:53:

Hi Juhani,

Thanks for your feedback in your previous comment. I have now updated the package with the requested changes. I understand that you may not be able to sponsor this package however I would appreciate any additional advise you can offer.

https://mentors.debian.net/package/auter

Did you notice (at https://mentors.debian.net/package/auter):

Package closes bugs in a wrong way
Errors:
    Bug #883611 does not belong to this package
    sponsorship-requests:
        #883611 (wishlist): RFS: auter/0.11 (ITP: Bug#880600)

Even though that message isn't too helpful, it is correct. One should close the ITP bug and not the RFS in the changelog of a new package.
https://lintian.debian.org/tags/new-package-should-close-itp-bug.html

The orig.tar.gz is not a real original tarball. It has generated files such as docs/auter.1 and lacks many files that are found in the github repository, e.g. Makefile, README.md, HACKING.md, LICENSE, and so on. It is not available for download, either.

Instead of that, please use a tarball that's available to download from
https://github.com/rackerlabs/auter/releases or
https://github.com/rackerlabs/auter/tags where your debian/watch points to. If you package something you call 0.11-1, its orig tarball should really be the same one that upstream calls 0.11.
https://wiki.debian.org/UpstreamGuide

There is code in the Makefile to extract the Standards-Version from lintian's files. That's not really correct or even useful, since the meaning of Standards-Version in debian/control is "the last version of Debian Policy against which this package was checked". It should only be updated after ensuring compliance (there's upgrading checklist to help). Having an out-of-date Standards-Version will have no effect on the built package whatsoever.
https://www.debian.org/doc/debian-policy/


With best regards,
Juhani


Reply to: