d for upgrading to 7 will be reduced.
Best regards
Ben
On Fri, 2016-12-16 at 00:53 +0100, Emmanuel Bourg wrote:
> Le 14/12/2016 à 20:03, Benjamin Mesing a écrit :
>
> > Any further thoughts?
>
> Thank you for checking the reverse dependencies. The update looks
> rather
* zookeeper
pass
Debian Java Maintainers
Any further thoughts?
Best regards
Ben
On Sun, 2016-12-11 at 18:54 +0100, Emmanuel Bourg wrote:
> Le 11/12/2016 à 15:45, Benjamin Mesing a écrit :
>
> > I now see several opt
Hi,
I have prepared a javacc 6.1.3 package and recompiled some of its
dependencies.
So far three packages fail to compile (there are probably more):
* css-parser
* lucene-solr
* lucene2
All three packages are a couple of years behind the latest upstream
version.
Is there an easy way to autobui
Hi,
mh_make is not supposed to use the jar files in the subdirectories of
your project. If your project depends on additional jar files, those
need to be provided by other packages. A lot of them are already
packaged, but you need to install those, before running mh_make. If
there are unpackaged d
Hi Emmanuel,
today I've made another attempt to update libjavaparser-java
(http://javaparser.org/) which is a prerequisite for updating umlet.
However, the latest version of libjavaparser-java fails with javacc 5.0
(available in Debian and used by mvn-debian) while it compiles fine
with javacc
Hi Andreas,
> > [WARNING] The POM for org.apache.maven.plugins:maven-install-
> > plugin:jar:2.5.2 is missing, no dependency information
> > available
> > and later on
> > [ERROR] Plugin org.apache.maven.plugins:maven-install-plugin:2.5.2
> > or one of its dependencies could not be
Hi Andreas,
ok, so oss-parent seems to be not in Debian (it is here: https://repo1
.maven.org/maven2/org/sonatype/oss/oss-parent/7/oss-parent-7.pom).
If it really is required, it need to be packaged.
I tried to remove the parent entry from generator/pom, and build
without it. Maybe oss-parent is
Hi,
I have downloaded and tried to build libnetlib-java
When trying to build I get the error:
make -f debian/rules binary
dh binary --buildsystem=maven --with javahelper
dh_testdir -O--buildsystem=maven
dh_update_autotools_config -O--buildsystem=maven
dh_auto_configu
Package: wnpp
Severity: normal
I request an adopter for the javaparser package.
The new upstream version of javaparser has a whole bunch of maven
dependencies. A lot of them are not yet packaged. Since I am lacking
the time and are not particularly skilled with maven, I will not be able
to pack
Hi all,
I am in the process of upgrading UMLet. UMLet has a non-versioned
dependency on libjavaparser-java. The new version of UMLet requires a
new version of libjavaparser-java which comes with some incompatible
changes (e.g. the naming of the packages has changed). There is only a
single rdepend
Hi,
I have the following situation:
* Upstream package (umlet) contains a manifest file
* I need to base my manifest on upstreams manifest file (there are
some properties inside, which are required by the application)
* I want to override some properties of the manifest
Hi,
I am no expert but I believe it is like this:
both are variables filled during packaging build and replaced when
creating the package. IIRC the content is stored in special files within
your build directory.
{misc:Depends} is filled by some debhelper/javahelper scripts with
things needed for
will actually not look much
more complicated then without maven.
Best regards
Ben
On Sun, 2013-09-22 at 00:00 +0200, Emmanuel Bourg wrote:
> Le 21/09/2013 10:58, Benjamin Mesing a écrit :
>
> > When packaging the new version I intend to remove the maven parts,
>
-21 at 10:58 +0200, Benjamin Mesing wrote:
> [resent to debian-java since it seems not to have reached
> pkg-java-maintainers@l.a.d.o]
>
> Hello,
>
> currently the package rsyntaxtextarea is maintained by Vladimir Kotov
> and Debian Java Maintainers. The package is in good sha
[resent to debian-java since it seems not to have reached
pkg-java-maintainers@l.a.d.o]
Hello,
currently the package rsyntaxtextarea is maintained by Vladimir Kotov
and Debian Java Maintainers. The package is in good shape but has not
seen any updates to a recent upstream version for two years. I
After updating libc, setting LD_PRELOAD worked without producing any
error messages. However, syslog showed nothing suspicious. Btw. the bug
in gzip you mentioned is now fixed.
I've reported a bug against jarwrapper (#634089) and will build the
package with a startup script instead.
Thanks for yo
Thanks Paul.
On Thu, 2011-07-14 at 23:36 +0200, Paul Wise wrote:
> This sounds a bit like bug #627121 against gzip, caused by the glibc
> memcpy stuff
>
> Try setting this environment variable:
>
> export LD_PRELOAD=/usr/lib/*/libc/memcpy-syslog-preload.so
After setting
export
LD_PRE
Hi,
I am packaging a java application (umlet). I've put the created jar file
into "/usr/share/java/umlet.jar" chmoded it to being executable (using
jh_exec) and added a symlink to it at /usr/bin/umlet.
The package depends on javawrapper.
Now when I try to run the application (either throuh "umlet
Hi,
> I want to make lintian happier but i've got the following warning:
> * W wrong-section-according-to-package-name
> o libzemberek-java => java
You usually get a more descriptive explanation by running
"lintian -i" on you package.
It seems the policies section list is not up to date. Ho
On Tue, 2007-10-09 at 06:48 +0200, Michael Koch wrote:
> On Sun, Sep 30, 2007 at 08:18:24AM +0200, Benjamin Mesing wrote:
> > > > I have tried:
> > > > * compile on Java 6 and run on Java 6 -> fails
> > > > * compile on Java 5 and run on Java
[Sorry for the late reply, I've missed you post]
Hello Michael
> I tried the application with current gij-4.3 and jamvm. Both worked fine
> for me. Can you please try to reproduce?
I was able to reproduce problems with bot jamvm and gij-4.3. With jamvm
I keep getting the "division by zero" excep
Hello,
On Fri, 2008-06-13 at 21:08 +0100, Matthew Johnson wrote:
> On Fri Jun 13 19:52, Yann Rouillard wrote:
> > > 4) There are many other jars in the tarball, and these should be removed
> > > as well (even though you have included their copyrights/licenses in
> > > debian/copyright). Generall
Hello
> It should not matter with which compiler you build your application as
> the bug is in the Swing implementation in GCJ.
>
> Can you debug this with gdb and track down which value is zero? Or at
> least provide a simple testcase that reproduces this?
I am not quite sure, how I could debug
Hello,
I have an application which throws loads of / by zero exceptions (see
below) when run with gij, and the ui looks almost empty. When run with
Sun java it works fine.
I've compiled it with both, sun java and ecj both leading to the same
result.
Help would be appreciated.
Best regards
Ben
Hello
On Sun, 2008-05-11 at 13:27 +0200, Eric Lavarde wrote:
> Hi,
>
> browsing through the repositories to check some Java stuff, I find quite
> some confusion around virtual packages:
I would also like to have this spelled out somewhere. Though policy's
requirement, for virtual packages to a
Hello,
my package (umlet - not yet in archive) does not build with gcj due to
using com.sun.tools.javac.Main. Therefore I am build-depending on
sun-java6-jdk.
However, I can't get an automatic build in a clean environment working,
because sun-java6-jdk does not install in a non-interactive enviro
On Thu, 2007-12-06 at 15:37 +0200, Anton Chernev wrote:
> Most of the X11 packages that the JDK wants to install are
> recommendations. You can use aptitude to find out which are required
> and
> deselect everything else (at least this is what I did).
Or simply use "aptitude -R ".
Regards Ben
> > I have tried:
> > * compile on Java 6 and run on Java 6 -> fails
> > * compile on Java 5 and run on Java 6 -> fails
> > * compile on Java 5 and run on Java 5 -> good
> >
> > Is there a solution for this problem? (I haven't tried adding xalan.jar
> > and serializer.jar to the
Hello,
it seems that xerces is not compatible with Java 6.
When using Java 6 I get the following exception:
Exception in thread "AWT-EventQueue-0" java.lang.AbstractMethodError:
org.apache.xerces.dom.DocumentImpl.getXmlStandalone()Z
at
com.sun.org.apache.xalan.internal.
On Tue, 2007-09-04 at 20:00 +0200, Florian Weimer wrote:
> * Benjamin Mesing:
>
> > I am packaging UMLet and it compiles fine with Sun Java 5. However,
> > starting from Sun Java 6 it complains that "package com.sun.tools.javac
> > does not exist".
>
>
Hello,
is there any Debian package that provides the Java package
"com.sun.tools.javac"?
I am packaging UMLet and it compiles fine with Sun Java 5. However,
starting from Sun Java 6 it complains that "package com.sun.tools.javac
does not exist".
Any help would be appreciated.
Regards Ben
--
[Please CC, I am not subscribed]
> > >>> How do I ensure, that the correct compiler is used.
> > >>> Is the only way, to explicitly set the java
> > >>> compiler path (i.e. /usr/lib/jvm/java-1.5.0/bin/javac
> >
> > >> Yes, that is the only correct way. We must be sure that the package
> > >> bui
[Please CC, I am not subscribed]
>>> How do I ensure, that the correct compiler is used.
>>> Is the only way, to explicitly set the java
>>> compiler path (i.e. /usr/lib/jvm/java-1.5.0/bin/javac
>> Yes, that is the only correct way. We must be sure that the package
>> builds with identical result
[Please CC, I am not subscribed]
Hello,
I want to build a package which requires Java 5. Therefore I
build-depend on (sun-java5-jdk | sun-java6-jdk). How do I ensure, that
the correct compiler is used. E.g. if a free java compiler is
installed, /usr/bin/javac might point to the free compiler whi
Hello,
> > They can be removed to use less space and be sure not to include code
> > that has been build with non free dependencies.
>
> The space argument is rather weak IMHO, and certainly shouldn't warrant
> rebuilding a source tarball only for that purpose. (Or do you have a source
> for th
[Please CC I am not subscribed]
Hello,
> It's preferable to leave the package contents exactly as upstream, and just
> repackage into a tarball. In that case you don't need to tag the orig
> filename.
Generally speaking yes, but the Debian Java Policy suggests, that class
files should be removed
[Please CC, I am not subscribed]
Hello,
I have an upstream release umlet.zip with the given content:
umlet.zip
+- com.umlet.plugin
+-
+- umlet.jar
+ <.class file hierarchy>
+ src
+ <.java file hierarchy>
(i.e. u
[Why is it, that nobody honors my request for CC?]
Thanks for the answers. I would definitely recommend to create a
java5.0-compiler and java5.0-runtime package.
I will use the dependency on sun-java5 for now and put it in contrib.
Regards Ben
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
w
[please CC I am not subscribed]
Hello,
I intent to package UMLet [1,2] which is a neat little UML editor.
However it requires Java 5.0 and I haven't found any information if
there is a 5.0 compatible free java compiler available. Also, how would
I specify a dependency on Java 5.0?
Looking at the
39 matches
Mail list logo