On 14/08/11 17:18, Aron Xu wrote:
No, I don't mean running lintian within pbuilder, but just build the
package in pbuilder. By simply running debuild on your system, there
are many things can influence the build result, for instance the
packages you have installed but not declared in Build-Depends, and the
environment variables you have set but not declared in debian/rules.
While with pbuilder, it makes a clean chroot, which means a minimal
amount of packages installed and a clean/default environment
variables, thus pbuilder can help you test if everything behaves
correctly.
After building your package in pbuilder, you can check the built
packages outside the chroot, lintian does not have the problem to
perform checks.
Thanks, I have now learned more about how pdebuild works. With my earlier
method, I hadn't really checked the pdebuild package. I was actually just
fooling myself, and was rechecking the 'debuild' package. The pdebuild package
actually ends up in /var/cache/pbuilder/result, which I didn't know...
Thanks for your work, but you forgot to add a minimum version
requirement to Build-Depends, that is "python (>= 2.6.6-3~)". This is
documented on the wiki page, please double check.
Done. Thanks.
OK, great. And please be aware that no upstream changelog isn't a
critical issue to get your package into Debian. So you don't need to
wait for a new release before uploading the first version of your
package.
Ok. Upstream seems to have a nice HTML changelog. I know there is Debian
documentation about how to treat this case, so I'll get that done even though it
is not a strict requirement.
Best regards
Torquil Sørensen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
