Hi Steffen and all,

today while talking with a backbox project administrator I discovered that 
popular tools such as openvas directly calls the amap binary.

I never talked with them, but I don't think it is feasible to ask to every 
security tool provider to patch their code for the only debian benefit.

I think I'm then changing again my opinion: the conflict field might be the 
only proper way to be sure such popular tools (not packaged in debian and some 
of them not even free) continue to work.

Is this one a good reason for a conflict?

Thanks for reading,

Gianfranco, who really don't want this kind of flame wars in such a beautiful 
project as debian.

Sent from Yahoo Mail on Android

Reply via email to