Closed lmoureaux closed 6 years ago
bdorney
commented
6 years ago Before we accept this bug can you try on one of the 904 daq machines? We updated most of them to cc7 so you may need to ask @jsturdy to place your account back on the machines.
jsturdy
commented
6 years ago If you must try to develop on lxplus, your option at this time is to pip install --user the missing packages
lmoureaux
commented
6 years ago Tried to make rpm in various environments, on branch develop:
| Environment | Python | Installed Packages | Result |
|---|---|---|---|
Vanilla lxplus |
2.6 | importlib 'setuptools<39.2.0' 'pip<10.1.0' |
:-1: (log)¹ |
importlib 'setuptools<38' 'pip<10.1.0' |
:+1: | ||
lxplus with² LCG 93 |
2.7 | None | :-1: (log) |
cc7 (gem904qc8daq)³ |
2.7 | None | :-1: (log) |
cc7 (gem904daq01) |
2.7 | importlib setuptools pip |
:+1: |
slc6 (gem904daq03) |
2.6 | importlib 'setuptools<38' 'pip<10.1.0' |
:+1: |
:+1: means that make rpm exited with exit code 0. I didn't check the produced packages.
There is a pattern:
rpm tools always use it, which makes total sense for system packaging)slc6 machines require pip install --user importlib 'setuptools<38' 'pip<10.1.0'cc7 machines require pip install --user importlib setuptools pipDidn't try at P5.
Closing as it's more of a documentation issue, and hence is a duplicate of #96.
Brief summary of issue
Even though
lxplusisn't a supported development environment, some of the tools cannot be run on the P5 machines (eg because they require cluster access). Developing and testing on different machines would be painful.make rpmcrashes onlxplus.Types of issue
Expected Behavior
make rpmworks on lxplus.Current Behavior
As recommended, the following wasn't done in a
virtualenv:Steps to Reproduce (for bugs)
See the above section.
Context (for feature requests)
Developing for #105. See also the Summary above.
Your Environment
developbash