Bug 515948 - Errors installing glibc-devel-2.10.1-2.i586 with --excludedocs
Summary: Errors installing glibc-devel-2.10.1-2.i586 with --excludedocs
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Andreas Schwab
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 516757
TreeView+ depends on / blocked
 
Reported: 2009-08-06 11:24 UTC by Alexander Todorov
Modified: 2016-11-24 16:13 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-08-10 13:34:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Alexander Todorov 2009-08-06 11:24:54 UTC
Description of problem:
When installing with --excludedocs there are errors caused by missing files.

Version:
glibc-devel-2.10.1-2.i586

How reproducible:
Always

Steps to reproduce:
1) rpm -ihv --excludedocs glibc-devel-2.10.1-2.i586  

or:
- use %packages --excludedocs in kickstart
- enable %_excludedocs macro in RPM

Expected results:
Package is installed without errors

Actual results:
Error(s): Installing glibc-devel-2.10.1-2.i586
install-info: No such file or directory for /usr/share/info/libc.info.gz

Additional info:
This bug is automatically filed with python-bugzilla and component assignment may be incorrect.

Comment 1 Andreas Schwab 2009-08-06 12:49:54 UTC
This does not preclude installation since the error is ignored.

Comment 2 Alexander Todorov 2009-08-06 13:16:38 UTC
It is a problem for QE since we expect clean output from installation. You can either redirect error messages to /dev/null or better use something like:
[ -f /.../file.info.gz ] && install-info ....

Comment 3 Andreas Schwab 2009-08-06 13:37:20 UTC
What is QE and why does it do that?

Comment 4 Alexander Todorov 2009-08-07 08:09:35 UTC
QE == Quality Engineering

We want clean logs because otherwise people think there are errors with their installation. This is particularly true for RHEL products but clean logs is always a nice thing to have.

Please also see this thread:
https://www.redhat.com/archives/fedora-packaging/2009-August/msg00028.html

As far as I can tell folks generally agree that this needs to be fixed in one way or another.

Comment 5 Andreas Schwab 2009-08-10 13:34:27 UTC
Fixed in 2.10.90-13.


Note You need to log in before you can comment on or make changes to this bug.