Package: clojure
Version: 1.1.0+dfsg-1
Severity: wishlist
I which Clojure 1.2.
Why don't you upload Clojure 1.2 which seems to be ready on Debian's
repository?
-- System Information:
Debian Release: 6.0
APT prefers stable
APT policy: (990, 'stable'), (500, 'squeeze-updates'), (500, 'oldstable
I'd be happy to help. I thought that architecture dependency was an
issue but I didn't realise how fickle Eclipse actually is. In fact,
it's really the only program where I haven't been able to
copy-and-drop the dot-file/folder to restore my settings. Anyway,
that's an upstream problem. I'll pi
Good Day!
Am Chris Thompson from United States. I will be pleased to have a discussion with you on my company intended offshore partnership, in which you will stand as a middle man between my company and the supplier of a product in Malaysia. If you are genuinely interested, respond immediately
Accepted:
java-gnome_4.0.19-1.debian.tar.gz
to main/j/java-gnome/java-gnome_4.0.19-1.debian.tar.gz
java-gnome_4.0.19-1.dsc
to main/j/java-gnome/java-gnome_4.0.19-1.dsc
java-gnome_4.0.19.orig.tar.gz
to main/j/java-gnome/java-gnome_4.0.19.orig.tar.gz
libjava-gnome-java-doc_4.0.19-1_all.deb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2011-03-15 21:10, Borden Rhodes wrote:
> Is this bug still being worked on? [...]
Hi
Personally I am hoping for a solution from upstream here; at best we
can hope to provide some fragile scripts that on a best effort basis
attempts to repair t
java-gnome_4.0.19-1_amd64.changes uploaded successfully to localhost
along with the files:
java-gnome_4.0.19-1.dsc
java-gnome_4.0.19.orig.tar.gz
java-gnome_4.0.19-1.debian.tar.gz
libjava-gnome-java_4.0.19-1_all.deb
libjava-gnome-java-doc_4.0.19-1_all.deb
libjava-gnome-jni_4.0.19-1_amd64
X-TagToolbar-Keys: D20110315230545409
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
That's because log4j 1.2.16 uses a packaging of 'bundle', instead of the
usual 'jar' packaging.
On 15/03/11 17:29, Miguel Landaeta wrote:
>
> On Mon, Mar 14, 2011 at 5:45 PM, Ludovic Cl
Author: gmazoyer-guest
Date: 2011-03-15 22:04:04 + (Tue, 15 Mar 2011)
New Revision: 13432
Modified:
trunk/java-gnome/debian/patches/03_libnotify_0_7.patch
Log:
Fix example compilation with libnotify >= 0.7.0.
Modified: trunk/java-gnome/debian/patches/03_libnotify_0_7.patch
Author: sylvestre
Date: 2011-03-15 21:55:48 + (Tue, 15 Mar 2011)
New Revision: 13431
Modified:
trunk/java-gnome/debian/control
Log:
right version of libnotify-dev
Modified: trunk/java-gnome/debian/control
===
--- trunk/java-gn
Accepted:
jasperreports_4.0.1+dfsg-1.debian.tar.gz
to main/j/jasperreports/jasperreports_4.0.1+dfsg-1.debian.tar.gz
jasperreports_4.0.1+dfsg-1.dsc
to main/j/jasperreports/jasperreports_4.0.1+dfsg-1.dsc
jasperreports_4.0.1+dfsg.orig.tar.gz
to main/j/jasperreports/jasperreports_4.0.1+dfsg.or
Author: gmazoyer-guest
Date: 2011-03-15 21:04:00 + (Tue, 15 Mar 2011)
New Revision: 13430
Modified:
trunk/java-gnome/debian/patches/03_libnotify_0_7.patch
Log:
Here is the real fixed patch.
Modified: trunk/java-gnome/debian/patches/03_libnotify_0_7.patch
===
Author: gmazoyer-guest
Date: 2011-03-15 20:49:00 + (Tue, 15 Mar 2011)
New Revision: 13429
Modified:
trunk/java-gnome/debian/patches/03_libnotify_0_7.patch
Log:
Fix for upstream configure file to compile with libnotify >= 0.7.0.
Modified: trunk/java-gnome/debian/patches/03_libnotify_0_7.pat
Is this bug still being worked on? I don't know if I have the same
cause but I have the same symptoms. I got a new computer, installed
Eclipse, moved my ~/.eclipse folder over to the machine and, same as
the initial bug report, the local plug-ins show up in "Installed
Software" they're not access
jasperreports_4.0.1+dfsg-1_amd64.changes uploaded successfully to localhost
along with the files:
jasperreports_4.0.1+dfsg-1.dsc
jasperreports_4.0.1+dfsg.orig.tar.gz
jasperreports_4.0.1+dfsg-1.debian.tar.gz
libjasperreports-java_4.0.1+dfsg-1_all.deb
libjasperreports-java-doc_4.0.1+dfsg-1_
Author: drazzib
Date: 2011-03-15 19:24:56 + (Tue, 15 Mar 2011)
New Revision: 13428
Added:
tags/jasperreports/4.0.1+dfsg-1/
tags/jasperreports/4.0.1+dfsg-1/debian/changelog
tags/jasperreports/4.0.1+dfsg-1/debian/patches/06_configure_javaflow.diff
tags/jasperreports/4.0.1+dfsg-1/deb
Author: drazzib
Date: 2011-03-15 19:23:37 + (Tue, 15 Mar 2011)
New Revision: 13427
Modified:
trunk/jasperreports/debian/changelog
trunk/jasperreports/debian/patches/06_configure_javaflow.diff
trunk/jasperreports/debian/patches/07_exclude_barcode4j_and_barbecue.diff
trunk/jasperrepo
Your message dated Tue, 15 Mar 2011 19:21:47 +0100
with message-id
and subject line Re: Bug#618501: sun-java6-jdk: CVE 2010-4476, Security Alert
has caused the Debian Bug report #618501,
regarding sun-java6-jdk: CVE 2010-4476, Security Alert
to be marked as done.
This means that you claim that th
Package: sun-java6-jdk
Version: 6.22-1
Severity: normal
Tags: squeeze
http://www.oracle.com/technetwork/topics/security/alert-cve-2010-4476-305811.html
It opens a security hole, if you need to use sun-jdk e.g. running a tomcat
server
new fixed upstream version >6.23 is placed in whezzy
-- Sys
On Mon, Mar 14, 2011 at 5:45 PM, Ludovic Claude
wrote:
>> liblog4j-1.2-java 1.2.15-11 (unstable) provides
>> /usr/share/maven-repo/log4j/log4j/1.2.x/log4j-1.2.x.pom
>>
>> liblog4j-1.2-java 1.2.16-1 (experimental) doesn't
>> provide that file anymore.
>>
>
> That looks wrong, as this package should
19 matches
Mail list logo