On Sun, Aug 14, 2011 at 22:54, Torquil Macdonald Sørensen <torq...@gmail.com> wrote: > On 14/08/11 15:46, Aron Xu wrote: >> >> Let me know when you have finished it, :-) >> > > Finished! > > Ok, I think your build problem appeared because "python" was not included as > a Build-Depends. Your build log indicated an error message where the program > "pyversions" was not found. I actually got the same error message in my > pbuilder build log without noticing it before. After including python as a > Build-Depends, I no longer have this problem. >
I don't have it now either, so next time please check the package built from pbuilder before uploading. > You suggested that I should run the lintian command within the chroot. I > have not yet figured out how to do this, but will investigate some man > pages. Even so, I am sufficiently confident that I have fixed the problem to > upload this once more to mentors.debian.net. My apologies if the problem is > still present. > 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. > So now I have included python as a Build-Depends, and I think I have > followed the instructions for converting to dh_python2. In this case it > seems to be as simple as to just obey the recommendations for the > Build-Depends and Depends, as well as to include the option --with python2 > for the dh commands that are run in the rules script. > 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. > I have uploaded a new version (with the same version number). Due to the new > "expo" system on mentors.debian.net I had to first delete the old package, > but the URL should be the same to the *.dsc. At least I get the updated > package when I download it using > > dget > http://mentors.debian.net/debian/pool/main/p/python-visvis/python-visvis_1.5-1.dsc > > Regarding the "P: python-visvis: no-upstream-changelog" lintian message, I > have inquired upstream about how to obtain a suitable changelog. > 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. -- Regards, Aron Xu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
