#6146 yum provides should account for --excludedocs
Closed: Invalid None Opened 8 years ago by dachary.

{{{%packages --excludedocs --instLangs=en --nocore}}} prevents manual pages from being installed. Still, yum leads the user to believe they will be installed. Forcing the installation of the manual pages or even tracing the reason for the man pages to be absent requires knowledge that is beyond what most user have. There should be so kind of hint in yum provides output to explain this is not a problem.

{{{
$ docker run -t -i fedora:21 bash

yum provides /usr/share/man/man1/ls.1.gz

fedora/21/x86_64/filelists_db | 25 MB 00:00:01
updates/21/x86_64/filelists_db | 13 MB 00:00:00
coreutils-8.22-19.fc21.x86_64 : A set of basic GNU tools commonly used in shell scripts
Repo : fedora
Matched from:
Filename : /usr/share/man/man1/ls.1.gz
coreutils-8.22-19.fc21.x86_64 : A set of basic GNU tools commonly used in shell scripts
Repo : @anaconda
Matched from:
Filename : /usr/share/man/man1/ls.1.gz

yum install coreutils

Package coreutils-8.22-19.fc21.x86_64 already installed and latest version
Nothing to do

ls -l /usr/share/man/man1/ls.1.gz

ls: cannot access /usr/share/man/man1/ls.1.gz: No such file or directory

yum install man

man ls

No manual entry for ls
}}}

See also https://fedorahosted.org/rel-eng/ticket/6145


This is not the place to report bugs again "yum" or any other package. This is for release engineering related requests.

Replying to [comment:1 pbrobinson]:

This is not the place to report bugs again "yum" or any other package. This is for release engineering related requests.

Where do you suggest I file this bug ? yum developers will probably reply that the way the docker fedora container is configured is not their concern. Or is it ? I feel my efforts to report this useability issue are causing anger and that you resent my attempts to help. Please accept my apologies for any inconvenience I may have caused.

The proper place to report these bugs are on bugzilla: https://bugzilla.redhat.com
There you would be in contact with the people actually having the power and responsibilities of the components you are concerned about.

Thanks for the report, it's always appreciated but it will be more useful on bugzilla than here :)

Replying to [comment:3 pingou]:

The proper place to report these bugs are on bugzilla: https://bugzilla.redhat.com
There you would be in contact with the people actually having the power and responsibilities of the components you are concerned about.

Thanks for the report, it's always appreciated but it will be more useful on bugzilla than here :)

:-) There are many projects and fields: https://bugzilla.redhat.com/enter_bug.cgi asks me to chose between a number of class. Is it "Community" ? It could be since maybe the fedora docker image, although "official" may only be supported as a community effort and not by paid employees. Or it could be "Fedora". But it's more a fedora installation than the Fedora distribution itself so Fedora packagers may end up telling me that it's not a matter of packaging but a matter of how the distribution is instantiated. If it's really officially supported in the sense that it's a Red Hat product, then I should probably go there.

I'm explaining all this to highlight that this landing page raises non trivial questions for someone willing to report a bug. Of course I could learn the exact meaning of this classification, although there is no "help" or "for more informaiton" link on the page. But that's likely to take at least half an hour, probably more if I get interested in the ecosystem.

If I chose the Fedora class, I land at https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora and need to chose a OS and Hardware, none of which has the docker keyword which leads me to believe I'm not where I should be.

I went ahead anyway and filled https://bugzilla.redhat.com/show_bug.cgi?id=1211170, half expecting to be bounced.

Please let me know if I should report this bug in a more appropriate place, I'd like my fourth attempt to be the right one ;-)

Login to comment on this ticket.

Metadata