Opened 16 years ago

Closed 15 years ago

Last modified 15 years ago

#142 closed defect (invalid)

sage build shouldn't modify $HOME

Reported by: was Owned by: was
Priority: minor Milestone: sage-duplicate/invalid/wontfix
Component: packages: standard Keywords:
Cc: Merged in:
Authors: Reviewers:
Report Upstream: Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges



Yep... My $HOME/.sage belonged to "root". I have no idea why that happened either... Maybe I used a "sudo" when I shouldn't... (But I really think I just used to "make".) In any case, a "sudo chown -R" fixed it.

Yes, this is a known bug in the install process. SAGE get's run during the install, which can cause some problems like you just had if the user doing the build is root but the $HOME for root is not /root.

William }}}

Change History (3)

comment:1 Changed 15 years ago by mabshoff

  • Milestone set to Sage-2.10

comment:2 Changed 15 years ago by was

  • Resolution set to invalid
  • Status changed from new to closed

Sage should *definitely* be allowed to run during the build. That's just the way it is.

comment:3 Changed 15 years ago by mabshoff

  • Milestone changed from Sage-2.10 to sage-duplicate/invalid
Note: See TracTickets for help on using tickets.