From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020314 Description of problem: running up2date (alone, with -u, or with --configure, etc.) fails to run. Same outcome in X or CLI (with or without rhn_register run first) - ouputs: [root@localhost root]# up2date Traceback (innermost last): File "/usr/sbin/up2date", line 16, in ? from up2date_client import clap ImportError: cannot import name clap Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Fresh skipjack install (on new drive) 2. run up2date Actual Results: Traceback (innermost last): File "/usr/sbin/up2date", line 16, in ? from up2date_client import clap ImportError: cannot import name clap [then returned to prompt] Expected Results: A good up2date run, checking RedHat for updates to the Skipjack beta1 system. Additional info: Dell Inspiron 4100
Created attachment 49904 [details] Fix for up2date problem
Created attachment 49905 [details] Fix for up2date problem
code fixed in cvs, should be in next release. (2.7.62)
*** Bug 61947 has been marked as a duplicate of this bug. ***
This should be fixed in versions 2.7.61 or higher.
*** Bug 62185 has been marked as a duplicate of this bug. ***
*** Bug 62242 has been marked as a duplicate of this bug. ***
I am not sure why this is CLOSED since the bug is still in : up2date-2.7.65-7.x.3 rpm-python-4.0.4-7x.9 python-clap-1.0.0-2 clap.py is NOT in the up2date directory AND it looks for up2datepopt which is NOT supplied by any package!
The bug is fixed, the versions in rawhide arent quite new enough. Nothing should be looking for up2datepopt in current versions. Sounds like rawhide is kind of busted. It will look for python-popt first, and then up2date-popt, sounds like it's not finding python-popt (and looking at that version of the package, it's missing the dep on python-popt). Install python-popt and it should be fine. The new version of the package will require python-popt. reassigning to a python-clap bug.
*** Bug 62316 has been marked as a duplicate of this bug. ***
This is fine on my fresh install from our internal trees