Hi Ragnar, seems like and interesting project and is well worth to appear in Debian
> So the question is how to improve the packages into a state that they > can go into debian and also how I go forward to have them in debian. you should start under guideness of lintian tool. Just run it on the resultant packages with '-i' to see detailed description of the detected problems Here is output of lintian -i rope_0.8.2-1_i386.changes W: rope source: build-depends-on-1-revision build-depends: python-all-dev (>= 2.5.2-1) N: N: The package declares a build dependency on a version of a package with N: a -1 Debian revision such as "libfoo (>= 1.2-1)". Such a dependency N: will not be satisfied by a backport of libfoo 1.2-1 and therefore N: makes backporting unnecessarily difficult. Normally, the -1 version is N: unneeded and a dependency such as "libfoo (>= 1.2)" would be N: sufficient. If there was an earlier -0.X version of libfoo that would N: not satisfy the dependency, use "libfoo (>= 1.2-1~)" instead. N: W: python-rope: copyright-without-copyright-notice N: N: The copyright file for this package does not appear to contain a N: copyright notice. You should copy the copyright notice from the N: upstream source (or add one of your own for a native package). A N: copyright notice must consist of Copyright, Copr., or the Unicode N: symbol of C in a circle followed by the years and the copyright N: holder. A copyright notice is not required for a work to be N: copyrighted, but Debian requires the copyright file include the N: authors and years of copyright, and including a valid copyright notice N: is the best way to do that. N: N: If the package is in the public domain rather than copyrighted, be N: sure to mention "public domain" in the copyright file. Please be aware N: that this is very rare and not the same as a DFSG-free license. True N: public domain software is generally limited to such special cases as a N: work product of a United States government agency. N: N: Refer to http://ftp-master.debian.org/REJECT-FAQ.html for details. N: W: python-rope: description-synopsis-might-not-be-phrased-properly N: N: The synopsis (first line in the package "Description:" field, the N: short description) ends with a full stop "." character. This is not N: necessary, as the synopsis doesn't need to be a full sentence. It is N: recommended that a descriptive phrase is used instead. N: N: Note also that the synopsis is not part of the rest of the N: "Description:" field. N: N: Refer to Policy Manual, section 3.4.1 for details. N: E: python-rope: description-synopsis-is-duplicated N: N: The first line of the extended Description: should not repeat the N: synopsis exactly. This indicates that either the synopsis is badly N: formed or that the extended description has been wrongly copied and N: pasted. N: N: Refer to Policy Manual, section 3.4.2 for details. N: W: python-rope: spelling-error-in-description python Python N: N: Lintian found a spelling or capitalization error in the package N: description. Lintian has a list of common misspellings that it looks N: for. It does not have a dictionary like a spelling checker does. It is N: particularly picky about spelling and capitalization in package N: descriptions since they're very visible to end users. N: W: python-rope: spelling-error-in-description python Python W: python-rope: new-package-should-close-itp-bug N: N: This package appears to be the first packaging of a new upstream N: software package (there is only one changelog entry and the Debian N: revision is 1), but it does not close any bugs. The initial upload of N: a new package should close the corresponding ITP bug for that package. N: N: This warning can be ignored if the package is not intended for Debian N: or if it is a split of an existing Debian package. N: N: Refer to Developers Reference, section 5.1 for details. N: On Thu, 19 Jun 2008, Ragnar Ouchterlony wrote: > Hi, > Since I have no idea how to really do this, I post here in the hope that > someone will find this useful and help me get these packages into > debian. > I was missing rope ( http://rope.sourceforge.net/ ) and ropemacs > ( http://rope.sourceforge.net/ropemacs.html ) in the debian repository, > so I thought that I should package them instead of just installing them > locally. Note that I do not have any great experience creating debian > packages although I have looked at it before. -- Yaroslav Halchenko Research Assistant, Psychology Department, Rutgers-Newark Student Ph.D. @ CS Dept. NJIT Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171 101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
