RE: Process to adopt moribund packages?

Contacting the current maintainer should IMO always be the (obvious) first step - if you feel the package is neglected, ask if he would mind if you'd take over. The reason I think it's been abandoned is that there's been a more recent upstream version for about two and a half years now.

Process to adopt moribund packages?

Is there a process for a prospective Debian developer to adopt a package that's not been updated for a long time? I know the current package maintainer can file an RFA, or orphan the package, but is there a process for a new maintainer to take the package over if the current maintainer doesn't

Problem with package build-depends against libpcap-dev - is this a bug?

I'm having problems building nmap and xprobe from source because of build-depends on libpcap-dev. I need to build these two packages from source because I have local patches that I want to apply to the source code before it's compiled. I'm running sarge on i386 and have libpcap0.8-dev

Re: Problem with package build-depends against libpcap-dev - isthis a bug?

Roy Hills [EMAIL PROTECTED] wrote: I'm running sarge on i386 and have libpcap0.8-dev installed, which allows both nmap and xprobe to build without error if I use dpkg-buildpackage -d to override the dependency check. Do the programs also run without problems?Yes, there are no problems running