Bug 1299494

Summary: Env variables are not set for --new-chroot
Product: [Fedora] Fedora Reporter: Vít Ondruch <vondruch>
Component: mockAssignee: Miroslav Suchý <msuchy>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: jdisnard, mebrown, msimacek, msuchy, praiskup, williams
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-02 14:31:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Vít Ondruch 2016-01-18 14:01:15 UTC 
Description of problem:
$ cat /etc/mock/cucos.cfg | grep RUBYOPT
config_opts['environment']['RUBYOPT'] = '-I/builddir/gem-cucos/lib/'

$ mock -r cucos shell --old-chroot
<mock-chroot>sh-4.3# env | grep RUBYOPT
RUBYOPT=-I/builddir/gem-cucos/lib/

$ mock -r cucos shell --new-chroot
sh-4.3# env | grep RUBYOPT





Version-Release number of selected component (if applicable):
$ rpm -q mock
mock-1.2.14-1.fc24.noarch


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
$ mock -r cucos shell --new-chroot
sh-4.3# env | grep RUBYOPT

Expected results:
$ mock -r cucos shell --new-chroot
sh-4.3# env | grep RUBYOPT
RUBYOPT=-I/builddir/gem-cucos/lib/


Additional info:
Comment 1 Vít Ondruch 2016-01-18 14:08:21 UTC 
Please note that --unpriv should be reflected as well.
Comment 2 Jan Kurik 2016-02-24 14:18:07 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
Comment 3 Miroslav Suchý 2016-06-02 14:31:31 UTC 
This has been fixed in bug 1311796

*** This bug has been marked as a duplicate of bug 1311796 ***