Bug 442701 - postinstall scriptlet tries to write into non-existent directory
Summary: postinstall scriptlet tries to write into non-existent directory
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: R-waveslim
Version: 9
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
Assignee: José Matos
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-16 11:15 UTC by Karsten Hopp
Modified: 2009-07-14 17:59 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-07-14 17:59:31 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Karsten Hopp 2008-04-16 11:15:25 UTC
Description of problem:
  Installier: R-waveslim                   ################### [2276/6284]
/var/tmp/rpm-tmp.23310: line 1: /usr/lib64/R/doc/html/search/index.txt: Datei
oder Verzeichnis nicht gefunden
Fehler: %post(R-waveslim-1.6.1-2.fc9.x86_64) Skriptlet fehlgeschlagen,
Beenden-Status 1

Version-Release number of selected component (if applicable):
R-waveslim-1.6.1-2.fc9

You're either missing a Requires(post) on some other package providing the
/usr/lib64/R/doc/html/search/ directory (although I haven't found one) or you
need to create that directory before you attempt to write any files there.
But in that case you also need to make sure that the directory get cleaned up
after deinstallation.

Comment 1 José Matos 2008-04-16 12:11:11 UTC
I guess that due to Spot's work the documentation now is in
/usr/lib/R/doc/html/search/ (notice that the 64 is missing). If that is the
case it should be easy to fix.

Since I don't have an x86_64 at hand could you confirm this or else I will do
it later at home.

Comment 2 Karsten Hopp 2008-04-16 12:30:46 UTC
It looks like he moved it to %doc:
> rpm -qpl R-2.6.2-1.fc9.i386.rpm | grep index.txt
/usr/share/doc/R-2.6.2/html/search/index.txt


> rpm -qpl R-2.6.2-1.fc9.x86_64.rpm | grep index.txt
/usr/share/doc/R-2.6.2/html/search/index.txt

Comment 3 Bug Zapper 2008-05-14 09:31:29 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2009-06-10 00:13:05 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2009-07-14 17:59:31 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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