There is still an issue in sid, the deployment no longer works after the
update to jetty8 in solr-jetty/3.6.2+dfsg-4. There are two reasons to this:
1. the symlink to the web app is misplaced (/var/lib/jetty should have
been updated to /var/lib/jetty8)
2. Jetty no longer follows symbolic links
Processing commands for cont...@bugs.debian.org:
tags 752547 + pending
Bug #752547 [solr-jetty] Broken symlink to solr's webapp
Added tag(s) pending.
tags 701876 + pending
Bug #701876 [solr-jetty] solr-jetty: Symlink to jquery in solr admin doesn't
work under jetty
Added tag(s) pending.
End
Processing control commands:
reopen -1
Bug #740596 {Done: Emmanuel Bourg ebo...@apache.org} [solr-jetty]
java.lang.NoClassDefFoundError: org/apache/tomcat/util/descriptor/LocalResolver
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared,
Control: reopen -1
Control: reassign -1 libjetty8-extra-java
Severity: important
Migrating to jetty8 didn't solve this issue, I've been able to reproduce
this error with solr-jetty. tomcat-util.jar is missing from the
/usr/share/jetty8/lib/jsp/ directory.
__
This is the maintainer address of
libparanamer-java_2.7-1_amd64.changes uploaded successfully to localhost
along with the files:
libparanamer-java_2.7-1.dsc
libparanamer-java_2.7.orig.tar.gz
libparanamer-java_2.7-1.debian.tar.xz
libparanamer-java_2.7-1_all.deb
libparanamer-java-doc_2.7-1_all.deb
Greetings,
Your
binary:libparanamer-java is NEW.
binary:libparanamer-java-doc is NEW.
source:libparanamer-java is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are
libpicocontainer-java_2.15-1_amd64.changes uploaded successfully to localhost
along with the files:
libpicocontainer-java_2.15-1.dsc
libpicocontainer-java_2.15.orig.tar.gz
libpicocontainer-java_2.15-1.debian.tar.xz
libpicocontainer-java_2.15-1_all.deb
Today I have received a private e-mail from Flemming and he intends to
relicense the affected files and even considers to change the whole
Robocode license to the GPL. However we will have to wait for the next
release of Robocode, 1.9.2.4, which shall include those changes.
Markus
FYI: The status of the gluegen2 source package
in Debian's testing distribution has changed.
Previous version: 2.2.1-1
Current version: 2.2.4-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will
FYI: The status of the jsoup source package
in Debian's testing distribution has changed.
Previous version: 1.7.3-1
Current version: 1.8.1-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will receive
FYI: The status of the checkstyle source package
in Debian's testing distribution has changed.
Previous version: 5.7-2
Current version: 5.9-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will receive
FYI: The status of the mongo-java-driver source package
in Debian's testing distribution has changed.
Previous version: 2.12.3-1
Current version: 2.12.4-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you
FYI: The status of the libfreemarker-java source package
in Debian's testing distribution has changed.
Previous version: 2.3.20-3
Current version: 2.3.20-4
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day
Package: solr-jetty
Version: 3.6.2+dfsg-4
Severity: serious
The postrm script of solr-jetty checks the existence of
/usr/sbin/dpkg-statoverride, but this path no longer exists since
dpkg/1.17.0. When solr-jetty is removed along jetty8 this brings dpkg in
a state where new installs fail because
Package: solr-jetty
Version: 3.6.2+dfsg-4
Severity: important
Dear Maintainer,
after update from jetty to jetty8, the symlink to the solr webapp is still
created in /var/lib/jetty, although the jetty8 webapps
should be placed to /var/lib/jetty8.
Best regards,
Andreas.
-- System Information:
jetty8_8.1.16-4_amd64.changes uploaded successfully to localhost
along with the files:
jetty8_8.1.16-4.dsc
jetty8_8.1.16-4.debian.tar.xz
libjetty8-java_8.1.16-4_all.deb
libjetty8-java-doc_8.1.16-4_all.deb
libjetty8-extra-java_8.1.16-4_all.deb
jetty8_8.1.16-4_all.deb
Greetings,
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 31 Oct 2014 18:54:25 +0100
Source: jetty8
Binary: libjetty8-java libjetty8-java-doc libjetty8-extra-java jetty8
Architecture: source all
Version: 8.1.16-4
Distribution: unstable
Urgency: medium
Maintainer: Debian
Your message dated Fri, 31 Oct 2014 21:49:30 +
with message-id e1xkk4y-0007o8...@franck.debian.org
and subject line Bug#740596: fixed in jetty8 8.1.16-4
has caused the Debian Bug report #740596,
regarding java.lang.NoClassDefFoundError:
org/apache/tomcat/util/descriptor/LocalResolver
to be
Your message dated Fri, 31 Oct 2014 21:49:30 +
with message-id e1xkk4y-0007oe...@franck.debian.org
and subject line Bug#767337: fixed in jetty8 8.1.16-4
has caused the Debian Bug report #767337,
regarding jetty8: Unable to purge if authbind is not installed
to be marked as done.
This means
Your message dated Fri, 31 Oct 2014 21:49:30 +
with message-id e1xkk4y-0007ok...@franck.debian.org
and subject line Bug#767369: fixed in jetty8 8.1.16-4
has caused the Debian Bug report #767369,
regarding jetty8: enable IPv6 by default
to be marked as done.
This means that you claim that the
lucene-solr_3.6.2+dfsg-5_amd64.changes uploaded successfully to localhost
along with the files:
lucene-solr_3.6.2+dfsg-5.dsc
lucene-solr_3.6.2+dfsg-5.debian.tar.xz
liblucene3-java_3.6.2+dfsg-5_all.deb
liblucene3-contrib-java_3.6.2+dfsg-5_all.deb
liblucene3-java-doc_3.6.2+dfsg-5_all.deb
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Fri, 31 Oct 2014 19:28:25 +0100
Source: lucene-solr
Binary: liblucene3-java liblucene3-contrib-java liblucene3-java-doc
libsolr-java solr-common solr-tomcat solr-jetty
Architecture: source all
Version: 3.6.2+dfsg-5
Your message dated Fri, 31 Oct 2014 22:04:55 +
with message-id e1xkkjt-0001kl...@franck.debian.org
and subject line Bug#767525: fixed in lucene-solr 3.6.2+dfsg-5
has caused the Debian Bug report #767525,
regarding solr-jetty: Symlink to webapp created in /var/lib/jetty, should be
Your message dated Fri, 31 Oct 2014 22:04:55 +
with message-id e1xkkjt-0001kf...@franck.debian.org
and subject line Bug#767519: fixed in lucene-solr 3.6.2+dfsg-5
has caused the Debian Bug report #767519,
regarding solr-jetty: update the path of dpkg-statoverride in the postrm script
to be
Your message dated Fri, 31 Oct 2014 22:04:55 +
with message-id e1xkkjt-0001kt...@franck.debian.org
and subject line Bug#701876: fixed in lucene-solr 3.6.2+dfsg-5
has caused the Debian Bug report #701876,
regarding solr-jetty: Symlink to jquery in solr admin doesn't work under jetty
to be
Your message dated Fri, 31 Oct 2014 22:04:55 +
with message-id e1xkkjt-0001kz...@franck.debian.org
and subject line Bug#752547: fixed in lucene-solr 3.6.2+dfsg-5
has caused the Debian Bug report #752547,
regarding Broken symlink to solr's webapp
to be marked as done.
This means that you claim
Source: jenkins
Severity: important
Tags: security upstream
Hi,
See [1] and [2] for details on CVE-2014-3665.
[1]
https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2014-10-30
[2] https://wiki.jenkins-ci.org/display/JENKINS/Slave+To+Master+Access+Control
Regards,
Markus Koschany wrote:
I think it is a bug because we want jinput to be available on all
supported architectures. However the severity should be normal.
Sure, but I just noticed there's already a bug open about that, #657771
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
__
This is the
Control: severity -1 normal
On Tue, 28 Oct 2014 11:05:11 + Steven Chamberlain ste...@pyro.eu.org
wrote:
Hi,
On 28/10/14 03:16, Michael Gilbert wrote:
This package currently depends on libjinput-jni, which is currently
not build on the kfreebsds (#657771), so the libjinput-java is
Processing control commands:
severity -1 normal
Bug #767051 [libjinput-java] libjinput-java: uninstallable on kfreebsd
Severity set to 'normal' from 'serious'
--
767051: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767051
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: forcemerge 657771 767051
On Fri, 31. Oct 22:36 Steven Chamberlain ste...@pyro.eu.org wrote:
Markus Koschany wrote:
I think it is a bug because we want jinput to be available on all
supported architectures. However the severity should be normal.
Sure, but I just noticed there's
Processing control commands:
forcemerge 657771 767051
Bug #657771 [src:jinput] jinput: FTBFS(!linux):
Unable to merge bugs because:
package of #767051 is 'libjinput-java' not 'src:jinput'
Failed to forcibly merge 657771: Did not alter merged bugs
--
657771:
Processing commands for cont...@bugs.debian.org:
reassign 767051 src:jinput
Bug #767051 [libjinput-java] libjinput-java: uninstallable on kfreebsd
Bug reassigned from package 'libjinput-java' to 'src:jinput'.
No longer marked as found in versions jinput/20100502+dfsg-7.
Ignoring request to alter
33 matches
Mail list logo
