Hi Fyodor On Mon, Aug 17, 2009 at 10:38:11PM -0700, Fyodor wrote: > On Tue, Aug 18, 2009 at 06:59:51AM +0200, Ola Lundqvist wrote: > > > > As I'm the maintainer (and actually creator now when I look in the > > chnagelog) > > of ndiff and do not really have a problem to get that package removed. > > The "old ndiff" (ndiff package) is old as you Fyodor states. > > Thanks Ola. Even though the Nmap project now has an official, > supported ndiff tool, we do appreciate your efforts in packaging this > 3rd party ndiff for all these years!
You are perfectly welcome. I must say that it has not been much work as you can see from my changelog. I had actually forgot that I was the one that created it. :-) > > So the following needs to be done: > > 1) Update nmap to "conflict" and "provide" ndiff (at least conflict). > > This part will solve this bug and must be done in any case, as we have > > ndiff in the archive now and people can have it installed already (like > > me). > > I'm not a Debian developer, but maybe someone else can do this? I > only follow the Debian Nmap bug tracker since I'm the author and > maintainer of Nmap. Oh, I see. I'm adding the nmap maintainer to the list of email receipiants. > > 2) Please check whether the ndiff script works in the same way as the > > "old ndiff". > > They serve the same purpose (show the difference between two Nmap > scans), but I haven't used "old ndiff" in many years. > > > > 2) Please check whether the nrun and ngen scripts work with the new nmap. > > Given how much Nmap has changed in the last 8 years (and these scripts > haven't), they at best work on a small subset of Nmap features. I > haven't tried them for the better part of a decade. Well neither have I... With that statement I think we can skip those scripts. > > If it does, you can merge that code to nmap. > > As these third party scripts are unrelated to the Nmap Project, we > don't think they should be merged with Debian's Nmap package. Even > the original author no longer supports them, and we don't want to > either. Ok. Perfectly fine with me. > > If it do not work we need to remove ndiff package anyway. > > 3) File a bug against ftp.debian.org requesting the removal of the package. > > If the ftp team needs my approval before it is removed, please Cc me and > > I'll answer that. > > > > Would this be ok with you? > > That sounds good although I think a Debian developer should do it. Have added the nmap maintainer to the recipient so he can do that. > By the way, we have no problem with old ndiff continuing as a package, > but we think the name of the package and script executable should be > changed to avoid conflicting. For example, the package could become > "nwatch" or "nrun" or "ngen" and the ndiff script could become > ndiff.pl. Removing the package entirely is another reasonable option. > We believe that most people trying to "apt get ndiff" are expecting > the official supported Nmap project Ndiff tool which we've been > promoting, and not an 8 year old set of unmaintained Perl scripts. I see. Well that may be true, but wouldn't they download the nmap package firstly? In any case as you state that ndiff has changed a lot in the recent years I think we should remove the ndiff package anyway as it would not work. Unmaintained software is not good to keep in the archive unless some Debian developer continue to maintain it. As I'm the maintainer and I do not regularly test it against nmap (which obviously changes) I think it is better to remove the ndiff package alltogether. But first we need to make the conflict in nmap to solve the main concern. Please file a bug against ftp.debian.org requesting the removal of ndiff and refer to http://bugs.debian.org/542054 so they know that I agree. Best regards, // Ola > Thanks, > Fyodor > -- --- Inguza Technology AB --- MSc in Information Technology ---- / o...@inguza.com Annebergsslingan 37 \ | o...@debian.org 654 65 KARLSTAD | | http://inguza.com/ Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --------------------------------------------------------------- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
