Op di, 12-09-2006 te 23:36 -0700, schreef Ryan Finnie: > On 9/12/06, Carlo Segre <segre@iit.edu> wrote: > > > > I noticed that you first filed the ITP in June. Since then, we have had a > > python transition to 2.4 and there is a new standard for python packaging. > > Th python2.X-package type packages are no longer the norm. You will need > > to convert your package to either python-central or python-support. > > The wiki docs made it rather easy to understand and convert over to a > unified python package, but I need a small clarification. Since my > python package provides only public extensions (no .py modules), I do > not need to reference python-support/python-central, correct? > python-support/python-central are needed only for bytecompilation of > modules? > > Also, since I already uploaded to mentors.debian.net, I will have to > bump the revision from 11.1.0.50-1 to 11.1.0.50-2. -1's changelog > entry is "Initial release (Closes: #376187)" (the ITP), but since -1 > never actually made it to incoming, what is the procedure for making > sure the eventual upload will close the ITP? Should I put "Initial > release (Closes: #376187)" again in the changelog for -2? Remove -1's > changelog entry completely? No, do not modify your earlier changelog. To close the ITP during upload your sponsor can rebuild the package with -v11.1.0.50-0 argument to dpkg-buildpackage. This will make sure your the changelog of -1 and -2 is included it the changes file used during upload. Greetings Arjan
Attachment:
signature.asc
Description: Dit berichtdeel is digitaal ondertekend