On Sat, May 2, 2009 at 12:23 AM, Matthias Julius <m...@julius-net.net> wrote:
> As explained in another post this should not affect the user since the > database format has not changed. Please investigate the DB->upgrade thing Clint mentioned and forward that upstream, with a patch if you are able. > I have not done anything about this. How much harm does this actually > do? At least this does not cause extra package dependancy because > libm comes with libc6. Very minimal, it just means dnshistory loads more libraries than it needs to and therefore uses slightly more RAM than it could. I suggest ignoring it for now, but sending a patch upstream for them to include in their VCS and the next release. > I think it might be appropriate to elevate this pedantic notice to > info level. I'm not sure if I agree, but please file a bug on lintian if you think that is the case. > I would welcome if you could have a look at the new package which is > at the same location on mentors: > > http://mentors.debian.net/debian/pool/main/d/dnshistory/dnshistory_1.3-2.dsc Uploaded, thanks for your contriibution to Debian :) Please mail this list for future uploads and I will upload if I am able. It might be a good idea to make a patch that either sets the path in doc/dnshistory.1 based on the parameters to ./configure or removes the path from the manual page and send that upstream, so that less distributions need to patch that file or care about patching it. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
