Your message dated Mon, 28 Sep 2009 21:15:16 +0200
with message-id <[email protected]>
and subject line Re: Bug#500840: liboro-java should depend only on -headless 
java runtime packages
has caused the Debian Bug report #500840,
regarding liboro-java should depend only on -headless java runtime packages
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 [email protected]
immediately.)


-- 
500840: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500840
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: liboro-java
Version: 2.0.8a-4
Severity: wishlist


Hi,

can liboro-java depend only on -headless java runtime packages?

Ubuntu has it allready done this way, therefore I assume it should work:
-> http://packages.ubuntu.com/de/intrepid/i386/liboro-java

Greetings,
Kolja.


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

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

Versions of packages liboro-java depends on:
pn  java-common                   <none>     (no description available)

liboro-java recommends no packages.

liboro-java suggests no packages.



--- End Message ---
--- Begin Message ---
Version: 2.0.8a-5


On Wed, Oct 01, 2008 at 11:25:20PM +0200, Kolja Nowak wrote:
> Package: liboro-java
> Version: 2.0.8a-4
> Severity: wishlist
> 
> 
> Hi,
> 
> can liboro-java depend only on -headless java runtime packages?
> 
> Ubuntu has it allready done this way, therefore I assume it should work:
> -> http://packages.ubuntu.com/de/intrepid/i386/liboro-java

This fix was applied in 2.0.8a-5 already and not closed automatically.
Doing now.


Cheers,
Michael


--- End Message ---

Reply via email to