Bug 433222 – gcc - libgcj update gets complaints from install-info

Bug 433222 - gcc - libgcj update gets complaints from install-info

Summary:	gcc - libgcj update gets complaints from install-info

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	gcc (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	All Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Jakub Jelinek
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2008-02-17 14:44 EST by Michal Jaegermann
Modified:	2008-02-19 11:14 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2008-02-19 11:14:33 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Michal Jaegermann 2008-02-17 14:44:38 EST

Description of problem:

An update to libgcj-4.3.0-0.9 causes the following:

install-info: menu item `Classpath Tools' already exists, for file `tools'

And inddeed there in /usr/share/info/dir there is already an entry:

* Classpath Tools: (tools).       GNU Classpath Tools Guide

Only an info file 'tools' does not exist anymore so this is "dead".
There is now 'cp-tools' but an attempt to crete a corresponding
entry failed as above.

One of possible way out would be to check for a failure of
/sbin/install-info in a %post script and if that happens just
try to edit /usr/share/info/dir (with 'sed -i ...', for example).

Version-Release number of selected component (if applicable):
libgcj-4.3.0-0.9

Comment 1 Jakub Jelinek 2008-02-19 11:14:33 EST

Should be fixed in libgcj-4.3.0-0.10.  As the problematic dir entries
were just in libgcj-4.3.0-0.[1-9], not even in some alpha release, adding a
%prein  workaround would be an overkill.

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