javahelper (Was "Re: Bug#441403: Incorrect versioned symlink")

2007-09-10 Thread Paul Cager
Kumar Appaiah wrote:
> Package: libjsch-java
> Version: 0.1.34-1
> Severity: serious
> 
> Hi!
> 
> I just observed that the symlink provided in libjsch-java points to
> the old version, and this causes many problems. Please consider fixing
> it. I am unable to contribute a patch because I am unable to build the
> package now, even on pbuilder, so you may be in foran FTBFS as well.
> 
> For the record:
> [EMAIL PROTECTED] ~] ls -l /usr/share/java/jsch*
> -rw-r--r-- 1 root root 165603 2007-09-03 18:11 /usr/share/java/jsch-0.1.34.jar
> lrwxrwxrwx 1 root root 15 2007-09-09 19:06 /usr/share/java/jsch.jar -> 
> jsch-0.1.28.jar

That reminds me...   There was some discussion a little while ago about
proposed new debhelper-style tools, specifically for Java builds. It
seems a dh_installjar would have helped here. Need more hours in the day...


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



RFC: docbook-xsl-saxon (Java extensions for use with DocBook XML stylesheets (Saxon))

2007-09-10 Thread Daniel Leidert
x-post to debian-java, debian-mentors and pkg-java-maintainers

Hi,

I'm building docbook-xsl-saxon, a Java package, that provides
docbook-xsl related extensions. For those interested in the packaging
files, see
http://svn.debian.org/wsvn/debian-xml-sgml/packages/docbook-xsl-saxon/trunk/debian/?rev=0&sc=0

I receive these informational objects from lintian:

I: docbook-xsl-saxon source: build-depends-without-arch-dep ant
I: docbook-xsl-saxon source: build-depends-without-arch-dep
java-gcj-compat-dev

Now I'm unsure, if lintian is right here. The clean target is defined in
an ant makefile (build.xml). So ant and java are both used in the clean
target. To my understanding of Build-Depends and Build-Depends-Indep, I
have to list at least ant in Build-Depends, not in Build-Depends-Indep.
I'm not sure about java-gcj-compat-dev, because java-gcj-compat provides
the java binary.

The package builds fine with kaffe and gcj-java-compat-dev. BTW: Do both
use ecj to compile the source? If yes, where is the difference, if I use
gcj-java-compat-dev or kaffe as build-dependency? I'm sorry for the
questions, but this is my first Java package and I'm trying to learn
more about Java packaging for Debian.

Please split answers and send them to the "right" list if you want. I'm
subscribed to all 3 lists, this posting is sent to.

Regards, Daniel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: javahelper (Was "Re: Bug#441403: Incorrect versioned symlink")

2007-09-10 Thread Michael Koch
On Mon, Sep 10, 2007 at 11:06:20PM +0100, Paul Cager wrote:
> Kumar Appaiah wrote:
> > Package: libjsch-java
> > Version: 0.1.34-1
> > Severity: serious
> > 
> > Hi!
> > 
> > I just observed that the symlink provided in libjsch-java points to
> > the old version, and this causes many problems. Please consider fixing
> > it. I am unable to contribute a patch because I am unable to build the
> > package now, even on pbuilder, so you may be in foran FTBFS as well.
> > 
> > For the record:
> > [EMAIL PROTECTED] ~] ls -l /usr/share/java/jsch*
> > -rw-r--r-- 1 root root 165603 2007-09-03 18:11 
> > /usr/share/java/jsch-0.1.34.jar
> > lrwxrwxrwx 1 root root 15 2007-09-09 19:06 /usr/share/java/jsch.jar -> 
> > jsch-0.1.28.jar
> 
> That reminds me...   There was some discussion a little while ago about
> proposed new debhelper-style tools, specifically for Java builds. It
> seems a dh_installjar would have helped here. Need more hours in the day...

In this case it wouldnt have helped. The old jsch package contained a
file debian/libsch-java.links with a hardcoded link. I removed that
file, tested package and all worked. Then I did an svn up (which made
the file reappear), did the final build and uploaded.

I agree that a helper like dh_installjar would be really nice.


Cheers,
Michael


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]