Processing commands for cont...@bugs.debian.org:
# Wed Aug 19 08:04:53 UTC 2009
# Tagging as pending bugs that are closed by packages in NEW
# http://ftp-master.debian.org/new.html
#
# Source package in NEW: libcommons-dbcp-java
tags 539179 + pending
Bug #539179 [libcommons-dbcp-java]
Package: azureus
Version: 4.2.0.4-1
Severity: grave
Justification: renders package unusable
I have openjdk-6-jre installed, because azureus used to depend on it.
openjdk works fine with other java applications as well, so no
complaints here. But (see bug report #515015) some users found it
On Wed, Aug 19, 2009 at 5:42 PM, Jan Willem Stumpeljstum...@planet.nl wrote:
Package: azureus
Version: 4.2.0.4-1
Severity: grave
Justification: renders package unusable
I have openjdk-6-jre installed, because azureus used to depend on it.
openjdk works fine with other java applications as
tag + unreproducible moreinfo
Well, I've tested it on openjdk, otherwise I wouldn't released it.
I've attached the output from my machine, after update-java-alternatives
--set java-6-openjdk and it's working fine.
I think it's something wrong with your installation. As Onkar pointed
please provide
Package: libtomcat6-java
Version: 6.0.20-5
Severity: important
The symlink /usr/share/tomcat6/lib/jasper.jar appears to have moved
from tomcat6-common (in 6.0.20-2) to libtomcat6-java (in
6.0.20-5). Because of this, upgrades fail (excuse the Swedish):
Förbereder att ersätta libtomcat6-java
Sorry about the typo. I have tested in chroot too. it doesn't seem to
happen. Waiting for your log output.
tags 542392 + unreproducible moreinfo
severity 542392 important
--
Best regards,
Adrian Perez adrianperez@gmail.com
signature.asc
Description: This is a digitally signed message part
Processing commands for cont...@bugs.debian.org:
tags 542392 + unreproducible moreinfo
Bug #542392 [azureus] azureus: Refuses to start
Added tag(s) unreproducible and moreinfo.
severity 542392 important
Bug #542392 [azureus] azureus: Refuses to start
Severity set to 'important' from 'grave'
I'm not sure it's a good change. When I worked on tomcat6 packaging, I
changed the permissions used in tomcat5.5 on purpose.
/etc/tomcat6:
This was set to root:root 644, with two exceptions:
- tomcat-users.xml that needs to be read by tomcat and hidden to users,
so it is root:tomcat6 640
-
Hello Thierry,
Well that sounds well argumented, in particular the issue of permissions
for /etc/tomcat6.
Do you recommend reverting permissions in /etc/tomcat6 to root:root 640?
In any case, such security issues should have been well documented in
the package, to prevent ignorant maintainers
Ludovic Claude wrote:
Well that sounds well argumented, in particular the issue of permissions
for /etc/tomcat6.
Do you recommend reverting permissions in /etc/tomcat6 to root:root 640?
Yes, I would recommend reverting /etc permissions the way they were
before (root:root 640 with the 2
Accepted:
commons-pool_1.5.2-1.diff.gz
to pool/main/c/commons-pool/commons-pool_1.5.2-1.diff.gz
commons-pool_1.5.2-1.dsc
to pool/main/c/commons-pool/commons-pool_1.5.2-1.dsc
commons-pool_1.5.2.orig.tar.gz
to pool/main/c/commons-pool/commons-pool_1.5.2.orig.tar.gz
Accepted:
libcommons-dbcp-java-doc_1.3~svn803474-1_all.deb
to
pool/main/libc/libcommons-dbcp-java/libcommons-dbcp-java-doc_1.3~svn803474-1_all.deb
libcommons-dbcp-java_1.3~svn803474-1.diff.gz
to
pool/main/libc/libcommons-dbcp-java/libcommons-dbcp-java_1.3~svn803474-1.diff.gz
Your message dated Wed, 19 Aug 2009 15:13:12 +
with message-id e1mdmqe-0004iw...@ries.debian.org
and subject line Bug#506361: fixed in commons-pool 1.5.2-1
has caused the Debian Bug report #506361,
regarding please split out api docs
to be marked as done.
This means that you claim that the
Your message dated Wed, 19 Aug 2009 15:14:09 +
with message-id e1mdmrz-0004kp...@ries.debian.org
and subject line Bug#539179: fixed in libcommons-dbcp-java 1.3~svn803474-1
has caused the Debian Bug report #539179,
regarding libcommons-dbcp-java: FTBFS if default-jdk points to openjdk
to be
Your message dated Wed, 19 Aug 2009 15:14:09 +
with message-id e1mdmrz-0004kn...@ries.debian.org
and subject line Bug#532888: fixed in libcommons-dbcp-java 1.3~svn803474-1
has caused the Debian Bug report #532888,
regarding Update the license to Apache License 2.0
to be marked as done.
This
FYI: The status of the gant source package
in Debian's testing distribution has changed.
Previous version: 1.6.1-2
Current version: 1.7.0-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will receive
FYI: The status of the jetty source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 6.1.19-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you
FYI: The status of the tomcat6 source package
in Debian's testing distribution has changed.
Previous version: 6.0.20-2
Current version: 6.0.20-5
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will
FYI: The status of the libstax-java source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 1.2.0-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day
FYI: The status of the surefire source package
in Debian's testing distribution has changed.
Previous version: 2.4.3-1
Current version: 2.4.3-3
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will
FYI: The status of the maven-repo-helper source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 0.7
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day
Adrian Perez wrote:
tag + unreproducible moreinfo
Well, I've tested it on openjdk, otherwise I wouldn't released it.
I've attached the output from my machine, after update-java-alternatives
--set java-6-openjdk and it's working fine.
I think it's something wrong with your installation. As
I think we both agree the problem is related to your environment and not
the packaging.
It seems the java-wrapper script it's not finding your java runtime,
which may be caused by a wrong environment configuration.
Make sure you have no environment variables like JAVA_HOME or JAVA_CMD
set, since
Extra info: downgrading to 3.1.1.0-4 restored functionality at once.
Regards, Jan
___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Adrian Perez wrote:
I think we both agree the problem is related to your
environment and not the packaging.
That's very likely.
It seems the java-wrapper script it's not finding your java
runtime, which may be caused by a wrong environment
configuration. Make sure you have no environment
On Wed, 2009-08-19 at 21:47 +0200, Jan Willem Stumpel wrote:
JAVA_HOME is set, to /usr/lib/java. I do not know where this is
set. JAVA_CMD is not normally set.
That's exactly what is causing the script to fail. It's using your
provided JAVA_HOME which is set to /usr/lib/java. Then, according
Hallo,
eclipse is now working OK. I have the following xulrunner packages
installed. I haven't xulrunner-dev installed.
vinc...@pc-vincent:~$ dpkg-query -l xulrunner*
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/
Package: maven-debian-helper
Version: 0.6
Severity: normal
Hi,
When using mh_lspoms command from maven-debian-helper, I'm getting the
following error :
Check the parent dependency in the sub project ./core/pom.xml
dpkg --search /usr/share/maven-
28 matches
Mail list logo
