On Wed, Aug 24, 2005 at 10:40:38AM -0400, Justin Pryzby wrote: > > > Another detail... you might extend the description (debian/control) > > > of the python2.(3|4)-goopy binary packages to read something like > > > "This package provides the modules for Python 2.4". > > > > Done that as well. > You can probably take advantage of debhelper substitution variables; > since you are making multiple binary packages, and their description > should all be the same, to within the version number. I guess what > you want to look at it /u/s/d/debhelper/PROGRAMMING.gz. I did look after you told me, but I felt nothing too great would result, so I left it as it is. > > As for the Build-Depends-Indep, I checked out the problem myself using > > pbuilder , and added python2.4-dev. Finally, I have eliminated all > > lintian warnings but one; outdated standards version! I think I am > > running the latest dh_make + debhelpers, and from what I gather from > > the lintian info site, this isn't too serious, is it? > Right. You can read /u/s/d/debian-policy/upgrading-checklist.txt.gz > to see if there's anything that needs to get updated in your package > in order to claim "compliance" with a higher version. If not, then > just change the version (in the changelog, the typical entry for this > is "* Bumped standards version"). As per your advice, I have looked through the policy, and find that the changes in policy have not affected my package. So, you've helped me remove the last warning lintian gave me. I have synced my packages with the web server, so please look at it if you want to. Thanks. Kumar -- Kumar Appaiah, 462, Jamuna Hostel, Indian Institute of Technology Madras, Chennai - 600 036
Attachment:
signature.asc
Description: Digital signature