* Emmanuel Bourg:
> Do you think elasticsearch should be removed from unstable?
Not necessarily. It should just not become part of stretch because there
is no sensible way to support it.
BTW: Apparently I was wrong about the 1.7.x branch no longer being
supported by the upstream project: A tag
control: severity -1 serious
control: retitle -1 Elasticsearch should not be part of a Debian release
At this point, there is no point in releasing with an elasticsearch
package.
There is no indication of a change in upstream security policy. In a
misguided attempt to slow down attackers, the
* Emmanuel Bourg:
> Hi Logan,
>
> If you need Elasticsearch on Debian/Ubuntu your best bet for now is to
> install the upstream package available on the download page [1]. The
> elasticsearch package maintained by Debian isn't ready for prime time
> yet and will probably not be part of the
control: retitle -1 re-assess possibility of security support before stretch
freeze
control: severity -1 important
We'll keep Elasticsearch in testing for the time being, but before the
stretch release a re-evaluation of our being able to provide security
support is needed. (With the 2.0 release
* Emmanuel Bourg:
As you want, it up to you if you want to use the modified package
immediately or in 5 days.
Done.
Right. I wrote NMU out of a habit -- the actual changelog is no NMU.
Good, could you just commit the changes on alioth please?
I could do that, but unfortunately the
* Emmanuel Bourg:
Thank you for the fix, it looks good to me.
Should I reschedule?
No need to upload an NMU though since you are a member of the Java
team,
Right. I wrote NMU out of a habit -- the actual changelog is no NMU.
-Hilko
__
This is the maintainer address of Debian's Java team
:13.0 +0200
+++ apache-log4j1.2-1.2.17/debian/changelog 2015-07-07 00:47:09.0 +0200
@@ -1,3 +1,10 @@
+apache-log4j1.2 (1.2.17-6) unstable; urgency=medium
+
+ * Team upload.
+ * Add missing .class files to .jar (Closes: #791446)
+
+ -- Hilko Bengen ben...@debian.org Tue, 07 Jul 2015 00
Control: tag -1 patch
* Hilko Bengen:
All of the missing classes are in the org/apache/log4j/pattern directory
which is missing from the jar that ships with this package.
Apparently the build.xml file that is used to build the jar has not been
kept up-to-date. The patch below seems to fix
Package: liblog4j1.2-java
Version: 1.2.17-5
Severity: grave
I am trying to build apache-log4j-extras1.2 (a dependency for
Elasticsearch 1.6) and am failing because a number of symbols cannot be
resolved, see below. It turns out that those classes are present in the
jar file -- and also in the
* Salvatore Bonaccorso:
Did you had a chance to get more details on it?
,[ http://seclists.org/bugtraq/2015/Jun/53 ]
| Elasticsearch versions 1.0.0 - 1.5.2 are vulnerable to an engineered
| attack on other applications on the system. The snapshot API may be used
| indirectly to place
Control: tags -1 moreinfo
* Salvatore Bonaccorso:
Source: elasticsearch
Version: 1.0.3+dfsg-5
Severity: grave
Tags: security upstream fixed-upstream
Where exactly has it been fixed upstream? A git coommit id would be
helpful.
Cheers,
-Hilko
__
This is the maintainer address of Debian's
* Emmanuel Bourg:
libguava-java has been updated to the version 18, elasticsearch can
now depend on it instead of libguava18-java.
Are you fucking kidding me?
__
This is the maintainer address of Debian's Java team
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers.
* Emmanuel Bourg:
t-digest is a fairly small library, did you consider porting
Elasticsearch to the new version instead of reverting to the previous
version? This looks like an easy modification, and upstream will
certainly be interested in such a change.
No, I did not. And I will not
* Emmanuel Bourg:
I got a look at Elasticsearch, and this is just a one line change:
state.centroidCount() becomes state.centroids().size() in
TDigestState.java. I wouldn't call that a severe incompatibility.
Please don't just look at Elasticsearch but at the
japi-compliance-checker report I
Package: libt-digest-java
Version: 3.0-1
Severity: grave
Elasticsearch 1.4.5 cannot be built with libt-digest-java/3.1-1 installed.
Reverting back to 3.0-1 resolves this problem.
The attached report generated by japi-compliance-checker shows that the
3.1 is backwards incompatible. The package
* Emmanuel Bourg:
Package: liblucene4-java
Version: 1:4.6.1+dfsg-2
Severity: serious
The liblucene4-java package installs dummy pom.xml files in
/usr/share/maven-repo
which are missing important information to be usable by other packages.
Emmanuel,
thank you for finding and reporting
* Emmanuel Bourg:
Source: lucene4
Version: 1:4.6.1+dfsg-2
Severity: serious
The lucene4 package contains several pre-generated Java files created by
JavaCC.
These files should be at least regenerated during the build and maybe removed
from the upstream tarball like the lucene-solr
control: tag -1 pending
* Emmanuel Bourg:
The Maven artifact is bundled in the elasticsearch package, it would be
preferable to package it separately in a libelasticsearch-java package
such that elasticsearch plugins can be built without installing the server.
I have created a todo branch in
* Philipp Hug:
I suspect you did also run into the following problem, which is related:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768178
Uh-oh, this is bad. I strongly suspect that elasticsearch is not the
only package that has this issue.
systemd's behavior is interesting, I suspect
* Timo Aaltonen:
This sounds more like a dupe of #722665 where the fault is that
libjackson-json-java never should've had the symlink called
jackson-core-java...
Which package should provide the versionless .jar file?
Is the versionless .jar file needed at all?
Was any of
Given that jackson-core has undergone breaking API changes between 1.9.x
and 2.4.x, there probably should not be a versionless jackson-core.jar
as part of libjackson2-core-jar.
Cheers,
-Hilko
__
This is the maintainer address of Debian's Java team
* Jamie Norrish:
$ sudo -u elasticsearch bash -x
/usr/share/elasticsearch/bin/elasticsearch.
Could you please try if upgrading to version 1.0.3+dfsg-5 (which I just
uploaded to unstable) fixes this problem?
The above command now runs elasticsearch properly.
So far so good...
It
* Jamie Norrish:
It doesn't appear that /etc/init.d/elasticsearch works, however.
What init system do you have? SysV? systemd?
systemd. Sorry for not specifying that before.
I ended up with systemd at some point, too. And I still have no idea how
to debug daemon startup problems. :-(
#
* Jamie Norrish:
I am also experiencing this problem, with the IOException trying to
write to /usr/share/elasticsearch/data/elasticsearch/nodes/49 when
running:
$ sudo -u elasticsearch bash -x /usr/share/elasticsearch/bin/elasticsearch.
Could you please try if upgrading to version
Package: src:lucene4
Version: 4.10.1+dfsg-1
Severity: grave
While working on fixing some issues in elasticsearch 1.0.3, I noticed
that it can no longer be built using Lucene 4.10.1 -- because of API/ABI
incompatibilities. lucene4-4.6.1+dfsg-1 which is currently in jessie
should *not* be replaced.
Package: elasticsearch
Version: 1.0.3+dfsg-4
Severity: grave
$ /usr/share/elasticsearch/bin/plugin
Error: Could not find or load main class org.elasticsearch.plugins.PluginManager
This happens because we forgot to adjust the classpath in the script.
-Hilko
__
This is the maintainer address of
* Gillu:
We never shipped 0.90.7 within Debian -- am I assuming correctly that
you used the .deb files provided by upstream?
Yes, this is very likely. I must have forgot this, apologies for not
mentioning it before. This must be it.
No worries. :-)
What output do you get when you run
* K. Gilden:
I upgraded my system on 10/18 and from that point onwards elasticsearch
(0.90.7
- 1.0.3+dfsg-3) doesn't start when invoking service elasticsearch start.
Running /usr/share/elasticsearch/bin/elasticsearch starts up the server just
fine.
We never shipped 0.90.7 within Debian --
Package: maven-debian-helper
Version: 1.6.8
Severity: important
Hi,
I'm trying to build libspatial4j-0.4-java, a Maven based project, but
for ABI incompatibility reasons I do NOT want the spatial4j-0.4.1.jar -
spatial4j.jar symlink in /usr/share/java.
From reading the comments in the generated
Source: elasticsearch
Severity: wishlist
The current version of elasticsearch in Debian/unstable is 1.0.3,
upstream is at 1.3.4. It can't be packaged without some extra
dependencies which will be tracked using this bug.
__
This is the maintainer address of Debian's Java team
Control: block -1 by 765444
Control: block -1 by 765317
elasticsearch 1.3.4 needs t-digest
__
This is the maintainer address of Debian's Java team
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers.
Please use
debian-j...@lists.debian.org for discussions and questions.
* Potter, Tim (Cloud Services):
Thanks for helping out with this bug. If you could attach your patch
(the debdiff tool can be helpful here) to the bug report, either Hilko
or I (or any DD) can rebuild and upload.
Attached. I didn't know about debdiff - what a great tool!
Thank you. I am
A git repository of the new package is available for review at
http://anonscm.debian.org/gitweb/?p=users/bengen/simple-xml.git.
Cheers,
-Hilko
__
This is the maintainer address of Debian's Java team
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers.
Please use
Control: block 736852 by -1
Source: simple-xml
Version: 2.3.2-1
Severity: wishlist
Something newer than 2.3.2-1 is is needed for building
carrotsearch-randomizedtesting. Version 2.7.1 is available.
__
This is the maintainer address of Debian's Java team
Control: tag -1 patch
I have prepared a new package for 2.7.1-1. It builds fine using sbuild.
Here's the .diff.gz.
Please review.
Cheers,
-Hilko
simple-xml_2.7.1-1.diff.gz
Description: Binary data
__
This is the maintainer address of Debian's Java team
Source: sisu-guice
Version: 3.1.1-1
Severity: grave
The binary files below are contained in the source tarball, but no
source is provided. Luckily, the package can still be built
Cheers,
-Hilko
sisu-guice-3.1.1 $ find -name \*.jar | xargs du -sch
504K./extensions/struts2/lib/jsp-api-2.1.jar
* Hilko Bengen:
The binary files below are contained in the source tarball, but no
source is provided. Luckily, the package can still be built
... after the files have been removed, I meant to say.
Cheers,
-Hilko
__
This is the maintainer address of Debian's Java team
http
Package: java-wrappers
Version: 0.1.25
Severity: important
Tags: patch
Dear Maintainer,
The run_jar() function in /usr/lib/java-wrappers/java-wrappers.sh
contains the following lines:
if locate_jar $1; then
shift
run_java -jar $@
else
java_fail Unable to find jar
Package: maven-debian-helper
Version: 1.5.1
Severity: normal
The package's description consists almost exclusively about what Apache
Maven is -- copied from http://maven.apache.org/what-is-maven.html.
The only sentence relevant to its contents is: This package makes it
possible to use Maven for
Package: maven-repo-helper
Version: 1.7.1
Severity: normal
The package's description consists almost exclusively about what Apache
Maven is -- copied from http://maven.apache.org/what-is-maven.html.
This is unneeded. If the user is interested in what Maven is, he can
still look at that pacakge's
Package: maven-debian-helper
Version: 1.5.1
Severity: normal
Quoting from the comments at the top of /usr/bin/mvn-debian itself, it
is an example script and [p]roduction use is not supported by the
maintainer of maven-debian-helper. It may make some sense to provide
such a script as an example in
jh_makepkg altogether; see my
patch below.
Cheers,
-Hilko
commit 70ce2c9b74292543625eec6a52bf7d4d1d0af0a9 (HEAD, refs/heads/master)
Author: Hilko Bengen ben...@debian.org
Date: Mon Mar 18 22:58:26 2013 +0100
Remove Maven support
Modified jh_makepkg
diff --git a/jh_makepkg b/jh_makepkg
index
is attached below.
Cheers,
-Hilko
commit 438d51ab5e90f2ec8e961785e19f11352542a0a7 (HEAD, refs/heads/master)
Author: Hilko Bengen ben...@debian.org
Date: Tue Mar 19 00:48:48 2013 +0100
mh_make: Don't use sudo to install extra packages -- bail out using error messages instead.
Modified
tag 619140 +moreinfo
thank you
So freemind asks for converting old config file format and asks for
converting my last opened mindmap but then does not start at all.
Uh, this is bad. :-(
Is the bug reproducable using only the old config file and without the
contents of the last opened mindmap?
44 matches
Mail list logo
