xslthl_2.1.3-3_amd64.changes ACCEPTED into unstable

2017-02-16 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 16 Feb 2017 07:01:26 + Source: xslthl Binary: libxslthl-java Architecture: source all Version: 2.1.3-3 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers

Processing of xslthl_2.1.3-3_amd64.changes

2017-02-16 Thread Debian FTP Masters
xslthl_2.1.3-3_amd64.changes uploaded successfully to localhost along with the files: xslthl_2.1.3-3.dsc xslthl_2.1.3-3.debian.tar.xz libxslthl-java_2.1.3-3_all.deb xslthl_2.1.3-3_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) __ This is

Bug#855324: pdfsam fails to start

2017-02-16 Thread Markus Koschany
On 17.02.2017 00:46, Philip Rinn wrote: > On 16.02.2017 at 23:18, Markus Koschany wrote: > [...] > >> thank you for the report. I can confirm this issue but I'm not sure what >> exactly is causing it. Given that pdfsam in Debian is pretty much >> outdated it probably makes sense to remove it from

Bug#855324: pdfsam fails to start

2017-02-16 Thread Philip Rinn
On 16.02.2017 at 23:18, Markus Koschany wrote: [...] > thank you for the report. I can confirm this issue but I'm not sure what > exactly is causing it. Given that pdfsam in Debian is pretty much > outdated it probably makes sense to remove it from Stretch. True, pdfsam is outdated but afaik

Bug#854551: 400 errors caused by 7.0.28-4+deb7u10

2017-02-16 Thread Markus Koschany
On 16.02.2017 23:39, Allen Hadden wrote: > The plot thickens! I created a local build from git using the > 7.0.28-4+deb7u10 tag. Interestingly when I did that I was unable to > reproduce the problem. Originally I suspected that there was something > wrong with my build. But after some digging,

Bug#854551: 400 errors caused by 7.0.28-4+deb7u10

2017-02-16 Thread Allen Hadden
The plot thickens! I created a local build from git using the 7.0.28-4+deb7u10 tag. Interestingly when I did that I was unable to reproduce the problem. Originally I suspected that there was something wrong with my build. But after some digging, I'm starting to suspect the official build.

Processed: Re: Bug#855324: pdfsam fails to start

2017-02-16 Thread Debian Bug Tracking System
Processing control commands: > tags -1 confirmed Bug #855324 [pdfsam] pdfsam fails to start Added tag(s) confirmed. -- 855324: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855324 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems __ This is the maintainer address of

Bug#855324: pdfsam fails to start

2017-02-16 Thread Markus Koschany
Control: tags -1 confirmed On 16.02.2017 20:19, Philip Rinn wrote: > Package: pdfsam > Version: 1.1.4-2 > Severity: grave > Justification: renders package unusable > > Hi, > > pdfsam fails to start with this error on the console: [...] thank you for the report. I can confirm this issue but

Bug#855324: pdfsam fails to start

2017-02-16 Thread Philip Rinn
Package: pdfsam Version: 1.1.4-2 Severity: grave Justification: renders package unusable Hi, pdfsam fails to start with this error on the console: philip@debian:~$ pdfsam [warning] /usr/bin/pdfsam: No java runtime was found

Bug#854551: 400 errors caused by 7.0.28-4+deb7u10

2017-02-16 Thread Markus Koschany
Hello, On 16.02.2017 17:38, Allen Hadden wrote: > We are seeing the same thing that Samuel Wolf described, but from our > web UI and with 7.0.28-4+deb7u10. We get seemingly random 400 HTTP returns. > > We downgraded to 7.0.28-4+deb7u4 and that problem went away. > > Unfortunately in our

Bug#854551: 400 errors caused by 7.0.28-4+deb7u10

2017-02-16 Thread Allen Hadden
We are seeing the same thing that Samuel Wolf described, but from our web UI and with 7.0.28-4+deb7u10. We get seemingly random 400 HTTP returns. We downgraded to 7.0.28-4+deb7u4 and that problem went away. Unfortunately in our environment the Tomcat-side Java exception is not being logged,

Bug#854551: Upgrade from 7.0.56-3+deb8u7 -> 7.0.56-3+deb8u8 break Alfresco Solr on Debian

2017-02-16 Thread Samuel Wolf
Try tomcat7 from backports in Jessie, no problem with it, Alfresco works fine. ii libservlet3.0-java 7.0.75-1~bpo8+1 all Servlet 3.0 and JSP 2.2 Java API classes ii libtomcat7-java 7.0.75-1~bpo8+1 all Servlet and JSP engine -- core

Bug#854551: Upgrade from 7.0.56-3+deb8u7 -> 7.0.56-3+deb8u8 break Alfresco Solr on Debian

2017-02-16 Thread Samuel Wolf
After upgrade from 7.0.56-3+deb8u7 to 7.0.56-3+deb8u8 Alfresco Solr doesn't work: 00:27:00,104 ERROR [org.alfresco.solr.tracker.AbstractTracker] Tracking failed org.alfresco.error.AlfrescoRuntimeException: 01160004 api/solr/aclchangesets return status:400 at