Processed: tagging as pending bugs that are closed by packages in NEW

2009-08-19 Thread Debian Bug Tracking System
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] libcommons-dbcp-java: FTBFS if default-jdk 
points to openjdk
Added tag(s) pending.
 # Source package in NEW: update-manager
 tags 480504 + pending
Bug #480504 [update-manager] Does neither update package list nor packages
Bug #480884 [update-manager] update-manager: it doesn't work. It find releases 
but you cannot update the packages
Added tag(s) pending.
Added tag(s) pending.
 # Source package in NEW: update-manager
 tags 523703 + pending
Bug #523703 [update-manager] update-manager: Fails to download changelogs for 
available updates after dist upgrade from lenny to unstable
Added tag(s) pending.
 # Source package in NEW: update-manager
 tags 454686 + pending
Bug #454686 [update-manager] update-manager: new messages are added by dpatch 
which isn't friendly for translators
Added tag(s) pending.
 # Source package in NEW: update-manager
 tags 503584 + pending
Bug #503584 [update-manager] update-manager: Install Updates button doesn't 
work when you check for updates manually
Added tag(s) pending.
 # Source package in NEW: update-manager
 tags 529333 + pending
Bug #529333 [update-manager] update-manager: fails to smart-upgrade
Added tag(s) pending.
 # Source package in NEW: update-manager
 tags 449040 + pending
Bug #449040 [update-manager] update-manager: Smart Upgrade removes packages 
with dependency problems without confirmation
Added tag(s) pending.
 # Source package in NEW: update-manager
 tags 519320 + pending
Bug #519320 [update-manager] update-manager: broken in testing/squeeze
Added tag(s) pending.
 # Source package in NEW: update-manager
 tags 519191 + pending
Bug #519191 [update-manager] Shows updates; but does not install them
Added tag(s) pending.
 # Source package in NEW: update-manager
 tags 533994 + pending
Bug #533994 [update-manager] update-manager: FTBFS: cp: cannot stat 
`./debian/tmp/usr/share/update-manager': No such file or directory
Added tag(s) pending.
 # Source package in NEW: update-manager
 tags 541584 + pending
Bug #541584 [update-manager] update-manager: should depend on python-gconf 
instead of python-gnome2
Added tag(s) pending.
 # Source package in NEW: update-manager
 tags 415376 + pending
Bug #415376 [update-manager] still thinks we're in Ubuntu
Added tag(s) pending.
 # Source package in NEW: update-manager
 tags 494498 + pending
Bug #494498 [update-manager] update-manager should use the user's browser 
instead of running it as root
Bug #494641 [update-manager] Clickable bug links open browser as 'root' if 
update-manager invoked by update-notifier
Added tag(s) pending.
Added tag(s) pending.
 # Source package in NEW: update-manager
 tags 515965 + pending
Bug #515965 [update-manager] update-manager fails with current dist not found 
in meta-release file
Added tag(s) pending.
 # Source package in NEW: update-manager
 tags 479130 + pending
Bug #479130 [update-manager] Could not calculate the upgrade
Added tag(s) pending.
 # Source package in NEW: clucene-core
 tags 542337 + pending
Bug #542337 [clucene-core] unstable reuses library package name from etch with 
incompatible ABI
Added tag(s) pending.

End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers


Bug#542392: azureus: Refuses to start

2009-08-19 Thread Jan Willem Stumpel
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 annoying
that other jre's, like Sun's, could not be used.

Now the latest azureus version corrects this, I believe by means of the script
java-wrappers.sh. I suppose sun jre users are now happy. But I am very
UNhappy, because now azureus refuses to start at all. The error messages
are:

/usr/lib/java-wrappers/java-wrappers.sh: line 243: /usr/lib/java/bin/java:
/ No such file or directory
/usr/lib/java-wrappers/java-wrappers.sh: line 243: exec:
/ /usr/lib/java/bin/java: cannot execute: No such file or directory

Why can't azureus simply use the /etc/alternatives mechanism? 

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages azureus depends on:
ii  java-wrappers 0.1.15 wrappers for java executables
ii  libcommons-cli-java   1.2-2  API for working with the command l
ii  liblog4j1.2-java  1.2.15-7   Logging library for java
ii  libswt-gtk-3.4-java   3.4.2-2Standard Widget Toolkit for GTK+ J
ii  openjdk-6-jre 6b16-4 OpenJDK Java runtime, using Hotspo

Versions of packages azureus recommends:
ii  vuze  4.2.0.4-1  Multimedia BitTorrent client

azureus suggests no packages.

-- no debconf information



___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers


Bug#542392: azureus: Refuses to start

2009-08-19 Thread Onkar Shinde
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 well, so no
 complaints here. But (see bug report #515015) some users found it annoying
 that other jre's, like Sun's, could not be used.

 Now the latest azureus version corrects this, I believe by means of the script
 java-wrappers.sh. I suppose sun jre users are now happy. But I am very
 UNhappy, because now azureus refuses to start at all. The error messages
 are:

 /usr/lib/java-wrappers/java-wrappers.sh: line 243: /usr/lib/java/bin/java:
 / No such file or directory
 /usr/lib/java-wrappers/java-wrappers.sh: line 243: exec:
 / /usr/lib/java/bin/java: cannot execute: No such file or directory

I don't see a problem with java-wrappers script or azureus launcher script.
Can you please try this?
Modify the azureus launcher script (/usr/bin/azureus), and add
DEBUG_WRAPPER=1 just before run_java.
i.e. DEBUG_WRAPPER=1 run_java -Dazureus.install.path=$HOME/.azureus $UI \
org.gudy.azureus2.ui.common.Main $@

Try launching azureus from command line then and paste the output in the bug.

 Why can't azureus simply use the /etc/alternatives mechanism?

Because azureus is known not to work with anything other than openjdk
or sun JREs. That's why. :-)


Cheers,
Onkar



___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers


Bug#542392: azureus: Refuses to start

2009-08-19 Thread Adrian Perez
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 debug information.






On Wed, 2009-08-19 at 18:36 +0530, Onkar Shinde wrote:
 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 well, so no
  complaints here. But (see bug report #515015) some users found it annoying
  that other jre's, like Sun's, could not be used.
 
  Now the latest azureus version corrects this, I believe by means of the 
  script
  java-wrappers.sh. I suppose sun jre users are now happy. But I am very
  UNhappy, because now azureus refuses to start at all. The error messages
  are:
 
  /usr/lib/java-wrappers/java-wrappers.sh: line 243: /usr/lib/java/bin/java:
  / No such file or directory
  /usr/lib/java-wrappers/java-wrappers.sh: line 243: exec:
  / /usr/lib/java/bin/java: cannot execute: No such file or directory
 
 I don't see a problem with java-wrappers script or azureus launcher script.
 Can you please try this?
 Modify the azureus launcher script (/usr/bin/azureus), and add
 DEBUG_WRAPPER=1 just before run_java.
 i.e. DEBUG_WRAPPER=1 run_java -Dazureus.install.path=$HOME/.azureus $UI \
 org.gudy.azureus2.ui.common.Main $@
 
 Try launching azureus from command line then and paste the output in the bug.
 
  Why can't azureus simply use the /etc/alternatives mechanism?
 
 Because azureus is known not to work with anything other than openjdk
 or sun JREs. That's why. :-)
 
 
 Cheers,
 Onkar
 
 
 
 ___
 pkg-java-maintainers mailing list
 pkg-java-maintainers@lists.alioth.debian.org
 http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
-- 
Best regards,
Adrian Perez adrianperez@gmail.com
$ azureus
[debug] /usr/bin/azureus: Found JAVA_HOME = '/usr/lib/jvm/java-6-openjdk'
[debug] /usr/bin/azureus: Found JAVA_CMD = '/usr/lib/jvm/java-6-openjdk/bin/java'
[debug] /usr/bin/azureus: Environment variable CLASSPATH is ''
[debug] /usr/bin/azureus: Runnning /usr/lib/jvm/java-6-openjdk/bin/java  -classpath /usr/lib/jni:/usr/lib/java:/usr/share/java/Azureus2.jar:/usr/share/java/log4j-1.2.jar:/usr/share/java/commons-cli.jar:/usr/share/java/swt.jar -Dazureus.install.path=/home/adrian/.azureus org.gudy.azureus2.ui.common.Main
file:/usr/lib/jni/ ; file:/usr/lib/java/ ; file:/usr/share/java/Azureus2.jar ; file:/usr/share/java/log4j-1.2.15.jar ; file:/usr/share/java/commons-cli-1.1.jar ; file:/usr/lib/java/swt-gtk-3.4.2.jar ; file:/home/adrian/
changeLocale: *Default Language* != English (United States). Searching without country..
changeLocale: Searching for language English in *any* country..
changeLocale: no message properties for Locale 'English (United States)' (en_US), using 'English (default)'
UIFunctions/ImageLoad took 0ms
new shell took 278ms
new shell setup took 50ms
skinlisteners init took 27ms
skin init took 191ms
MainMenu init took 204ms
createWindow init took 0ms
skin layout took 25ms
pre skin widgets init took 50ms
hooks init took 0ms
WARNING: already added UIUpdatable com.aelitis.azureus.ui.swt.views.skin.sidebar.side...@1742700
skin widgets (1/2) init took 276ms
skin widgets init took 177ms
pre SWTInstance init took 0ms
Init Core Columns took 150ms
SWTInstance init took 0ms
shell.layout took 76ms
-DONE DISPATCH AT 1250688197362;2403ms
-READY AT 1250688197412;2453ms
shell.open took 754ms
processStartupDMS took 0ms
vuzeactivities init took 0ms
Locale Initializing took 0ms
28575:Core: 84ms for activity between 'Loading Plugin: azupnpav' and 'Loading Plugin: azupdater'
28626:Core: 25ms for activity between 'Loading Plugin: Start/Stop Rules' and 'Loading Plugin: Torrent Removal Rules'
28650:Core: 25ms for activity between 'Loading Plugin: Torrent Removal Rules' and 'Loading Plugin: Share Hoster'
28707:Core: 51ms for activity between 'Loading Plugin: Plugin Update Checker' and 'Loading Plugin: UPnP'
28804:Core: 25ms for activity between 'Loading Plugin: DHT Tracker' and 'Loading Plugin: Magnet URI Handler'
28839:Core: 25ms for activity between 'Loading Plugin: Core Update Checker' and 'Loading Plugin: Core Patch Checker'
28844:Core: 25ms for activity between 'Loading Plugin: Core Patch Checker' and 'Loading Plugin: Platform Checker'
29007:Core: 126ms for activity between 'Loading Plugin: Buddy' and 'Loading Torrent  2 of 6 : Hed Kandi live from Marbella, Spain [Z4G7LFJXIOAVU55W2JROHC6RLF6KXJCU].torrent'
29236:Core: 227ms for activity between 'Initializing Global Torrent Manager' and 'Initializing Plugin: UPnP Media Server'

Bug#542397: libtomcat6-java: upgrade fails, needs Conflict with older tomcat6-common

2009-08-19 Thread Marcus Better
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 6.0.20-2 (med 
.../libtomcat6-java_6.0.20-5_all.deb) ...
Packar upp ersättande libtomcat6-java ...
dpkg: fel vid hantering av 
/var/cache/apt/archives/libtomcat6-java_6.0.20-5_all.deb (--unpack):
 försöker skriva över /usr/share/tomcat6/lib/jasper.jar som också finns i 
paketet tomcat6-common

Seems like libtomcat6-java needs a Conflicts with tomcat6-common ( 6.0.20-5).

Retrying the update succeeds, since by then the new tomcat6-common has
already been unpacked.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30.4-melech (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libtomcat6-java depends on:
ii  default-jre-headless [java6-r 1.6-33 Standard Java or Java compatible R
ii  libcommons-dbcp-java  1.2.2-1Database Connection Pooling Servic
ii  libcommons-pool-java  1.3-1  pooling implementation for Java ob
ii  libecj-java   3.5-1  Eclipse Java compiler (library)
ii  libservlet2.5-java6.0.20-5   Servlet 2.5 and JSP 2.1 Java API c
ii  openjdk-6-jre-headless [java6 6b16-4 OpenJDK Java runtime, using Hotspo

libtomcat6-java recommends no packages.

Versions of packages libtomcat6-java suggests:
pn  tomcat6   none (no description available)

-- debconf-show failed



___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers

Bug#542392: azureus: Refuses to start

2009-08-19 Thread Adrian Perez
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
___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers

Processed: Re: azureus: Refuses to start

2009-08-19 Thread Debian Bug Tracking System
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'

 --
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers


Bug#532284: Permissions for tomcat6

2009-08-19 Thread Thierry Carrez
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
- Catalina directory that should allow autodeploy of new contexts by
tomcat, so it is root:tomcat6 775

The idea behind this was to specifically *exclude* the tomcat6 user from
messing with key configuration files like server.xml or
tomcat-users.xml, and it is a security measure against any traversal by
the tomcat6 user.

Your argument is that you need to be root to configure Tomcat. Well,
this mimics what is done for every other daemon out there: allow root to
configure it, and do not allow the user the daemon is run under to
modify its own configuration. See /etc/apache2 for an example of this.

/var/lib/tomcat6/webapps:

This was set to 775 root:tomcat6 so that tomcat can autodeploy
applications. Additionally, members of the tomcat6 group are also
allowed to deploy applications.

Changing that to tomcat6:adm just transfers that capability from the
tomcat6 group to the adm group. Looks like we lose some granularity,
 and I fail to see why adding users to the tomcat6 group does not look
like a good idea. But I can live with that :)

-- 
Thierry Carrez



___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers


Bug#532284: Permissions for tomcat6

2009-08-19 Thread Ludovic Claude
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 (me!) from messing up with
those sensitive issues.

Ludovic

Thierry Carrez a écrit :
 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
 - Catalina directory that should allow autodeploy of new contexts by
 tomcat, so it is root:tomcat6 775
 
 The idea behind this was to specifically *exclude* the tomcat6 user from
 messing with key configuration files like server.xml or
 tomcat-users.xml, and it is a security measure against any traversal by
 the tomcat6 user.
 
 Your argument is that you need to be root to configure Tomcat. Well,
 this mimics what is done for every other daemon out there: allow root to
 configure it, and do not allow the user the daemon is run under to
 modify its own configuration. See /etc/apache2 for an example of this.
 
 /var/lib/tomcat6/webapps:
 
 This was set to 775 root:tomcat6 so that tomcat can autodeploy
 applications. Additionally, members of the tomcat6 group are also
 allowed to deploy applications.
 
 Changing that to tomcat6:adm just transfers that capability from the
 tomcat6 group to the adm group. Looks like we lose some granularity,
  and I fail to see why adding users to the tomcat6 group does not look
 like a good idea. But I can live with that :)
 



___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers


Bug#532284: Permissions for tomcat6

2009-08-19 Thread Thierry Carrez
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 exceptions).

For /var/lib/tomcat6/webapps, the new setting doesn't lessen security so
I don't care so much. If someone has a good argument on why allowing the
adm group to deploy tomcat6 webapps is better than using the tomcat6
group, then so be it. To me it just sounds like we lose the possibility
of allowing someone to deploy webapps without making him a full member
of the adm group...

 In any case, such security issues should have been well documented in
 the package, to prevent ignorant maintainers (me!) from messing up with
 those sensitive issues.

Yes, I missed that in my changes-from-tomcat5.5 notes in README.Debian.

-- 
Thierry



___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers


commons-pool_1.5.2-1_amd64.changes ACCEPTED

2009-08-19 Thread Archive Administrator

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
libcommons-pool-java-doc_1.5.2-1_all.deb
  to pool/main/c/commons-pool/libcommons-pool-java-doc_1.5.2-1_all.deb
libcommons-pool-java_1.5.2-1_all.deb
  to pool/main/c/commons-pool/libcommons-pool-java_1.5.2-1_all.deb


Override entries for your package:
commons-pool_1.5.2-1.dsc - optional java
libcommons-pool-java-doc_1.5.2-1_all.deb - optional doc
libcommons-pool-java_1.5.2-1_all.deb - optional java

Announcing to debian-devel-chan...@lists.debian.org
Closing bugs: 506361 


Thank you for your contribution to Debian.

___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers


libcommons-dbcp-java_1.3~svn803474-1_amd64.changes ACCEPTED

2009-08-19 Thread Archive Administrator

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
libcommons-dbcp-java_1.3~svn803474-1.dsc
  to 
pool/main/libc/libcommons-dbcp-java/libcommons-dbcp-java_1.3~svn803474-1.dsc
libcommons-dbcp-java_1.3~svn803474-1_all.deb
  to 
pool/main/libc/libcommons-dbcp-java/libcommons-dbcp-java_1.3~svn803474-1_all.deb
libcommons-dbcp-java_1.3~svn803474.orig.tar.gz
  to 
pool/main/libc/libcommons-dbcp-java/libcommons-dbcp-java_1.3~svn803474.orig.tar.gz


Override entries for your package:
libcommons-dbcp-java-doc_1.3~svn803474-1_all.deb - optional doc
libcommons-dbcp-java_1.3~svn803474-1.dsc - optional java
libcommons-dbcp-java_1.3~svn803474-1_all.deb - optional java

Announcing to debian-devel-chan...@lists.debian.org
Closing bugs: 532888 539179 


Thank you for your contribution to Debian.

___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers


Bug#506361: marked as done (please split out api docs)

2009-08-19 Thread Debian Bug Tracking System
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 problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
506361: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
package: libcommons-pool-java
version: 1.3-1
severity: minor

This package contains api documentation, that is not useful at runtime;
it's only useful during development.

Having it included for all installs, is a waste, as most installs don't
need to see the individual method calls.

Please split it out into a separate package.


---End Message---
---BeginMessage---
Source: commons-pool
Source-Version: 1.5.2-1

We believe that the bug you reported is fixed in the latest version of
commons-pool, which is due to be installed in the Debian FTP archive:

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
libcommons-pool-java-doc_1.5.2-1_all.deb
  to pool/main/c/commons-pool/libcommons-pool-java-doc_1.5.2-1_all.deb
libcommons-pool-java_1.5.2-1_all.deb
  to pool/main/c/commons-pool/libcommons-pool-java_1.5.2-1_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 506...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Damien Raude-Morvan draz...@drazzib.com (supplier of updated commons-pool 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 18 Aug 2009 20:59:34 +0200
Source: commons-pool
Binary: libcommons-pool-java libcommons-pool-java-doc
Architecture: source all
Version: 1.5.2-1
Distribution: unstable
Urgency: low
Maintainer: Debian Java Maintainers 
pkg-java-maintainers@lists.alioth.debian.org
Changed-By: Damien Raude-Morvan draz...@drazzib.com
Description: 
 libcommons-pool-java - pooling implementation for Java objects
 libcommons-pool-java-doc - pooling implementation for Java objects - 
documentation
Closes: 506361
Changes: 
 commons-pool (1.5.2-1) unstable; urgency=low
 .
   * New upstream release.
   * Split Javadoc API in a -doc package (Closes: #506361)
   * Migrate to CDBS packaging:
 - Cleanup debian/rules
 - Use quilt as patch system
 - Remove useless Suggests
 - Remove useless debian/dirs
   * Bump Standards-Version to 3.8.3:
 - Include a get-orig-source target
 - Change section to java
 - Add Homepage field
   * Add myself to Uploaders
   * Use default-jdk/jre:
 - Depends on default-jre-headless
 - Build-Depends on default-jdk
 - Use /usr/lib/jvm/default-java as JAVA_HOME
   * Update debian/copyright:
 - Don't include full Apache 2 licence
 - Update Copyright assignements
   * Maven POMs:
 - Add a Build-Depends-Indep dependency on maven-repo-helper
 - Use mh_installpom and mh_installjar to install the POM and the jar to the
  Maven repository
   * Move api documentation to /usr/share/doc/libcommons-pool-java/api
Checksums-Sha1: 
 80f50f1788ef3396d75808f862bd3a6669426770 1490 commons-pool_1.5.2-1.dsc
 36e9798da8f07c1fbabaf75c45c94f0e28f9bda8 477222 commons-pool_1.5.2.orig.tar.gz
 a3d0bb7e3ed52267dff0fd7a9005bfa63c3d7698 3521 commons-pool_1.5.2-1.diff.gz
 a5a91d7a534ab49d4475af33ac2a659f5c5c11ef 9 
libcommons-pool-java_1.5.2-1_all.deb
 3c9713ffe383e1b74bcac80c6172ed217322d51f 96610 
libcommons-pool-java-doc_1.5.2-1_all.deb
Checksums-Sha256: 
 50bb9c5137f6a8579525ecf6525b4ae226c98d8430ed45eb358947ad4f42cd9e 1490 
commons-pool_1.5.2-1.dsc
 7af7f7c5046759b77e15f9969f03177440d6fe086aa2894b75feb0b948c62418 477222 
commons-pool_1.5.2.orig.tar.gz
 6729e35fd89af1b293c753a9ceaa721b026fe66c13529fd11d75dec40564d81f 3521 
commons-pool_1.5.2-1.diff.gz
 2ca89c37111f8485390567191037e2a16a3d5844cf5f8373bbe678e4ae46963c 9 
libcommons-pool-java_1.5.2-1_all.deb
 67f71e7c0860bcce732f52dc3768b726867c8d2d0362c794907a7b49847545d1 96610 
libcommons-pool-java-doc_1.5.2-1_all.deb
Files: 
 

Bug#539179: marked as done (libcommons-dbcp-java: FTBFS if default-jdk points to openjdk)

2009-08-19 Thread Debian Bug Tracking System
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 marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
539179: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libcommons-dbcp-java
Version: 1.2.2-1
Severity: important
Usertags: java-common

Hi,

this package FTBFS if default-jdk points to openjdk - a change that is
planned for the future. The relevant part of the build log is:

[javac] 
/tmp/buildd/libcommons-dbcp-java-1.2.2/src/java/org/apache/commons/dbcp/BasicDataSource.java:44:
 org.apache.commons.dbcp.BasicDataSource is not abstract and does not override 
abstract method isWrapperFor(java.lang.Class) in java.sql.Wrapper
[javac] public class BasicDataSource implements DataSource {
[javac]^
[javac] 
/tmp/buildd/libcommons-dbcp-java-1.2.2/src/java/org/apache/commons/dbcp/DelegatingStatement.java:46:
 org.apache.commons.dbcp.DelegatingStatement is not abstract and does not 
override abstract method isPoolable() in java.sql.Statement
[javac] public class DelegatingStatement extends AbandonedTrace implements 
Statement {
[javac]^
[javac] 
/tmp/buildd/libcommons-dbcp-java-1.2.2/src/java/org/apache/commons/dbcp/DelegatingStatement.java:131:
 isClosed() in org.apache.commons.dbcp.DelegatingStatement cannot implement 
isClosed() in java.sql.Statement; attempting to assign weaker access 
privileges; was public
[javac] protected boolean isClosed() {
[javac]   ^
[javac] 
/tmp/buildd/libcommons-dbcp-java-1.2.2/src/java/org/apache/commons/dbcp/DelegatingPreparedStatement.java:50:
 org.apache.commons.dbcp.DelegatingPreparedStatement is not abstract and does 
not override abstract method setNClob(int,java.io.Reader) in 
java.sql.PreparedStatement
[javac] public class DelegatingPreparedStatement extends DelegatingStatement
[javac]^
[javac] 
/tmp/buildd/libcommons-dbcp-java-1.2.2/src/java/org/apache/commons/dbcp/DelegatingCallableStatement.java:53:
 org.apache.commons.dbcp.DelegatingCallableStatement is not abstract and does 
not override abstract method setNClob(java.lang.String,java.io.Reader) in 
java.sql.CallableStatement
[javac] public class DelegatingCallableStatement extends 
DelegatingPreparedStatement
[javac]^
[javac] 
/tmp/buildd/libcommons-dbcp-java-1.2.2/src/java/org/apache/commons/dbcp/DelegatingConnection.java:51:
 org.apache.commons.dbcp.DelegatingConnection is not abstract and does not 
override abstract method createStruct(java.lang.String,java.lang.Object[]) in 
java.sql.Connection
[javac] public class DelegatingConnection extends AbandonedTrace
[javac]^
[javac] 
/tmp/buildd/libcommons-dbcp-java-1.2.2/src/java/org/apache/commons/dbcp/DelegatingResultSet.java:55:
 org.apache.commons.dbcp.DelegatingResultSet is not abstract and does not 
override abstract method updateNClob(java.lang.String,java.io.Reader) in 
java.sql.ResultSet
[javac] public class DelegatingResultSet extends AbandonedTrace implements 
ResultSet {
[javac]^
[javac] 
/tmp/buildd/libcommons-dbcp-java-1.2.2/src/java/org/apache/commons/dbcp/PoolablePreparedStatement.java:41:
 org.apache.commons.dbcp.PoolablePreparedStatement is not abstract and does not 
override abstract method setNClob(int,java.io.Reader) in 
java.sql.PreparedStatement
[javac] public class PoolablePreparedStatement extends 
DelegatingPreparedStatement implements PreparedStatement {
[javac]^
[javac] 
/tmp/buildd/libcommons-dbcp-java-1.2.2/src/java/org/apache/commons/dbcp/PoolingConnection.java:42:
 org.apache.commons.dbcp.PoolingConnection is not abstract and does not 
override abstract method createStruct(java.lang.String,java.lang.Object[]) in 
java.sql.Connection
[javac] public class PoolingConnection extends DelegatingConnection 
implements Connection, KeyedPoolableObjectFactory {
[javac]^
[javac] 
/tmp/buildd/libcommons-dbcp-java-1.2.2/src/java/org/apache/commons/dbcp/PoolingDataSource.java:45:
 org.apache.commons.dbcp.PoolingDataSource is not abstract and does not 
override abstract method isWrapperFor(java.lang.Class) in java.sql.Wrapper
[javac] public class PoolingDataSource implements DataSource {
[javac]^
[javac] 

Bug#532888: marked as done (Update the license to Apache License 2.0)

2009-08-19 Thread Debian Bug Tracking System
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 means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
532888: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=532888
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---

Package: libcommons-dbcp-java
Version: 1.2.2-1
Severity: serious

The license in the package (Apache License 1.1) doesn't match the
license of the upstream release (Apache License 2.0)

https://svn.apache.org/repos/asf/commons/proper/dbcp/tags/DBCP_1_2_2/LICENSE.txt







---End Message---
---BeginMessage---
Source: libcommons-dbcp-java
Source-Version: 1.3~svn803474-1

We believe that the bug you reported is fixed in the latest version of
libcommons-dbcp-java, which is due to be installed in the Debian FTP archive:

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
libcommons-dbcp-java_1.3~svn803474-1.dsc
  to 
pool/main/libc/libcommons-dbcp-java/libcommons-dbcp-java_1.3~svn803474-1.dsc
libcommons-dbcp-java_1.3~svn803474-1_all.deb
  to 
pool/main/libc/libcommons-dbcp-java/libcommons-dbcp-java_1.3~svn803474-1_all.deb
libcommons-dbcp-java_1.3~svn803474.orig.tar.gz
  to 
pool/main/libc/libcommons-dbcp-java/libcommons-dbcp-java_1.3~svn803474.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 532...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Damien Raude-Morvan draz...@drazzib.com (supplier of updated 
libcommons-dbcp-java package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 18 Aug 2009 21:04:39 +0200
Source: libcommons-dbcp-java
Binary: libcommons-dbcp-java libcommons-dbcp-java-doc
Architecture: source all
Version: 1.3~svn803474-1
Distribution: unstable
Urgency: low
Maintainer: Debian Java Maintainers 
pkg-java-maintainers@lists.alioth.debian.org
Changed-By: Damien Raude-Morvan draz...@drazzib.com
Description: 
 libcommons-dbcp-java - Database Connection Pooling Services
 libcommons-dbcp-java-doc - Database Connection Pooling Services - documentation
Closes: 532888 539179
Changes: 
 libcommons-dbcp-java (1.3~svn803474-1) unstable; urgency=low
 .
   [ Emmanuel Bourg ]
   * Update of the URLs
   * Rename Jakarta Commons to Apache Commons
   * debian/copyright: Switch to Apache License 2.0. Closes: #532888.
 .
   [ Damien Raude-Morvan ]
   * New upstream SVN snapshot (r803474).
 - Fix FTBFS when using OpenJDK-6 (JDBC4 API) (Closes: #539179)
 - Add Build-Depends and Suggests on glassfish-javaee
   * Add myself as Uploaders
   * Bump Debhelper to 5
   * Use default-jdk/jre:
 - Build-Depends on default-jdk
 - Depends on default-jre-headless
 - Use /usr/lib/jvm/default-java as JAVA_HOME
   * Updated Standards-Version to 3.8.3:
 - Change section to java
 - Include a get-orig-source target
 - Add Homepage field
   * Remove useless dirs/links debhelper files
   * Split Javadoc API in a -doc package
   * Use quilt as patch system
   * Maven POMs:
 - Add a Build-Depends-Indep dependency on maven-repo-helper
 - Use mh_installpom and mh_installjar to install the POM and the jar to the
   Maven repository
   * Move api documentation to /usr/share/doc/libcommons-dbcp-java/api
Checksums-Sha1: 
 0269b9790f74162ccb5f3ce911457dfcb425046a 1621 
libcommons-dbcp-java_1.3~svn803474-1.dsc
 b21343ef9cc51f8d48b5c285d9f2ce537cb14a56 926974 
libcommons-dbcp-java_1.3~svn803474.orig.tar.gz
 21691036ef6b787dd3e49475bbce14e5799cf572 4154 
libcommons-dbcp-java_1.3~svn803474-1.diff.gz
 4d0a046cea563025619757b999e8af5587e9fca5 155754 
libcommons-dbcp-java_1.3~svn803474-1_all.deb
 ce98232c7fa43061b3d0686644daed94c9e67325 157816 
libcommons-dbcp-java-doc_1.3~svn803474-1_all.deb
Checksums-Sha256: 
 957482305e825767e754995f22ea193aacae6a34906c64517227283b781dfa32 1621 

gant 1.7.0-1 MIGRATED to testing

2009-08-19 Thread Debian testing watch
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
later changes on the next day.
See http://release.debian.org/testing-watch/ for more information.

___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers


jetty 6.1.19-2 MIGRATED to testing

2009-08-19 Thread Debian testing watch
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 will receive
later changes on the next day.
See http://release.debian.org/testing-watch/ for more information.

___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers


tomcat6 6.0.20-5 MIGRATED to testing

2009-08-19 Thread Debian testing watch
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 receive
later changes on the next day.
See http://release.debian.org/testing-watch/ for more information.

___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers


libstax-java 1.2.0-1 MIGRATED to testing

2009-08-19 Thread Debian testing watch
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 you will receive
later changes on the next day.
See http://release.debian.org/testing-watch/ for more information.

___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers


surefire 2.4.3-3 MIGRATED to testing

2009-08-19 Thread Debian testing watch
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 receive
later changes on the next day.
See http://release.debian.org/testing-watch/ for more information.

___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers


maven-repo-helper 0.7 MIGRATED to testing

2009-08-19 Thread Debian testing watch
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 you will receive
later changes on the next day.
See http://release.debian.org/testing-watch/ for more information.

___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers


Bug#542392: azureus: Refuses to start

2009-08-19 Thread Jan Willem Stumpel
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 Onkar pointed
 please provide debug information.

 Can you please try this?
 Modify the azureus launcher script (/usr/bin/azureus), and add
 DEBUG_WRAPPER=1 just before run_java.
 i.e. DEBUG_WRAPPER=1 run_java -Dazureus.install.path=$HOME/.azureus $UI \
 org.gudy.azureus2.ui.common.Main $@

 Try launching azureus from command line then and paste the output in the bug.

OK; the output doesn't look at all like yours:

j...@vega:~$ azureus
[1] 24821
j...@vega:~$ [debug] /usr/bin/azureus: Environment variable
CLASSPATH is ''
[debug] /usr/bin/azureus: Runnning /usr/lib/java/bin/java
-classpath
/usr/lib/jni:/usr/lib/java:/usr/share/java/Azureus2.jar:/usr/share/java/log4j-1.2.jar:/usr/share/java/commons-cli.jar:/usr/share/java/swt.jar
-Dazureus.install.path=/home/jws/.azureus
org.gudy.azureus2.ui.common.Main
/usr/lib/java-wrappers/java-wrappers.sh: line 243:
/usr/lib/java/bin/java: No such file or directory
/usr/lib/java-wrappers/java-wrappers.sh: line 243: exec:
/usr/lib/java/bin/java: cannot execute: No such file or directory

[1]+  Exit 126azureus

BTW ls -al in /etc/alternatives gives:
java - /usr/lib/jvm/java-6-openjdk/jre/bin/java
java.1.gz - /usr/lib/jvm/java-6-openjdk/jre/man/man1/java.1.gz
javaws - /usr/lib/jvm/java-6-openjdk/jre/bin/javaws
javaws.1.gz - /usr/lib/jvm/java-6-openjdk/jre/man/man1/javaws.1.gz
libswt-3.4-java - /usr/share/java-config/libswt-gtk-3.4-java
mozilla-javaplugin.so -
/usr/lib/jvm/java-6-openjdk/jre/lib/i386/IcedTeaPlugin.so

And I CAN start azureus from command line by
 JAVA_CMD=/etc/alternatives/java azureus

or by exporting JAVA_CMD=/etc/alternatives/java before starting X.
 The output in such a case is:

j...@vega:~$ JAVA_CMD=/etc/alternatives/java azureus
[debug] /usr/bin/azureus: Environment variable CLASSPATH is ''
[debug] /usr/bin/azureus: Runnning /etc/alternatives/java
-classpath
/usr/lib/jni:/usr/lib/java:/usr/share/java/Azureus2.jar:/usr/share/java/log4j-1.2.jar:/usr/share/java/commons-cli.jar:/usr/share/java/swt.jar
-Dazureus.install.path=/home/jws/.azureus
org.gudy.azureus2.ui.common.Main
file:/usr/lib/jni/ ; file:/usr/lib/java/ ;
file:/usr/share/java/Azureus2.jar ;
file:/usr/share/java/log4j-1.2-1.2.15.jar ;
file:/usr/share/java/commons-cli-1.2.jar ;
file:/usr/lib/java/swt-gtk-3.4.2.jar ; file:/home/jws/
Core Start Completed

Unfortunately, this works only from the command line. Clicking on
a torrent link in a web page does not start azureus.

Regards, Jan




___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers


Bug#542392: azureus: Refuses to start

2009-08-19 Thread Adrian Perez
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 the script may be able to find them properly, and set them
locally for the script. 
Also, their use it's deprecated by the new java policy.

What's the output of update-java-alternatives -l along with the
priorities?

Paste the output of the following sequence:

  . /usr/lib/java-wrappers/java-wrappers.sh
  export JAVA_{HOME,CMD}=
  DEBUG_WRAPPER=1 find_java_runtime openjdk


You've tried to reset alternatives back with: 
update-alternatives -s java-6-openjdk

or (for runtime only),
update-java-alternatives --jre --set java-6-openjdk

Hope that helps.
-- 
Best regards,
Adrian Perez adrianperez@gmail.com


signature.asc
Description: This is a digitally signed message part
___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers

Bug#542392: Extra info

2009-08-19 Thread Jan Willem Stumpel
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


Bug#542392: azureus: Refuses to start

2009-08-19 Thread Jan Willem Stumpel
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 variables like
 JAVA_HOME or JAVA_CMD set, since the script may be able to find
 them properly, and set them locally for the script.

 Also, their use it's deprecated by the new java policy.

JAVA_HOME is set, to /usr/lib/java. I do not know where this is
set. JAVA_CMD is not normally set.

As to your other suggestions, I'll answer tomorrow (I have to get
up very early, so must hit the sack about now). BTW my previous
message must have crossed yours. Where can I read more about the
new java policy?

Regards, Jan



___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers


Bug#542392: azureus: Refuses to start

2009-08-19 Thread Adrian Perez
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 to
that path, is running bin/java, which in case your var is set correctly
that would be /usr/lib/jvm/java-6-openjdk/bin/java.
I'm pretty sure that's the root cause of that wrong behavior.

You don't need to do the extra steps (although they don't hurt at all),
you need to investigate is your JAVA_HOME is persistant, then who's
setting it. Check your ~/.bash* files, /etc/bash.bashrc, the like, you
know.

A downgrade to a previous version would of course work, because there
the azureus script was the hardcoded one, I think, although there's no
reason to failure after you have done what I've told you.

-- 
Best regards,
Adrian Perez adrianperez@gmail.com


signature.asc
Description: This is a digitally signed message part
___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers

Bug#507536: eclipse: undefined symbol: _ZN4nsID5ParseEPKc

2009-08-19 Thread Vincent Smeets
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
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
uppercase=bad)
||/ NameVersion Description
+++-===-===-==
un  xulrunner   none  (no
description available)
ii  xulrunner-1.9   1.9.0.11-0lenny1XUL + XPCOM
application runner
un  xulrunner-1.9-commonnone  (no
description available)
un  xulrunner-1.9-gnome-support none  (no
description available)


Regards,
Vincent


Niels Thykier wrote:
 Hi

 Those of you who have experienced this problem, could you please write
 which version of xulrunner you have and whether it fixed it?

 Those you still experiencing the problem, please check if your version
 of xulrunner is listed here[1] next to the matching version of eclipse.
 At least xulrunner 1.9.1 have broken backwards compatibility[2].

 ~Niels

 [1] http://www.eclipse.org/swt/faq.php#browserlinux
 [2] http://glandium.org/blog/?p=416

   



___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers


Bug#542511: maven-debian-helper: mh_lspoms fails with IOException: Cannot run program

2009-08-19 Thread Damien Raude-Morvan
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-
repo/org/apache/mina/build/1.1.7/build-1.1.7.pom 
dpkg : /usr/share/maven-repo/org/apache/mina/build/1.1.7/build-1.1.7.pom 
introuvable.
Cannot execute dpkg 
 
 dpkg --search /usr/bin/mvn
  
maven2: /usr/bin/mvn
 
Found maven2
 
 apt-file search /usr/share/maven-
repo/org/apache/mina/build/1.1.7/build-1.1.7.pom  
java.io.IOException: Cannot run program apt-file: java.io.IOException: 
error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:474)  
   
at 
org.debian.maven.packager.DependenciesSolver.executeProcess(DependenciesSolver.java:379)

at 
org.debian.maven.packager.DependenciesSolver.searchPkg(DependenciesSolver.java:365)
 
at 
org.debian.maven.packager.DependenciesSolver.resolveDependencies(DependenciesSolver.java:310)
   
at 
org.debian.maven.packager.DependenciesSolver.resolveDependencies(DependenciesSolver.java:251)
   
at 
org.debian.maven.packager.DependenciesSolver.resolveDependencies(DependenciesSolver.java:270)
   
at 
org.debian.maven.packager.DependenciesSolver.solveDependencies(DependenciesSolver.java:220)
 
at 
org.debian.maven.packager.DependenciesSolver.main(DependenciesSolver.java:518)  

Caused by: java.io.IOException: java.io.IOException: error=2, No such file or 
directory
at java.lang.UNIXProcess.init(UNIXProcess.java:164)   
   
at java.lang.ProcessImpl.start(ProcessImpl.java:81) 
   
at java.lang.ProcessBuilder.start(ProcessBuilder.java:467)  
   
... 7 more


Maybe a Recommends on apt-file should be added to package ?


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages maven-debian-helper depends on:
ii  default-jre [java2-runtime]   1.6-33 Standard Java or Java compatible 
R
ii  gcj-jre [java2-runtime]   4:4.3.3-9  Java runtime environment using 
GIJ
ii  java-gcj-compat [java2-runtim 1.0.80-5.1 Java runtime environment using 
GIJ
ii  libmaven-clean-plugin-java2.3-3  Maven clean plugin
ii  libmaven-compiler-plugin-java 2.0.2-4Maven compiler plugin
ii  libmaven-jar-plugin-java  2.2-4  Maven Jar plugin
ii  libmaven-resources-plugin-jav 2.3-5  Maven resources plugin
ii  libmaven-site-plugin-java 2.0-2  Maven Site Plugin for generating 
a
ii  libplexus-velocity-java   1.1.7-2Plexus component interface to 
velo
ii  libsurefire-java  2.4.3-3Surefire test framework for Java
ii  maven-repo-helper 0.7Helper tools for including Maven 
m
ii  maven22.2.0-2Java software project management 
a
ii  openjdk-6-jre [java2-runtime] 6b16-4 OpenJDK Java runtime, using 
Hotspo
ii  sun-java5-jre [java2-runtime] 1.5.0-20-1 Sun Java(TM) Runtime Environment 
(
ii  sun-java6-jre [java2-runtime] 6-15-1 Sun Java(TM) Runtime Environment 
(
ii  velocity  1.6.2-2Java-based template engine for 
web

maven-debian-helper recommends no packages.

Versions of packages maven-debian-helper suggests:
pn  libmaven-javadoc-plugin-java  none (no description available)

-- no debconf information

-- 
Damien Raude-Morvan / www.drazzib.com


signature.asc
Description: This is a digitally signed message part.
___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers