libcommons-jexl2-java_2.1.1-1_amd64.changes uploaded successfully to localhost
along with the files:
libcommons-jexl2-java_2.1.1-1.dsc
libcommons-jexl2-java_2.1.1.orig.tar.gz
libcommons-jexl2-java_2.1.1-1.debian.tar.gz
libcommons-jexl2-java_2.1.1-1_all.deb
binary:libcommons-jexl2-java-doc is NEW.
binary:libcommons-jexl2-java is NEW.
source:libcommons-jexl2-java is NEW.
Your package contains new components which requires manual editing of
the override file. It is ok otherwise, so please be patient. New
packages are usually added to the override
Processing control commands:
reopen -1
Bug #706333 {Done: Gabriele Giacone 1o5g4...@gmail.com} [sweethome3d]
sweethome3d: Walls or Rooms don't appear
Bug reopened
Ignoring request to alter fixed versions of bug #706333 to the same values
previously set
--
706333:
Control: reopen -1
I can't reproduce it.
Please upload a kazam/istanbul/byzanz + key-mon recording somewhere.
__
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
Control: reassign -1 src:maven
Moritz Muehlenhoff j...@inutil.org writes:
Package: maven3
There is no maven3 package, so I'm reassigning to maven, which does have
a version = 3, so I assume it is the package you meant to file the bug
against.
Severity: grave
Tags: security
Justification:
Hi,
It appears that the sun-java6-jdk package has been removed from the canonical
mirror, and was subsequently purged from my internal mirror.
I have an urgent and temporary need for this .deb to get me through a test
cycle before I can replace it with a supported Java.
I have spent the
Hello Java package maintainers,
Ubuntu has recently shipped security fixes for a whole mountain of Java
fixes (see forwarded mail below).
I have randomly taken one of the bugs, CVE-2013-1518 and checked it:
https://security-tracker.debian.org/tracker/CVE-2013-1518
and it apears Debian is
On 2013-03-13 20:55, Jim Goddard wrote:
Hi,
Hi,
Sorry for the very late reply. I am not sure why but your email did not
reach my inbox until today (29th of April), but I don't see a reply to
this email, so I hope better late than never applies to this case.
It appears that the
Package: cofoja
Version: 1.0~r139-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu ubuntu-patch saucy
cofoja fails to build with OpenJDK 7, because the unmappable character
diagnostics that were warnings in OpenJDK 6 are now errors. These start
with:
libcommons-logging-java_1.1.2-2_amd64.changes uploaded successfully to localhost
along with the files:
libcommons-logging-java_1.1.2-2.dsc
libcommons-logging-java_1.1.2-2.debian.tar.gz
libcommons-logging-java_1.1.2-2_all.deb
libcommons-logging-java-doc_1.1.2-2_all.deb
Greetings,
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 15 Apr 2013 18:33:00 +0200
Source: libcommons-logging-java
Binary: libcommons-logging-java libcommons-logging-java-doc
Architecture: source all
Version: 1.1.2-2
Distribution: experimental
Urgency: low
Maintainer:
Package: cofoja
Severity: minor
Dear Maintainer,
Please either update the Vcs-Git and Vcs-Browser fields (which refer to
cofoja.git) or rename the pkg-java git repository on Alioth (which is named
libcofoja-java.git) so that debcheckout and the PTS links work correctly.
Thank you,
tony
--
12 matches
Mail list logo