Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #222916 > unrolled thread

Debian man pages have annoying feature(sic)

Back to article view | Back to linux.debian.user

Contents

  Debian man pages have annoying feature(sic) Richard Owlett <rowlett@cloud85.net> - 2020-05-30 12:00 +0200
    Re: Debian man pages have annoying feature(sic) <tomas@tuxteam.de> - 2020-05-30 13:00 +0200
      Re: Debian man pages have annoying feature(sic) Richard Owlett <rowlett@cloud85.net> - 2020-05-30 15:40 +0200
    Re: Debian man pages have annoying feature(sic) Richard Owlett <rowlett@cloud85.net> - 2020-05-30 15:50 +0200
      Re: Debian man pages have annoying feature(sic) The Wanderer <wanderer@fastmail.fm> - 2020-05-30 16:20 +0200
    Re: Debian man pages have annoying feature(sic) l0f4r0@tuta.io - 2020-05-30 16:20 +0200
      Re: Debian man pages have annoying feature(sic) <tomas@tuxteam.de> - 2020-05-30 17:00 +0200
        Re: Debian man pages have annoying feature(sic) Richard Owlett <rowlett@cloud85.net> - 2020-05-30 17:10 +0200
          Re: Debian man pages have annoying feature(sic) David Wright <deblis@lionunicorn.co.uk> - 2020-05-30 23:10 +0200
            Re: Debian man pages have annoying feature(sic) Andrei POPESCU <andreimpopescu@gmail.com> - 2020-06-01 09:00 +0200
            Re: Debian man pages have annoying feature(sic) Richard Owlett <rowlett@cloud85.net> - 2020-06-02 13:20 +0200
              Re: Debian man pages have annoying feature(sic) Brian <ad44@cityscape.co.uk> - 2020-06-02 16:40 +0200
              Re: Debian man pages have annoying feature(sic) David Wright <deblis@lionunicorn.co.uk> - 2020-06-02 17:10 +0200
    Re: Debian man pages have annoying feature(sic) Andrei POPESCU <andreimpopescu@gmail.com> - 2020-05-30 16:50 +0200
    Re: Debian man pages have annoying feature(sic) Ralph Katz <ralph@ralphkatz.com> - 2020-06-01 23:20 +0200
      Re: Debian man pages have annoying feature(sic) Richard Owlett <rowlett@cloud85.net> - 2020-06-02 00:10 +0200
        Re: Debian man pages have annoying feature(sic) Bob Weber <bobrweber@gmail.com> - 2020-06-02 00:30 +0200
        Re: Debian man pages have annoying feature(sic) l0f4r0@tuta.io - 2020-06-02 01:00 +0200
        Something is buggy - was [Re: Debian man pages have annoying  feature(sic)] Richard Owlett <rowlett@cloud85.net> - 2020-06-02 15:10 +0200
          Re: Something is buggy - was [Re: Debian man pages have annoying  feature(sic)] The Wanderer <wanderer@fastmail.fm> - 2020-06-02 15:50 +0200
            Re: Something is buggy - was [Re: Debian man pages have annoying  feature(sic)] Richard Owlett <rowlett@cloud85.net> - 2020-06-02 17:50 +0200
              Re: Something is buggy - was [Re: Debian man pages have annoying  feature(sic)] Andrei POPESCU <andreimpopescu@gmail.com> - 2020-06-03 07:30 +0200
          Re: Something is buggy - was [Re: Debian man pages have annoying  feature(sic)] l0f4r0@tuta.io - 2020-06-02 16:30 +0200
    [CLARIFICATION] Re: Debian man pages have annoying feature(sic) Richard Owlett <rowlett@cloud85.net> - 2020-06-02 12:40 +0200
      Re: [CLARIFICATION] Re: Debian man pages have annoying feature(sic) Dan Ritter <dsr@randomstring.org> - 2020-06-02 14:40 +0200
    Re: Debian man pages have annoying feature(sic) Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2020-06-02 16:40 +0200

Page 1 of 2  [1] 2  Next page →

#222916 — Debian man pages have annoying feature(sic)

I the recent thread about returning a Debian installation to its 
original state "popularity-contest" was mentioned.

I wished to compare it to other tools mentioned in that thread.
Obvious stating point -- read the man page.
As I never installed its package I went to 
https://manpages.debian.org/buster/popularity-contest/popularity-contest.8.en.html 
.

It did not explicitly answer my question.
However, under "SEE ALSO" it stated:
> Additional documentation is in /usr/share/doc/popularity-contest/.

*PROBLEM*
As package is not installed, that directory does *NOT* exist.

Where to find required documentation on the web?

NOTE BENE
This post is about man pages as a class.

[toc] | [next] | [standalone]

#222917

[Multipart message — attachments visible in raw view] — view raw

On Sat, May 30, 2020 at 04:52:47AM -0500, Richard Owlett wrote:
> I the recent thread about returning a Debian installation to its
> original state "popularity-contest" was mentioned.
> 
> I wished to compare it to other tools mentioned in that thread.
> Obvious stating point -- read the man page.
> As I never installed its package I went to https://manpages.debian.org/buster/popularity-contest/popularity-contest.8.en.html
> .
> 
> It did not explicitly answer my question.
> However, under "SEE ALSO" it stated:
> >Additional documentation is in /usr/share/doc/popularity-contest/.
> 
> *PROBLEM*
> As package is not installed, that directory does *NOT* exist.
> 
> Where to find required documentation on the web?
> 
> NOTE BENE
> This post is about man pages as a class.

Of course, it would be nice to have everything in the man page.
That is in general difficult, since upstream doesn't always
do it this way -- packaging isn't the place to change that.

That said, it's possible to browse Debian packages sources
in the 'net.

I'll show how to do it based on your concrete example.

First, the structure of a source package doesn't correspond
to the installed binary package; the reference given in the
above "SEE ALSO" is relative to the binary package. So first
you have a look at popularity-contest's "list of files", that's
in <https://packages.debian.org/> (I'm assuming buster):

  https://packages.debian.org/buster/all/popularity-contest/filelist

(Of course you can click your way through to this URL).

You can see that in /usr/share/doc/... there is a FAQ, a README,
a changelog, a copyright and a subdirectory examples.

Now you go to the corresponding place in <https://sources.debian.org/>:

  https://sources.debian.org/src/popularity-contest/1.67/

There they are: FAQ, README and examples (the two missing ones
are Debian infrastructure and live in the subdir debian).

Note that it won't work this way always and 100%, because
package installation /might/ do some magic, which you may
look up in debian/rules, debian/postinst, etc. -- but that's
it, more or less.

Enjoy
-- tomás

[toc] | [prev] | [next] | [standalone]

#222919

On 05/30/2020 05:57 AM, tomas@tuxteam.de wrote:
> On Sat, May 30, 2020 at 04:52:47AM -0500, Richard Owlett wrote:
>> I the recent thread about returning a Debian installation to its
>> original state "popularity-contest" was mentioned.
>>
>> I wished to compare it to other tools mentioned in that thread.
>> Obvious stating point -- read the man page.
>> As I never installed its package I went to https://manpages.debian.org/buster/popularity-contest/popularity-contest.8.en.html
>> .

_Clarification by OP_

I had not installed popularity-contest _for cause_:
   a. its phone-home feature violates my security & privacy policy.
   b. it would pull in unneeded packages which might interfere with
      intentionally installed package(s) to serve similar functions.

>>
>> It did not explicitly answer my question.
>> However, under "SEE ALSO" it stated:
>>> Additional documentation is in /usr/share/doc/popularity-contest/.
>>
>> *PROBLEM*
>> As package is not installed, that directory does *NOT* exist.
>>
>> Where to find required documentation on the web?
>>
>> NOTE BENE
>> This post is about man pages as a class.
> 
> Of course, it would be nice to have everything in the man page.
> That is in general difficult, since upstream doesn't always
> do it this way -- packaging isn't the place to change that.
> 
> That said, it's possible to browse Debian packages sources
> in the 'net.
> 
> I'll show how to do it based on your concrete example.
> 
> First, the structure of a source package doesn't correspond
> to the installed binary package; the reference given in the
> above "SEE ALSO" is relative to the binary package. So first
> you have a look at popularity-contest's "list of files", that's
> in <https://packages.debian.org/> (I'm assuming buster):
> 
>    https://packages.debian.org/buster/all/popularity-contest/filelist
> 
> (Of course you can click your way through to this URL).

I strongly recommend that methodology to those reading this thread 
because they have a similar problem. I suspect that in the long term, 
having followed the intervening links and cross references will prove 
more valuable than the targeted final URLs.

> 
> You can see that in /usr/share/doc/... there is a FAQ, a README,
> a changelog, a copyright and a subdirectory examples.
> 
> Now you go to the corresponding place in <https://sources.debian.org/>:
> 
>    https://sources.debian.org/src/popularity-contest/1.67/
> 
> There they are: FAQ, README and examples (the two missing ones
> are Debian infrastructure and live in the subdir debian).
> 
> Note that it won't work this way always and 100%, because
> package installation /might/ do some magic, which you may
> look up in debian/rules, debian/postinst, etc. -- but that's
> it, more or less.
> 
> Enjoy
> -- tomás
> 

Thank you.

[toc] | [prev] | [next] | [standalone]

#222920

On 05/30/2020 06:14 AM, Peter Hillier-Brook wrote:
> On 30/05/2020 10:52, Richard Owlett wrote:
>> I the recent thread about returning a Debian installation to its
>> original state "popularity-contest" was mentioned.
>>
>> I wished to compare it to other tools mentioned in that thread.
>> Obvious stating point -- read the man page.
>> As I never installed its package I went to
>> https://manpages.debian.org/buster/popularity-contest/popularity-contest.8.en.html
>> .
>>
>> It did not explicitly answer my question.
>> However, under "SEE ALSO" it stated:
>>> Additional documentation is in /usr/share/doc/popularity-contest/.
>>
>> *PROBLEM*
>> As package is not installed, that directory does *NOT* exist.
>>
>> Where to find required documentation on the web?
>>
>> NOTE BENE
>> This post is about man pages as a class.
> 
> `sudo apt install popularity-contest`

Not always a good idea -- see my reply to Tomas.
Not always physically possible -- a non-privileged user may benefit from 
the documentation of an uninstalled package.

> 
> then read the manual.
> 
> 
> 

[toc] | [prev] | [next] | [standalone]

#222923

[Multipart message — attachments visible in raw view] — view raw

On 2020-05-30 at 09:45, Richard Owlett wrote:

> On 05/30/2020 06:14 AM, Peter Hillier-Brook wrote:
> 
>> On 30/05/2020 10:52, Richard Owlett wrote:

>>> *PROBLEM* As package is not installed, that directory does *NOT*
>>> exist.
>>> 
>>> Where to find required documentation on the web?
>>> 
>>> NOTE BENE This post is about man pages as a class.
>> 
>> `sudo apt install popularity-contest`
> 
> Not always a good idea -- see my reply to Tomas. Not always
> physically possible -- a non-privileged user may benefit from the
> documentation of an uninstalled package.

Possible workarounds for that scenario:

* 'apt-get source popularity-contest', find the source of the file
you're looking for in the resulting directory, and read that

* download the .deb from snapshot.debian.org, extract it with 'dpkg -x
filename.deb directory-to-extract-into', find the file you're looking
for in the resulting directory, and read that

There are possibly others.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

[toc] | [prev] | [next] | [standalone]

#222921

Hi,

30 mai 2020 à 13:14 de phb@hbsys.plus.com:

> `sudo apt install popularity-contest`
>
> then read the manual.
>
I think the OP doesn't want to install the package, otherwise there would be no question ;)
I would suggest the following instead:

1) create a directory (a temp one if you prefer):
mkdir popularity-contest-doc && cd popularity-contest-doc

2) download the package:
apt download popularity-contest

3) extract the /usr/share/doc/popularity-contest part (you need to adjust the version package X.YY):
dpkg --fsys-tarfile popularity-contest_X.YY_all.deb | tar x --directory . ./usr/share/doc/popularity-contest

4) read what you want in the usr/share/doc/popularity-contest/ subfolder

Of course, the method indicated by Tomas is great and may be easier than mine (+ doesn't leave Debian package files on your computer).

Best regards,
l0f4r0

[toc] | [prev] | [next] | [standalone]

#222925

[Multipart message — attachments visible in raw view] — view raw

On Sat, May 30, 2020 at 04:13:22PM +0200, l0f4r0@tuta.io wrote:

[...]

> I would suggest the following instead:

[download + unpack]

> Of course, the method indicated by Tomas is great and may be easier than mine (+ doesn't leave Debian package files on your computer).

I don't think "my" method is easier. Personally, I'd go with yours
any time (I dislike browsers) -- but I had the impression (wrongly?)
that the OP wanted a "webby" solution. But thanks for chiming in
with alternatives!

Cheers
-- t

[toc] | [prev] | [next] | [standalone]

#222926

On 05/30/2020 09:50 AM, tomas@tuxteam.de wrote:
> On Sat, May 30, 2020 at 04:13:22PM +0200, l0f4r0@tuta.io wrote:
> 
> [...]
> 
>> I would suggest the following instead:
> 
> [download + unpack]
> 
>> Of course, the method indicated by Tomas is great and may be easier than mine (+ doesn't leave Debian package files on your computer).
> 
> I don't think "my" method is easier. Personally, I'd go with yours
> any time (I dislike browsers) -- but I had the impression (wrongly?)
> that the OP wanted a "webby" solution. But thanks for chiming in
> with alternatives!
> 

Yes. A "webby" solution can have two benefits in my environment:
   a. may minimize download downloaded byte count.
   b. following intervening links and cross references can lead to
      answering important un-asked questions.

[toc] | [prev] | [next] | [standalone]

#222933

On Sat 30 May 2020 at 10:08:41 (-0500), Richard Owlett wrote:
> On 05/30/2020 09:50 AM, tomas@tuxteam.de wrote:
> > On Sat, May 30, 2020 at 04:13:22PM +0200, l0f4r0@tuta.io wrote:
> > 
> > [...]
> > 
> > > I would suggest the following instead:
> > 
> > [download + unpack]
> > 
> > > Of course, the method indicated by Tomas is great and may be easier than mine (+ doesn't leave Debian package files on your computer).
> > 
> > I don't think "my" method is easier. Personally, I'd go with yours
> > any time (I dislike browsers) -- but I had the impression (wrongly?)
> > that the OP wanted a "webby" solution. But thanks for chiming in
> > with alternatives!
> > 
> 
> Yes. A "webby" solution can have two benefits in my environment:
>   a. may minimize download downloaded byte count.
>   b. following intervening links and cross references can lead to
>      answering important un-asked questions.

For man pages, I type   man foo   into google. That usually throws
up one or two links from different sources.

For this specific package, where I don't know the foo to type,
I googled   debian popularity contest   which got me plenty of
hits, including a load of graphs that it can produce, its
(section 8) man page, the wiki (which has a reference to the FAQ),
and the Debian packages page for popularity-contest.

The last of these (which is obviously already in my FF bookmarks)
gives you links to the package's download page, and you can download
it with that link from different mirrors. I usually paste the address
into wget, if it works (which preserves the metadata), but you
can just click it instead.

Then, as mentioned already, just press Return on the .deb file in
Midnight Commander to look at any files in the package.

I thought most people knew how to use the web like this, for
documentation on anything and (almost) everything.

If there were any chance I'd use the package, I'd download it via
apt, to get it cached, and known to apt. But that requires root.

I hope none of this violates your policy (or, as I would put it,
disagrees with your preferences).

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#222960

[Multipart message — attachments visible in raw view] — view raw

On Sb, 30 mai 20, 16:05:54, David Wright wrote:
> 
> For man pages, I type   man foo   into google. That usually throws
> up one or two links from different sources.

I have/had these configured as search engines in Firefox (Vimium):

dpkg: https://packages.debian.org/search?keywords=%s
(Understands binary package names only)

bts: https://bugs.debian.org/%s
(Understands binary package names, source package names with 
src:<package>, and bug numbers)

pts: https://packages.qa.debian.org/%s
dpt: https://tracker.debian.org/%s
(These will show source packages only, but can search by binary or 
source package names. The PTS has been superseded by Tracker)

man: https://manpages.debian.org/%s
(Understands man pages only)
 
> If there were any chance I'd use the package, I'd download it via
> apt, to get it cached, and known to apt. But that requires root.

'apt download <package>' works also without root privileges because it 
downloads to the current directory (not APT's cache).

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#223003

On 05/30/2020 04:05 PM, David Wright wrote:
> On Sat 30 May 2020 at 10:08:41 (-0500), Richard Owlett wrote:
>> On 05/30/2020 09:50 AM, tomas@tuxteam.de wrote:
>>> On Sat, May 30, 2020 at 04:13:22PM +0200, l0f4r0@tuta.io wrote:
>>>
>>> [...]
>>>
>>>> I would suggest the following instead:
>>>
>>> [download + unpack]
>>>
>>>> Of course, the method indicated by Tomas is great and may be easier than mine (+ doesn't leave Debian package files on your computer).
>>>
>>> I don't think "my" method is easier. Personally, I'd go with yours
>>> any time (I dislike browsers) -- but I had the impression (wrongly?)
>>> that the OP wanted a "webby" solution. But thanks for chiming in
>>> with alternatives!
>>>
>>
>> Yes. A "webby" solution can have two benefits in my environment:
>>    a. may minimize download downloaded byte count.
>>    b. following intervening links and cross references can lead to
>>       answering important un-asked questions.
> 
> For man pages, I type   man foo   into google. That usually throws
> up one or two links from different sources.
> [snip]

You missed my point entirely. I have accessed the man page via 
https://manpages.debian.org/ . It lacks information *CRITICAL* to 
whether or not to install the package. It skirts the issue by referring 
to a file which will exist, *if and only if*, the package has already 
been installed. I.E. classical infinite loop ;}

[toc] | [prev] | [next] | [standalone]

#223016

On Tue 02 Jun 2020 at 06:13:00 -0500, Richard Owlett wrote:

> On 05/30/2020 04:05 PM, David Wright wrote:
> > On Sat 30 May 2020 at 10:08:41 (-0500), Richard Owlett wrote:
> > > On 05/30/2020 09:50 AM, tomas@tuxteam.de wrote:
> > > > On Sat, May 30, 2020 at 04:13:22PM +0200, l0f4r0@tuta.io wrote:
> > > > 
> > > > [...]
> > > > 
> > > > > I would suggest the following instead:
> > > > 
> > > > [download + unpack]
> > > > 
> > > > > Of course, the method indicated by Tomas is great and may be easier than mine (+ doesn't leave Debian package files on your computer).
> > > > 
> > > > I don't think "my" method is easier. Personally, I'd go with yours
> > > > any time (I dislike browsers) -- but I had the impression (wrongly?)
> > > > that the OP wanted a "webby" solution. But thanks for chiming in
> > > > with alternatives!
> > > > 
> > > 
> > > Yes. A "webby" solution can have two benefits in my environment:
> > >    a. may minimize download downloaded byte count.
> > >    b. following intervening links and cross references can lead to
> > >       answering important un-asked questions.
> > 
> > For man pages, I type   man foo   into google. That usually throws
> > up one or two links from different sources.
> > [snip]
> 
> You missed my point entirely. I have accessed the man page via
> https://manpages.debian.org/ . It lacks information *CRITICAL* to whether or
> not to install the package. It skirts the issue by referring to a file which
> will exist, *if and only if*, the package has already been installed. I.E.
> classical infinite loop ;}

'apt download <package>' has been mentioned a few times. The package
may be opened and the contents of /usr/share/doc/<package> viewed.
This takes all of two minutes. Is there something lacking in this
technique? Too simple and straightforward, perhaps?

-- 
Brian

[toc] | [prev] | [next] | [standalone]

#223020

On Tue 02 Jun 2020 at 06:13:00 (-0500), Richard Owlett wrote:
> On 05/30/2020 04:05 PM, David Wright wrote:
> > On Sat 30 May 2020 at 10:08:41 (-0500), Richard Owlett wrote:
> > > On 05/30/2020 09:50 AM, tomas@tuxteam.de wrote:
> > > > On Sat, May 30, 2020 at 04:13:22PM +0200, l0f4r0@tuta.io wrote:
> > > > 
> > > > [...]
> > > > 
> > > > > I would suggest the following instead:
> > > > 
> > > > [download + unpack]
> > > > 
> > > > > Of course, the method indicated by Tomas is great and may be easier than mine (+ doesn't leave Debian package files on your computer).
> > > > 
> > > > I don't think "my" method is easier. Personally, I'd go with yours
> > > > any time (I dislike browsers) -- but I had the impression (wrongly?)
> > > > that the OP wanted a "webby" solution. But thanks for chiming in
> > > > with alternatives!
> > > > 
> > > 
> > > Yes. A "webby" solution can have two benefits in my environment:
> > >    a. may minimize download downloaded byte count.
> > >    b. following intervening links and cross references can lead to
> > >       answering important un-asked questions.
> > 
> > For man pages, I type   man foo   into google. That usually throws
> > up one or two links from different sources.
> > [snip]
> 
> You missed my point entirely. I have accessed the man page via
> https://manpages.debian.org/ . It lacks information *CRITICAL* to
> whether or not to install the package. It skirts the issue by
> referring to a file which will exist, *if and only if*, the package
> has already been installed. I.E. classical infinite loop ;}

My References header includes two of you posts. The first says

    "NOTE BENE This post is about man pages as a class"

and the second says

    "A "webby" solution can have two benefits in my environment"

as seen above. I ignored your little complaint about a specific man
page; instead, I addressed the Debian man pages in the subject line,
and particularly when the name of the command or package is hazy.

Thanks to Andrei for the list of references.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#222924

[Multipart message — attachments visible in raw view] — view raw

On Sb, 30 mai 20, 04:52:47, Richard Owlett wrote:
> 
> *PROBLEM*
> As package is not installed, that directory does *NOT* exist.

Midnight Commander (and probably other file managers as well) can browse 
downloaded .deb files.

    apt download popularity-contest
    mc (browse the CONTENTS directory)

Hope this helps,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#222985

On 5/30/20 3:52 AM, Richard Owlett wrote:
...
> *PROBLEM*
> As package is not installed, that directory does *NOT* exist.
> 
> Where to find required documentation on the web?
> 
> NOTE BENE
> This post is about man pages as a class.
> 

apt show debian-goodies
...
debman     - Easily view man pages from a binary .deb without extracting
               [man, apt* (via debget)]

So...  ~$ dman packagename   # will fetch the manpages as though they
were local.

Regards,
Ralph

[toc] | [prev] | [next] | [standalone]

#222987

On 06/01/2020 04:02 PM, Ralph Katz wrote:
> On 5/30/20 3:52 AM, Richard Owlett wrote:
> ...
>> *PROBLEM*
>> As package is not installed, that directory does *NOT* exist.
>>
>> Where to find required documentation on the web?
>>
>> NOTE BENE
>> This post is about man pages as a class.
>>
> 
> apt show debian-goodies
> ...
> debman     - Easily view man pages from a binary .deb without extracting
>                 [man, apt* (via debget)]
> 
> So...  ~$ dman packagename   # will fetch the manpages as though they
> were local.
> 
> Regards,
> Ralph


Thank you. Looks interesting.
1st didn't work even after installing debian-goodies.
Suspect operator. Leaving now. will pursue in morning.

[toc] | [prev] | [next] | [standalone]

#222988

[Multipart message — attachments visible in raw view] — view raw

On 6/1/20 6:02 PM, Richard Owlett wrote:
> On 06/01/2020 04:02 PM, Ralph Katz wrote:
>> On 5/30/20 3:52 AM, Richard Owlett wrote:
>> ...
>>> *PROBLEM*
>>> As package is not installed, that directory does *NOT* exist.
>>>
>>> Where to find required documentation on the web?
>>>
>>> NOTE BENE
>>> This post is about man pages as a class.
>>>
>>
>> apt show debian-goodies
>> ...
>> debman     - Easily view man pages from a binary .deb without extracting
>>                 [man, apt* (via debget)]
>>
>> So...  ~$ dman packagename   # will fetch the manpages as though they
>> were local.
>>
>> Regards,
>> Ralph
>
>
> Thank you. Looks interesting.
> 1st didn't work even after installing debian-goodies.
> Suspect operator. Leaving now. will pursue in morning


Try the online manuals at https://manpages.debian.org/ 
<https://manpages.debian.org/> .


-- 


*...Bob*

[toc] | [prev] | [next] | [standalone]

#222990

Hi,

2 juin 2020 à 00:02 de rowlett@cloud85.net:

> On 06/01/2020 04:02 PM, Ralph Katz wrote:
>
>> apt show debian-goodies
>> ...
>> debman     - Easily view man pages from a binary .deb without extracting
>>  [man, apt* (via debget)]
>>
>> So...  ~$ dman packagename   # will fetch the manpages as though they
>> were local.
>>
>> Regards,
>> Ralph
>>
> Thank you. Looks interesting.
> 1st didn't work even after installing debian-goodies.
> Suspect operator. Leaving now. will pursue in morning.
>
Are you speaking of debman? If so I suspect you forgot the last part with the command you want its manpages.
In short, you have multiple possibilities:

dman cmd
debman -f local_package.deb cmd
debman -p package cmd
debmany package|local_package.deb

Best regards,
l0f4r0

[toc] | [prev] | [next] | [standalone]

#223007 — Something is buggy - was [Re: Debian man pages have annoying feature(sic)]

On 06/01/2020 05:02 PM, Richard Owlett wrote:
> On 06/01/2020 04:02 PM, Ralph Katz wrote:
>> On 5/30/20 3:52 AM, Richard Owlett wrote:
>> ...
>>> *PROBLEM*
>>> As package is not installed, that directory does *NOT* exist.
>>>
>>> Where to find required documentation on the web?
>>>
>>> NOTE BENE
>>> This post is about man pages as a class.
>>>
>>
>> apt show debian-goodies
>> ...
>> debman     - Easily view man pages from a binary .deb without extracting
>>                 [man, apt* (via debget)]
>>
>> So...  ~$ dman packagename   # will fetch the manpages as though they
>> were local.
>>
>> Regards,
>> Ralph
> 
> 
> Thank you. Looks interesting.
> 1st didn't work even after installing debian-goodies.
> Suspect operator. Leaving now. will pursue in morning.

I am running Debian 9.8 with MATE desktop

Synaptic reports:
> Commit Log for Mon Jun  1 16:45:47 2020
> Installed the following packages:
> curl (7.52.1-5+deb9u9)
> dctrl-tools (2.24-2+b1)
> debian-goodies (0.69.1)
> libcurl3 (7.52.1-5+deb9u9)
> 

Copy and paste this morning from MATE terminal
> richard@defaultinstall:~$ dman gforth
> bash: dman: command not found
> richard@defaultinstall:~$ debman gforth
> Usage: debman [options] [-- man(1) options] <man page name> ...
> 
> Options should be exactly one of:
>         -f package.deb          read pages from package.deb archive
>         -p package              download .deb for package and read pages
>                                 from there
> richard@defaultinstall:~$ debman -p gforth
> Usage: debman [options] [-- man(1) options] <man page name> ...
> 
> Options should be exactly one of:
>         -f package.deb          read pages from package.deb archive
>         -p package              download .deb for package and read pages
>                                 from there
> richard@defaultinstall:~$ debman -f gforth.deb
> Usage: debman [options] [-- man(1) options] <man page name> ...
> 
> Options should be exactly one of:
>         -f package.deb          read pages from package.deb archive
>         -p package              download .deb for package and read pages
>                                 from there
> richard@defaultinstall:~$ 

I have verified that both
https://manpages.debian.org/stretch/gforth/gforth.1.en.html
   and
https://manpages.debian.org/buster/gforth/gforth.1.en.html

Help please.
TIA

[toc] | [prev] | [next] | [standalone]

#223011 — Re: Something is buggy - was [Re: Debian man pages have annoying feature(sic)]

[Multipart message — attachments visible in raw view] — view raw

On 2020-06-02 at 09:05, Richard Owlett wrote:

> On 06/01/2020 05:02 PM, Richard Owlett wrote:
>
>> On 06/01/2020 04:02 PM, Ralph Katz wrote:

>>> apt show debian-goodies
>>> ...
>>> debman     - Easily view man pages from a binary .deb without extracting
>>>                 [man, apt* (via debget)]
>>>
>>> So...  ~$ dman packagename   # will fetch the manpages as though they
>>> were local.
>>>
>>> Regards,
>>> Ralph
>> 
>> 
>> Thank you. Looks interesting.
>> 1st didn't work even after installing debian-goodies.
>> Suspect operator. Leaving now. will pursue in morning.

> Copy and paste this morning from MATE terminal
>> richard@defaultinstall:~$ dman gforth
>> bash: dman: command not found
>> richard@defaultinstall:~$ debman gforth
>> Usage: debman [options] [-- man(1) options] <man page name> ...
>> 
>> Options should be exactly one of:
>>         -f package.deb          read pages from package.deb archive
>>         -p package              download .deb for package and read pages
>>                                 from there
>> richard@defaultinstall:~$ debman -p gforth
>> Usage: debman [options] [-- man(1) options] <man page name> ...
>> 
>> Options should be exactly one of:
>>         -f package.deb          read pages from package.deb archive
>>         -p package              download .deb for package and read pages
>>                                 from there
>> richard@defaultinstall:~$ debman -f gforth.deb
>> Usage: debman [options] [-- man(1) options] <man page name> ...
>> 
>> Options should be exactly one of:
>>         -f package.deb          read pages from package.deb archive
>>         -p package              download .deb for package and read pages
>>                                 from there
>> richard@defaultinstall:~$ 
> 
> I have verified that both
> https://manpages.debian.org/stretch/gforth/gforth.1.en.html
>    and
> https://manpages.debian.org/buster/gforth/gforth.1.en.html
> 
> Help please.

I've dug into this, and while I thought at first there was a bug here
myself, I've figured it out.

The command lines you're giving are specifying the package name, but not
the name of the man page. The "<man page name>" argument at the end of
the usage section is not optional.

For example,

$ debman -p gforth vmgen

works fine for me.

If you need to find out the name of the actual man page (since, e.g., it
isn't intuitively obvious that gforth will contain a man page for the
name 'vmgen'), something like

$ apt-file show gforth | grep /man/

ought to do it; just drop the leading path (up through the final '/')
and the trailing ".X.gz" (where X is a number) from each filename, and
it should be a valid man-page argument to debman.

(I'm not sure what it will do if there's a package which installs two
man pages with the same name but different sections, because I haven't
yet found any examples of packages which do that.)

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web