Your message dated Wed, 21 Nov 2007 07:06:17 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#452229: Dependency on "lynx"
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: arno-iptables-firewall
Version: 1.8.8.i-1
I noticed that the package depends on "lynx" for some reason. However,
I do not understand, for what reason exactly does
arno-iptables-firewall would need lynx. I do not use lynx, and would
like not having to keep it installed. Also, no other package on my
system depends on it.
Can you please explain the reason for this dependency? Maybe it could
be removed? Or at least, please consider adding an alternate
dependency for "links", which is what, I am sure, quite some people
would prefer to having on their systems instead of lynx.
Thanks in advance.
--- End Message ---
--- Begin Message ---
Hi,
On Wed, Nov 21, 2007 at 10:09:27AM +0500, RM wrote:
> Package: arno-iptables-firewall
> Version: 1.8.8.i-1
>
> I noticed that the package depends on "lynx" for some reason. However,
> I do not understand, for what reason exactly does
> arno-iptables-firewall would need lynx. I do not use lynx, and would
> like not having to keep it installed. Also, no other package on my
> system depends on it.
>
> Can you please explain the reason for this dependency? Maybe it could
> be removed? Or at least, please consider adding an alternate
> dependency for "links", which is what, I am sure, quite some people
> would prefer to having on their systems instead of lynx.
The dependency is there, because the included 'arno-fwfilter' tool
contains a hardcoded call to lynx. Alternative dependencies would not
work without patching the sources. So even if I do it, I'm not sure that
I don't get a bug report asking 'Why not use lynx instead of foo as
upstream does...' ;-)
For this reason I will close this bug now. However, if there are reason
for switching away from lynx (other than personal preferences), please
let me know and I will talk to upstream whether we can do the switch for
everybody.
Alternatively I will evaluate whether a Recommends instead of Depends
would do it. You get rid of lynx, but you'd also loose 'arno-fwfilter'.
Thanks,
Michael
--
GPG key: 1024D/3144BE0F Michael Hanke
http://apsy.gse.uni-magdeburg.de/hanke
ICQ: 48230050
signature.asc
Description: Digital signature
--- End Message ---
