Bug 235614 - brp-java-repack-jars redefines TMPDIR while using mktemp
brp-java-repack-jars redefines TMPDIR while using mktemp
Product: Fedora
Classification: Fedora
Component: redhat-rpm-config (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jon Masters
: EasyFix
Depends On:
Blocks: 244899
  Show dependency treegraph
Reported: 2007-04-07 22:35 EDT by Matthew Miller
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-06-19 14:17:21 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 Matthew Miller 2007-04-07 22:35:57 EDT
Description of problem:

mktemp uses the TMPDIR environment variable. The brp-java-repack-jars script
resets TMPDIR to arbitrary values that don't necessarily exist, and then tries
to use mktemp. Failures ensue.

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


How reproducible:


Steps to Reproduce:
1. try to build, for example, a jpackage.org nosrc rpm
2. watch it not work.
3. there is no step three.
Actual results:

it fails with an error message about a temporary directory not existing.

Expected results:

it shouldn't be looking there anyway

Additional info:

replace all instances of TMPDIR in this script with something like JTMPDIR and
the problem is solved
Comment 1 Matthew Miller 2007-06-11 16:01:35 EDT
This is still a problem in current Fedora Rawhide (pre-f8, at this point), and
in RHEL5. It's an easy fix -- please make it.
Comment 2 Jeremy Katz 2007-06-19 14:17:21 EDT
Push will be fixed for rawhide later today  
Comment 3 Matthew Miller 2007-06-19 14:19:28 EDT
Thanks man. 
Comment 4 Matthew Miller 2007-06-19 14:28:58 EDT
Also, this probably deserves to get put in an update for RHEL5 eventually.
Comment 5 Jon Masters 2007-06-19 14:51:59 EDT
Cloned as a RHEL5 bug.


Note You need to log in before you can comment on or make changes to this bug.