newinstall.sh downloads to /tmp/conda_packages.txt , causing user conflicts

Description

We are seeing that "newinstall.sh" performs a curl of conda_packages.txt within the MiniConda installation to /tmp/conda_packages.txt . This file is always left there (I believe), or at the very least can be stranded there with a failed or truncated installation. This can 'lock out' of others, causing build failures say on a machine like lsstdev if a file like

[daues@lsst-dev ~]$ ls -l /tmp/conda_packages.txt
rw-rw-r- 1 moeyensj moeyensj 928 Feb 23 10:03 /tmp/conda_packages.txt

gets left behind. The error looks like :

it would seem more prudent for the file to be downloaded to
/tmp/conda_packages_${USER}.txt or /tmp/conda_packages_$$.txt
or something similar.

Checklist

Lucidchart Diagrams

Issue Matrix

hide

Activity

Greg Daues February 24, 2016 at 3:20 PM

I see stack building with newinstall.sh to succeed on lsstdev in the presence of
a formerly hostile /tmp/conda_packages.txt , so the issue looks completely resolved.

Joshua Hoblitt February 24, 2016 at 3:00 PM

I'm going to close this ticket but please feel free to reopen it if you encounter a related problem.

Joshua Hoblitt February 24, 2016 at 2:59 PM

Joshua Hoblitt February 24, 2016 at 2:56 PM

travis passes after the publish: https://travis-ci.org/lsst/lsst/builds/111580388

Joshua Hoblitt February 24, 2016 at 2:44 PM

published miniconda2-3.19.0.lsst3 from b1938

Done
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Reviewers

Kian-Tat Lim
Tim Jenness

Story Points

RubinTeam

Components

Checklist

Created February 23, 2016 at 10:57 AM
Updated February 24, 2016 at 3:20 PM
Resolved February 24, 2016 at 3:00 PM