snappy-java_1.1.1.6-1_amd64.changes uploaded successfully to localhost
along with the files:
snappy-java_1.1.1.6-1.dsc
snappy-java_1.1.1.6.orig.tar.xz
snappy-java_1.1.1.6-1.debian.tar.xz
libsnappy-java_1.1.1.6-1_all.deb
libsnappy-jni_1.1.1.6-1_amd64.deb
Greetings,
Your Debian
binary:libsnappy-jni 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 valid), so please be patient.
Packages are routinely processed through to the
Hello Stephen,
On Mon, 08 Sep 2014, Stephen Nelson wrote:
For what it's worth, CVE-2014-3578 was assigned to a directory traversal
vulnerability in libspring-java
( http://www.pivotal.io/security/cve-2014-3578)
Thanks for letting us know about this one. I've had a quick look and it
might
On 26 Nov 2014 10:45, Raphael Hertzog hert...@debian.org wrote:
Hello Stephen,
On Mon, 08 Sep 2014, Stephen Nelson wrote:
For what it's worth, CVE-2014-3578 was assigned to a directory
traversal
vulnerability in libspring-java
( http://www.pivotal.io/security/cve-2014-3578)
Thanks
I've been investigating this issue as well. I contacted an upstream
developer and it seems the actual fix for this issue is unknown. The
version 3.2.0 was just reported as not vulnerable by the security
researched who discovered this issue.
I can prepare an upgrade to the latest 3.2.x version but
On Wed, Nov 26, 2014 at 12:40:37PM +0100, Emmanuel Bourg wrote:
I've been investigating this issue as well. I contacted an upstream
developer and it seems the actual fix for this issue is unknown. The
version 3.2.0 was just reported as not vulnerable by the security
researched who discovered
Le 26/11/2014 12:41, Moritz Muehlenhoff a écrit :
I didn't look into the specific issue, but Red Hat Bugzilla has
references to isolated patches?
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2014-0225
I don't know why the title of the mail refers to CVE-2014-0225, but the
bug #760733 is
FYI: The status of the libspring-java source package
in Debian's testing distribution has changed.
Previous version: 3.0.6.RELEASE-16
Current version: 3.0.6.RELEASE-17
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple
gradle-propdeps-plugin_0.0.7-1_amd64.changes uploaded successfully to localhost
along with the files:
gradle-propdeps-plugin_0.0.7-1.dsc
gradle-propdeps-plugin_0.0.7.orig.tar.xz
gradle-propdeps-plugin_0.0.7-1.debian.tar.xz
gradle-propdeps-plugin_0.0.7-1_all.deb
Greetings,
Your
binary:gradle-propdeps-plugin is NEW.
source:gradle-propdeps-plugin 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 valid), so please be patient.
Control: tags -1 patch confirmed
On Mon, 24 Nov 2014 17:19:23 +0100 Markus Koschany a...@gambaru.de wrote:
With new installations I see the same result as mentioned in this bug
report. No option for Java or C++ projects. My old installation of
eclipse, which has been constantly updated over
Processing control commands:
tags -1 patch confirmed
Bug #763994 [eclipse] eclipse: no java or c++ project available in filenew
Added tag(s) confirmed and patch.
--
763994: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
12 matches
Mail list logo
