Bug 24940 – emerge -pf fails with python NameError

• Product: Portage Development
• Status: RESOLVED FIXED

[Description Shaun Cloherty 2003-07-20 20:30:44 UTC]

Just emerge sync'ed, and noticed a new version of portage has been released.
emerge portage updated to 2.0.48-r5 (on x86). I etc-update'd, and merged
/etc/make.conf and replaced /etc/make.globals. Now, 'emerge -fp' of anything
fails with a Python NameError: global name 'strict' is not defined. This is the
case with any package I have tried. I have tried with and without 'strict' in
FEATURES in /etc/make/conf.

'emerge -p packagename' and 'emerge -f packagename' work as expected.



Reproducible: Always
Steps to Reproduce:
1. emerge -pf distcc
2.
3.

Actual Results:  
root@SC-PIII shaunc # emerge -pf distcc
Calculating dependencies ...done!
 
http://mirror.aarnet.edu.au/pub/gentoo/distfiles/distcc-2.7.1.tar.bz2 
http://distcc.samba.org/ftp/distcc/distcc-2.7.1.tar.bz2
Traceback (most recent call last):
  File "/usr/bin/emerge", line 1951, in ?
    mydepgraph.merge(mydepgraph.altlist())
  File "/usr/bin/emerge", line 1176, in merge
    retval=portage.doebuild(y,"fetch",myroot,edebug,("--pretend" in
myopts),fetchonly=1)
  File "/usr/lib/python2.2/site-packages/portage.py", line 1734, in doebuild
    if not digestcheck(checkme, ("strict" in features)):
  File "/usr/lib/python2.2/site-packages/portage.py", line 1484, in digestcheck
    return digestCheckFiles(myfiles, mydigests, basedir, "src_uri")
  File "/usr/lib/python2.2/site-packages/portage.py", line 1402, in digestCheckFiles
    if strict:
NameError: global name 'strict' is not defined



Expected Results:  
root@SC-PIII shaunc # emerge -pf distcc
Calculating dependencies ...done!
 
http://mirror.aarnet.edu.au/pub/gentoo/distfiles/distcc-2.7.1.tar.bz2
http://distcc.samba.org/ftp/distcc/distcc-2.7.1.tar.bz2

[Comment 1 Nicholas Jones (RETIRED) 2003-07-21 23:35:50 UTC]

:-/

Fixed for 48-r6