jetty8 8.1.18-1 MIGRATED to testing

2015-10-14 Thread Debian testing watch
FYI: The status of the jetty8 source package in Debian's testing distribution has changed. Previous version: 8.1.17-2 Current version: 8.1.18-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will

Bug#801693: jasperreports: Please migrate to groovy 2.x

2015-10-14 Thread Markus Koschany
On Tue, 13 Oct 2015 11:21:02 -0300 Miguel Landaeta wrote: > Package: src:jasperreports > Version: 4.1.3+dfsg-4 > Severity: important > User: pkg-java-maintainers@lists.alioth.debian.org > Usertags: groovy2-transition > > This package FTBFS when groovy 2.x is used. I had a

Bug#798343: libbcprov-java-doc: Package does not contain docs, api folder empty

2015-10-14 Thread Markus Koschany
Am 14.10.2015 um 13:08 schrieb dean: > On 10/11/15 22:27, Markus Koschany wrote: >> On Sun, 11 Oct 2015 12:48:45 +1000 dean > Hi Markus and list, > >> >> I think there is even a simpler way to change the source encoding. In >> Debian we normally use an ant.properties

jedit 5.2.0+dfsg-1 MIGRATED to testing

2015-10-14 Thread Debian testing watch
FYI: The status of the jedit source package in Debian's testing distribution has changed. Previous version: 5.1.0+dfsg-2 Current version: 5.2.0+dfsg-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you

Bug#801320: marked as done (jasperreports: depends on obsolete libasm2-java library)

2015-10-14 Thread Debian Bug Tracking System
Your message dated Wed, 14 Oct 2015 19:26:58 +0200 with message-id <561e9062.4010...@gambaru.de> and subject line Re: jasperreports: depends on obsolete libasm2-java library has caused the Debian Bug report #801320, regarding jasperreports: depends on obsolete libasm2-java library to be marked as

Processed: Re: Bug#766977: elasticsearch not starting

2015-10-14 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 elasticsearch: Please provide a systemd service file Bug #766977 [elasticsearch] elasticsearch not starting Changed Bug title to 'elasticsearch: Please provide a systemd service file' from 'elasticsearch not starting' -- 766977:

Bug#766977: elasticsearch not starting

2015-10-14 Thread John Paul Adrian Glaubitz
Control: retitle -1 elasticsearch: Please provide a systemd service file > However the fact remains, systemd is confusingly reporting ES as > being started when it is not. IMHO, that's an issue. Not an issue here. Without START_DAEMON=true, systemd correctly reports the unit as run successfully