Bug 452047 - Installation from PlaneT repository fails: cache directories not writable
Installation from PlaneT repository fails: cache directories not writable
Product: Fedora
Classification: Fedora
Component: plt-scheme (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Gérard Milmeister
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-06-18 18:58 EDT by Michel Alexandre Salim
Modified: 2009-07-14 11:21 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-14 11:21:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michel Alexandre Salim 2008-06-18 18:58:44 EDT
Description of problem:
Trying to use a PlaneT package would fail, as PLT Scheme tries to compile the
files and store the results in non-writable directories

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

How reproducible:

Steps to Reproduce:
1. rm -rf ~/.plt-scheme/planet (otherwise, the second time installation is
attempted, planet does not reattempt the previous failed steps)
2. From mzscheme or drscheme, type in REPL:
(require (planet "test.ss" ("schematics" "schemeunit.plt" 2 10)))
Actual results:
open-output-file: cannot open output file:
"/usr/lib64/plt/collects/config/compiled/config_ss.zo" (Permission denied; errno=13)
setup-plt: error: during making for <planet>/schematics/schemeunit.plt/2/10
setup-plt:   open-output-file: cannot open output file:
"/usr/lib64/plt/collects/config/compiled/config_ss.zo" (Permission denied; errno=13)
Internal PLaneT error: trying to install already-installed package

Expected results:
Should just work

Additional info:
Comment 1 Michel Alexandre Salim 2008-06-18 21:21:33 EDT
Eli Barzilay helped debugging this; the culprit is that some files were deleted,
either because they are of size 0 (Eli pointed out that one such file is used
merely for its executable permission, as a stub to which scripts are appended
to), and the files that are removed because they contain the buildroot.

I'm currently working out how to get the buildroot out. It looks like some of
the Makefiles wrongly assume that DESTDIR is where the package will end up
permanently, instead of just a packaging temporary. Eugh.
Comment 2 Michel Alexandre Salim 2008-06-18 23:16:23 EDT
Reported upstream: http://bugs.plt-scheme.org/query/?cmd=view&pr=9524
Comment 3 Gérard Milmeister 2008-09-17 10:23:17 EDT
I built the new version 4.1 for rawhide.
The buildroot is still in. For now I disabled
buildroot checking, and it seems that everything
runs fine. All platforms have been built
successfully, but x86_64 is built using -O1
instead of -O2 (it should be possible to find
out what optimization flag exactly breaks the
built, but this takes time), and ppc64 is built
using --enable-cgcdefault.
Please try it out. Maybe we can reduce some
of the modifications to the optflags.
Comment 4 Michel Alexandre Salim 2008-10-08 17:07:19 EDT
I've not tested it heavily, but it seems to work. There is a problem with SELinux, though -- /usr/bin/mred needs its context to be unconfined_execmem_exec_t, otherwise thousands of AVC denial messages get generated in a very short time span. Do you think this can be addressed, or should one of us file a request bug against selinux-policy-targeted?
Comment 5 Gérard Milmeister 2008-10-08 18:27:36 EDT
On F-9 I don't get any selinux messages, maybe this
is specific to rawhide? (I checked that allow_execmem=0)
Comment 6 Bug Zapper 2009-06-09 21:41:36 EDT
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: 
Comment 7 Bug Zapper 2009-07-14 11:21:55 EDT
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.