Your message dated Wed, 1 Mar 2017 18:34:23 +0100
with message-id <ed7262ca-5d27-9086-61e8-03c3865e4...@ninthfloor.org>
and subject line Re: Bug#856409: proguard: Please relax the dependency on 
proguard-gui
has caused the Debian Bug report #856409,
regarding proguard: Please relax the dependency on proguard-gui
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.)


-- 
856409: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856409
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: proguard
Severity: normal

Dear Maintainer,

The packages depending on the 'proguard' package normally need the
command line version only. This means that it is impossible to install
such packages on a headless server without bringing it several (~150)
unused GUI dependencies.

Please consider lowering the dependency on proguard-gui to a
Recommend, thus allowing existing packages to keep the dependency on
proguard while not enforcing the installation of proguard-gui.

Thank you,

Paride

--- End Message ---
--- Begin Message ---
On 2017-02-28 19:41, Emmanuel Bourg wrote:
> Le 28/02/2017 à 18:59, Paride Legovini a écrit :
> 
>> Even better: as most packages with a hard dependency on proguard really
>> depend only on the library, you could let this package Recommend: both
>> proguard-cli and proguard-gui.
> 
> The packages using only the library should depend on libproguard-java.

Agreed, closing this bug.
Thank you.

Paride

--- End Message ---
__
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 discussions and questions.

Reply via email to