Re: RFS: libnanoxml2-java
Everything looks good now, and I'd be happy to upload, _but_: you now have: Suggests: nanoxml2-java-doc whereas you actually want: Suggests: libnanoxml2-java-doc Fixed and uploaded to mentors. Thank you for your help. Sveinung -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: libnanoxml2-java
Hello! Thank you for your feedback. I've had a look at this and it looks pretty good, except you have: Suggests: nanoxml2-doc but the package name is libnanoxml2-java-doc. Fixed. By the way, should the copyright text from dh_helper be included in debian/rules like it is now? (Lintian did not warn me about it so I assumed it was OK) A few potentian issues: - Is it safe to do as I have done in debian/origCleaner.sh (using one more parameter than uscan passes to tell set the tempdir from get-orgi-source) or do I risk that uscan adds parameters without notice? (If adding is the only risk I could pass the tempdir by the second parameter instead and make it ignore it if it is the one uscan sends) - the pdf's in the orig.tar.gz violates debian policy (they could be generated), or? (I am sorry. I had forgotten about them) Sveinung -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: libnanoxml2-java
- Is it safe to do as I have done in debian/origCleaner.sh (using one more parameter than uscan passes to tell set the tempdir from get-orgi-source) or do I risk that uscan adds parameters without notice? (If adding is the only risk I could pass the tempdir by the second parameter instead and make it ignore it if it is the one uscan sends) Hmm, not sure. I think it's fine, given you'll update it if it breaks uscan. It's not used in the real build process, so there's no real problem with it breaking. OK. Then I'll wait. - the pdf's in the orig.tar.gz violates debian policy (they could be generated), or? (I am sorry. I had forgotten about them) You could strip them out with the jar. Since you are repacking the tarball anyway, that's worth doing. Agreed. The generated files (pdf, html and gif) are gone in this upload. If you are installing them (which seems a good idea?) then you certainly need to build them from source, but the latex files seem to be there. The reason I did not install them is that the original source for an image in the documentation for NanoXML-Java is a graffle file. I was not able to find any free tool to build it. I could of course include only the documentation for NanoXML-Lite or modify the documentation for NanoXML-Java to not include the image if that is wanted. Sveinung -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RFS: libnanoxml2-java
Hello! I am looking for a sponsor for my package libnanoxml2-java, a small XML parser for Java. * Package name: libnanoxml2-java Version : 2.2.3.dfsg-4 Upstream Author : Marc De Scheemaecker * URL : http://nanoxml.cyberelf.be/ * License : zlib Section : libs It builds these binary packages: libnanoxml2-java - small XML parser for Java libnanoxml2-java-doc - documentation for libnanoxml2-java The package appears to be lintian clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/l/libnanoxml2-java - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/l/libnanoxml2-java/libnanoxml2-java_2.2.3.dfsg-4.dsc I also have some questions: - I read that it was preferred to bump the changelog before each upload to mentors. Will it be possible to shorten it and get it back to 0 before the upload? - This is my first from scratch Debian package. Anything I could improve? I would be glad if someone uploaded this package for me if it is good enough. Kind regards Sveinung Kvilhaugsvik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: libnanoxml2-java
The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/l/libnanoxml2-java - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/l/libnanoxml2-java/libnanoxml2-java_2.2.3.dfsg-4.dsc There seems to be a problem with the source package, I was getting md5sum errors trying to dget that .dsc file. Hmm... Seems like an old version of the orig (I changed get-orig-source) still was there. Fixed. The new upload can be found by running dget http://mentors.debian.net/debian/pool/main/l/libnanoxml2-java/libnanoxml2-java_2.2.3.dfsg-1.dsc I also have some questions: - I read that it was preferred to bump the changelog before each upload to mentors. Will it be possible to shorten it and get it back to 0 before the upload? Well, back to 1, which is the first Debian-revision. It's not critical, but I prefer changelog entries to correspond to Debian uploads. In the new upload I have gone back to 1. (That and the new orig is the only change) - This is my first from scratch Debian package. Anything I could improve? I would be glad if someone uploaded this package for me if it is good enough. If you can check the md5sum package above I'll happily look it over and sponsor. Thank you very much. Sveinung -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Version number in rules
Is there a way to get the Debian version as a variable in the rules file? Is there a standard way to remove the .dsfg from it? -- Helsing Sveinung -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
The copyright statement in rules
Should the copyright statement in debian/rules autogenerated by dh_make be kept, removed or added to? That is this statement: #!/usr/bin/make -f # -*- makefile -*- # Sample debian/rules that uses debhelper. # # This file was originally written by Joey Hess and Craig Small. # As a special exception, when this file is copied by dh-make into a # dh-make output file, you may use that output file without restriction. # This special exception was added by Craig Small in version 0.37 of dh-make. # # Modified to make a template file for a multi-binary package with separated # build-arch and build-indep targets by Bill Allombert 2001 -- Helsing Sveinung -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Examples
When there are two packages, packagename (that contains a library) and packagename-doc (that contains documentation and examples), do the documentation and examples go in /usr/share/doc/package or /usr/share/doc/packagename-doc? If it goes in /usr/share/doc/package, are there a way to make dh_installexamples use /usr/share/doc/package even if the files go in packagename-doc? -- Helsing Sveinung -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Request for comments (before I file a RFS)
NanoXML is a (actually more than one) small XML parser for Java. Provides the Java packages net.n3.nanoxml.*, net.n3.nanoxml.sax.* and nanoxml.* in different jars. I have packaged it since it is a dependency for Knoplerfish (an OSGI implementation that I hope to package for Debian) I have a few questions I hope someone can answer: Should I install the examples? In that case, should they be in doc? Should I run the tests during the build? Some small xml files has no license statement. Does that mean that I remove them? (If you have time to take a look at the package:) Are there things in it that I should improve? Have I made any mistakes? This is the first Debian package I have made from scratch, so I would appreciate the feedback. Is now the time to start looking for a sponsor? The package (everything in a tarball) can be downloaded from http://folk.ntnu.no/kvilhaug/debian/nanoxml.tar.gz Debian-bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478727 Source: libnanoxml-java Binary: libnanoxml-java, libnanoxml-java-doc License: This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: 1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. 2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. 3. This notice may not be removed or altered from any source distribution. -- Sincerly Sveinung Many have imagined republics and principalities which have never been seen or known to exist in reality; for how we live is so far removed from how we ought to live, that he who abandons what is done for what ought to be done, will rather bring about his own ruin than his preservation. (quote Niccolo Machiavelli, The Prince) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
