Your message dated Sat, 5 Sep 2015 16:51:18 -0400
with message-id <[email protected]>
and subject line Re: Bug#99538: bind-dev: Missing symlinks for some man pages
has caused the Debian Bug report #99538,
regarding bind-dev: Missing symlinks for some man pages
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
99538: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=99538
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bind-dev
Severity: normal
Hi,
An upcoming release of Debian policy, version 3.5.5.0, contains an amendment
which clarifies the way man pages need to be installed.
Until now, packages could install /usr/share/man/man1/foo.1.gz with 'foo,
bar \- programs to do something' in the NAME section and have no
corresponding symbolic link from bar.1.gz (policy suggested using a symbolic
link, but wasn't clear that it's required), and our man program happened to
magically figure it out for itself and display the right man page when you
typed 'man bar'. However, guaranteeing that this would work even when you've
recently installed some new packages has a serious performance impact on
man, as it frequently has to go and look through the filesystem to update
its database.
Before woody's base system is frozen, I intend to remove this "feature" from
man-db, so that its performance is consistent and acceptable for a
reasonable number of people. It isn't a standard feature even among the
various man page browsers in Debian, let alone in other Linux distributions,
so there should be no compatibility problems. However, your package seems to
rely on it, so this bug is being filed to let you know that the way some of
your man pages are installed needs to be improved in order to work properly
in woody. All you need to do, if you already have, say, foo(1) and expect
bar(1) to work as well, is install a symbolic link to foo.1.gz as bar.1.gz
(.so links and hard links are also OK, though symlinks are recommended).
Here's a list of man pages and the names that don't appear anywhere in the
filesystem:
usr/share/man/man3/getaddrinfo.3bind.gz: gai_strerror
usr/share/man/man3/getaddrinfo.3bind.gz: getaddrinfo freeaddrinfo
usr/share/man/man3/gethostbyname.3bind.gz: endhostent
usr/share/man/man3/gethostbyname.3bind.gz: gethostbyaddr
usr/share/man/man3/gethostbyname.3bind.gz: gethostent
usr/share/man/man3/gethostbyname.3bind.gz: herror
usr/share/man/man3/gethostbyname.3bind.gz: sethostent
usr/share/man/man3/getipnodebyname.3bind.gz: getipnodebyaddr
usr/share/man/man3/getnetent.3bind.gz: endnetent
usr/share/man/man3/getnetent.3bind.gz: getnetbyaddr
usr/share/man/man3/getnetent.3bind.gz: getnetbyname
usr/share/man/man3/getnetent.3bind.gz: setnetent
usr/share/man/man3/hesiod.3bind.gz: hesiod_end
usr/share/man/man3/hesiod.3bind.gz: hesiod_free_list
usr/share/man/man3/hesiod.3bind.gz: hesiod_init
usr/share/man/man3/hesiod.3bind.gz: hesiod_resolve
usr/share/man/man3/hesiod.3bind.gz: hesiod_to_bind
usr/share/man/man3/inet_cidr.3bind.gz: inet_cidr_ntop
usr/share/man/man3/inet_cidr.3bind.gz: inet_cidr_pton
usr/share/man/man3/resolver.3bind.gz: dn_comp
usr/share/man/man3/resolver.3bind.gz: dn_expand
usr/share/man/man3/resolver.3bind.gz: fp_nquery
usr/share/man/man3/resolver.3bind.gz: fp_resstat
usr/share/man/man3/resolver.3bind.gz: herror
usr/share/man/man3/resolver.3bind.gz: hostalias
usr/share/man/man3/resolver.3bind.gz: hstrerror
usr/share/man/man3/resolver.3bind.gz: p_query
usr/share/man/man3/resolver.3bind.gz: res_close
usr/share/man/man3/resolver.3bind.gz: res_findzonecut
usr/share/man/man3/resolver.3bind.gz: res_hostalias
usr/share/man/man3/resolver.3bind.gz: res_init
usr/share/man/man3/resolver.3bind.gz: res_isourserver
usr/share/man/man3/resolver.3bind.gz: res_mkquery
usr/share/man/man3/resolver.3bind.gz: res_nclose
usr/share/man/man3/resolver.3bind.gz: res_ninit
usr/share/man/man3/resolver.3bind.gz: res_nmkquery
usr/share/man/man3/resolver.3bind.gz: res_nmkupdate
usr/share/man/man3/resolver.3bind.gz: res_nquery
usr/share/man/man3/resolver.3bind.gz: res_nquerydomain
usr/share/man/man3/resolver.3bind.gz: res_nsearch
usr/share/man/man3/resolver.3bind.gz: res_nsend
usr/share/man/man3/resolver.3bind.gz: res_nsendsigned
usr/share/man/man3/resolver.3bind.gz: res_nupdate
usr/share/man/man3/resolver.3bind.gz: res_ourserver_p
usr/share/man/man3/resolver.3bind.gz: res_pquery
usr/share/man/man3/resolver.3bind.gz: res_query
usr/share/man/man3/resolver.3bind.gz: res_querydomain
usr/share/man/man3/resolver.3bind.gz: res_search
usr/share/man/man3/resolver.3bind.gz: res_send
usr/share/man/man3/resolver.3bind.gz: res_update
usr/share/man/man3/tsig.3bind.gz: ns_find_tsig
usr/share/man/man3/tsig.3bind.gz: ns_sign
usr/share/man/man3/tsig.3bind.gz: ns_sign_tcp
usr/share/man/man3/tsig.3bind.gz: ns_sign_tcp_init
usr/share/man/man3/tsig.3bind.gz: ns_verify
usr/share/man/man3/tsig.3bind.gz: ns_verify_tcp
usr/share/man/man3/tsig.3bind.gz: ns_verify_tcp_init
If the list looks odd, please check man(7) to see if the man page is
formatted properly. This output was generated by way of mandb, so if it's
confused then users will be too; if it turns out that it's done the wrong
thing, please reassign this bug to man-db so that I can fix it. I might not
have caught symlinks that are created in the postinst (say, using
alternatives); if that's the case, please close this bug.
Please see bug #94995 and policy 3.5.5 section 13.1 for more information,
and feel free to contact me if you need help.
Thanks,
--
Colin Watson, via a script
--- End Message ---
--- Begin Message ---
Hi, Colin:
The manpages referenced below belonged to the old "libbind" resolver
code that was shipped in BIND8. The BIND9 source distribution also
included a copy of libbind until BIND 9.6.0, but I don't believe it was
ever shipped in any of the binary packages built by src:bind9.
Since these manpages no longer exist in the Debian archive (though many
of them have been superseded by similarly named manpages from other
packages), I'm closing this bug.
Colin Watson wrote:
> Package: bind-dev
> Severity: normal
>
> Hi,
>
> An upcoming release of Debian policy, version 3.5.5.0, contains an amendment
> which clarifies the way man pages need to be installed.
>
> Until now, packages could install /usr/share/man/man1/foo.1.gz with 'foo,
> bar \- programs to do something' in the NAME section and have no
> corresponding symbolic link from bar.1.gz (policy suggested using a symbolic
> link, but wasn't clear that it's required), and our man program happened to
> magically figure it out for itself and display the right man page when you
> typed 'man bar'. However, guaranteeing that this would work even when you've
> recently installed some new packages has a serious performance impact on
> man, as it frequently has to go and look through the filesystem to update
> its database.
>
> Before woody's base system is frozen, I intend to remove this "feature" from
> man-db, so that its performance is consistent and acceptable for a
> reasonable number of people. It isn't a standard feature even among the
> various man page browsers in Debian, let alone in other Linux distributions,
> so there should be no compatibility problems. However, your package seems to
> rely on it, so this bug is being filed to let you know that the way some of
> your man pages are installed needs to be improved in order to work properly
> in woody. All you need to do, if you already have, say, foo(1) and expect
> bar(1) to work as well, is install a symbolic link to foo.1.gz as bar.1.gz
> (.so links and hard links are also OK, though symlinks are recommended).
>
> Here's a list of man pages and the names that don't appear anywhere in the
> filesystem:
>
> usr/share/man/man3/getaddrinfo.3bind.gz: gai_strerror
> usr/share/man/man3/getaddrinfo.3bind.gz: getaddrinfo freeaddrinfo
> usr/share/man/man3/gethostbyname.3bind.gz: endhostent
> usr/share/man/man3/gethostbyname.3bind.gz: gethostbyaddr
> usr/share/man/man3/gethostbyname.3bind.gz: gethostent
> usr/share/man/man3/gethostbyname.3bind.gz: herror
> usr/share/man/man3/gethostbyname.3bind.gz: sethostent
> usr/share/man/man3/getipnodebyname.3bind.gz: getipnodebyaddr
> usr/share/man/man3/getnetent.3bind.gz: endnetent
> usr/share/man/man3/getnetent.3bind.gz: getnetbyaddr
> usr/share/man/man3/getnetent.3bind.gz: getnetbyname
> usr/share/man/man3/getnetent.3bind.gz: setnetent
> usr/share/man/man3/hesiod.3bind.gz: hesiod_end
> usr/share/man/man3/hesiod.3bind.gz: hesiod_free_list
> usr/share/man/man3/hesiod.3bind.gz: hesiod_init
> usr/share/man/man3/hesiod.3bind.gz: hesiod_resolve
> usr/share/man/man3/hesiod.3bind.gz: hesiod_to_bind
> usr/share/man/man3/inet_cidr.3bind.gz: inet_cidr_ntop
> usr/share/man/man3/inet_cidr.3bind.gz: inet_cidr_pton
> usr/share/man/man3/resolver.3bind.gz: dn_comp
> usr/share/man/man3/resolver.3bind.gz: dn_expand
> usr/share/man/man3/resolver.3bind.gz: fp_nquery
> usr/share/man/man3/resolver.3bind.gz: fp_resstat
> usr/share/man/man3/resolver.3bind.gz: herror
> usr/share/man/man3/resolver.3bind.gz: hostalias
> usr/share/man/man3/resolver.3bind.gz: hstrerror
> usr/share/man/man3/resolver.3bind.gz: p_query
> usr/share/man/man3/resolver.3bind.gz: res_close
> usr/share/man/man3/resolver.3bind.gz: res_findzonecut
> usr/share/man/man3/resolver.3bind.gz: res_hostalias
> usr/share/man/man3/resolver.3bind.gz: res_init
> usr/share/man/man3/resolver.3bind.gz: res_isourserver
> usr/share/man/man3/resolver.3bind.gz: res_mkquery
> usr/share/man/man3/resolver.3bind.gz: res_nclose
> usr/share/man/man3/resolver.3bind.gz: res_ninit
> usr/share/man/man3/resolver.3bind.gz: res_nmkquery
> usr/share/man/man3/resolver.3bind.gz: res_nmkupdate
> usr/share/man/man3/resolver.3bind.gz: res_nquery
> usr/share/man/man3/resolver.3bind.gz: res_nquerydomain
> usr/share/man/man3/resolver.3bind.gz: res_nsearch
> usr/share/man/man3/resolver.3bind.gz: res_nsend
> usr/share/man/man3/resolver.3bind.gz: res_nsendsigned
> usr/share/man/man3/resolver.3bind.gz: res_nupdate
> usr/share/man/man3/resolver.3bind.gz: res_ourserver_p
> usr/share/man/man3/resolver.3bind.gz: res_pquery
> usr/share/man/man3/resolver.3bind.gz: res_query
> usr/share/man/man3/resolver.3bind.gz: res_querydomain
> usr/share/man/man3/resolver.3bind.gz: res_search
> usr/share/man/man3/resolver.3bind.gz: res_send
> usr/share/man/man3/resolver.3bind.gz: res_update
> usr/share/man/man3/tsig.3bind.gz: ns_find_tsig
> usr/share/man/man3/tsig.3bind.gz: ns_sign
> usr/share/man/man3/tsig.3bind.gz: ns_sign_tcp
> usr/share/man/man3/tsig.3bind.gz: ns_sign_tcp_init
> usr/share/man/man3/tsig.3bind.gz: ns_verify
> usr/share/man/man3/tsig.3bind.gz: ns_verify_tcp
> usr/share/man/man3/tsig.3bind.gz: ns_verify_tcp_init
>
> If the list looks odd, please check man(7) to see if the man page is
> formatted properly. This output was generated by way of mandb, so if it's
> confused then users will be too; if it turns out that it's done the wrong
> thing, please reassign this bug to man-db so that I can fix it. I might not
> have caught symlinks that are created in the postinst (say, using
> alternatives); if that's the case, please close this bug.
>
> Please see bug #94995 and policy 3.5.5 section 13.1 for more information,
> and feel free to contact me if you need help.
>
> Thanks,
>
> --
> Colin Watson, via a script
--
Robert Edmonds
[email protected]
--- End Message ---
