If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Source tarballs contain psutil temporary files

NEW
Unassigned

Status

()

Core
Build Config
5 years ago
3 months ago

People

(Reporter: glandium, Unassigned)

Tracking

(Blocks: 1 bug)

Trunk
x86_64
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
For instance, the 19.0b6 source tarball contains these files:
  python/psutil/_psutil_linux.so                                
  python/psutil/_psutil_posix.so                                
  python/psutil/build/lib.linux-i686-2.7/_psutil_linux.so       
  python/psutil/build/lib.linux-i686-2.7/_psutil_posix.so       
  python/psutil/build/temp.linux-i686-2.7/psutil/_psutil_linux.o
  python/psutil/build/temp.linux-i686-2.7/psutil/_psutil_posix.o

Surely, it's bad that we create these files in the source directory, but we're kind of mitigating with .hgignore. Maybe we should hg purge --all or something like that before creating the tarballs?
Good idea, I guess this is related to the new-ish virtualenv stuff that happens as part of the build? We actually just call a packaging target to do this: https://mxr.mozilla.org/mozilla-central/source/toolkit/mozapps/installer/packager.mk#828
Component: Release Engineering: Automation (General) → Build Config
Product: mozilla.org → Core
QA Contact: catlee
Version: other → Trunk
The generic problem here is we invoke setup.py from the source dir. Currently, only psutil is using setup.py IIRC. I'd definitely like to see virtualenv/Python foo not create files in the source dir. It's possibly worth opining a meta bug for that.

Updated

3 months ago
Blocks: 1380405
You need to log in before you can comment on or make changes to this bug.