at bottom :-
On 22/04/2017, Antoine Beaupre <anar...@debian.org> wrote:
> On Thu, Mar 23, 2017 at 02:55:51PM +0000, Ian Jackson wrote:
>> Michael Stapelberg writes ("Re: Bug#851885: Please add pseudopackage
>> `manpages.debian.org'"):
>> > Oh, I m not planning to create any bugs. I m working with GitHub. iwj@
>> > wanted
>> > this pseudo-package to be created, and I agreed to accept bug reports
>> > via the
>> > pseudo package, while continuing to use GitHub as the canonical issue
>> > tracker.
>>
>> As an example, my personal todo list has an entry to make the code
>> behind manpages.debian.org automatically serve up its own source in
>> its output. The result of that would be a patch or pull request which
>> I would like to submit as a bug to the Debian BTS.
>
> That sounds like something that should be reported against the upstream
> repository on Github, but I guess it's fine if it's reported against
> manpages.debian.org if you absolutely don't want to use Github. :)
>
> Should that issue be created now then? I seem to understand that Don
> wanted us to create an issue *before* he creates the pseudo-package. I'm
> not too familiar with how the internals of the BTS works, so maybe I
> misunderstood...
>
> A.
>
Hi all,
I too am unfamiliar with the internals of how the BTS works. This bug
was prompted by me, see https://github.com/Debian/debiman/issues/52
when I came to know that Ian Jackson has reported it just a week
before.
I don't really want to use github for something which should be under
debian infrastructure. It feels/felt wrong to use github to report
issues with debiman when its job/work is to present debian man pages
for us i.e. users of Debian
In a somewhat larger context, it would be also useful for newbies who
want to ask for a manpage for a package and dunno it needs to be filed
under the package with a wishlist priority.
One specific use-case is to get more accurate searching methods and
having more details as to how to search and get the most out of the
search-engine. There currently isn't any documentation to tell how to
use the search-engine.
Another issue/use-case is having stats about number of man-pages
relative to binary packages. I know and have seen that binary packages
have more than one binary tool, seeing total number of /bin/* and
/usr/bin/* for any single architecture and see manpages for that
architecture. IIRC the number is somewhere in the early 20's.
manpages.debian.org could be instrumental in sharing that information
by way of stats as well as linking to off-line tools or/and online
tools so more manpages are created and they are also current. Also
I'm not sure if all man-pages have been converted to HTML.
I do see that manpages.debian.org has started incorporating source
package dates https://manpages.debian.org/jessie/coreutils/ls.1.en.html
So have given 2-3 bugs above any of which could be used to create
manpages.debian.org psuedopackage.
Look forward to its creation.
--
Regards,
Shirish Agarwal शिरीष अग्रवाल
My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
