I would opt for option 2 or maybe 3.
About option 2, I could split x11vnc into x11vnc and x11vnc-data packages.
x11vnc-data package will contain all jars (/usr/share/x11vnc/classes) and
will
be platform-independent (architecture all).
So when a user installs the x11vnc package then by
yes, x11vnc will have a dependency on x11vnc-data package.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
The options aren't particularly good, but you have some:
1) Create your own keystore that is compatible with this jarsigner,
and use that instead of the included one.
Note that this jarsigning going on here in x11vnc has nothing to
do with security or
On Fri, Dec 04, 2009 at 08:17:01PM -0500, Karl J. Runge wrote:
Does it still fail when using Sun's java/jarsigner?
Sun's java/jarsigner isn't available on the hppa architecture.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
Sun's java/jarsigner isn't available on the hppa architecture.
Oh, I see now.
Looking around I found these implementation files:
http://docjar.org/html/api/gnu/javax/crypto/jce/keyring/GnuKeyring.java.html
http://docjar.org/html/api/gnu/java/security/Registry.java.html
The former
Does it still fail when using Sun's java/jarsigner?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: x11vnc
Version: 0.9.8-2
Severity: important
User: debian-h...@lists.debian.org
Usertags: hppa
x11vnc_0.9.8-2 reliably fails to build on hppa:
https://buildd.debian.org/build.php?pkg=x11vncver=0.9.8-2arch=hppafile=log
From the most recent build log:
[...]
adding: TextViewer$1.class
7 matches
Mail list logo
