On Wed, Aug 5, 2009 at 10:45 PM, Jonny Lamb<jo...@debian.org> wrote: > On Wed, Aug 05, 22:31:08 +0530, Onkar Shinde wrote: >> 1. Remove dfsg from version. > > As long as the upstream tarball which is uploaded does not contain any > non-DFSG files, sure. Perhaps it's just the CVS snapshot with these > weird files which I removed. > >> 2. Use upstream source zip for version 1.5.2 instead of retrieving >> files from CVS. > > Sure. > > Thanks for looking into this,
It seems that I spoke too early without checking all the facts. My apologies. The upstream source zip file contains only java source code and it does not contain source for native libraries (.cpp files). So it is a must that the source be retrieved from CVS. And we need to remove unzipsfx binary when creating the tar. Hence the dfsg in version stays. I have done following improvements to the packaging bits. 1. Instead of getting latest version from CVS, I am getting files by a release tag. This makes sure that no matter when the files are checked out they will correspond to a particular release. The release tag is calculated from version in changelog. I found the list of possible tags from upstream website. 2. I am using cvs export instead of cvs chekout in get-orig-source target. Not a major change, it just doesn't require any user interaction. 3. I have done some other changes in control file to adjust build and runtime dependencies appropriately. All the changes I did are checked in pkg-java svn. Unfortunately I could not actually build the package in pbuilder as there was some problem with aptitude getting upgraded/installed on powerpc. I tested the changes in Ubuntu karmic pbuilder though and it builds fine. Please take a look at the changes in svn and let me know what you think. Cheers, Onkar -- To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
