Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 160328 - depresolve backtrace
Summary: depresolve backtrace
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-06-14 14:34 UTC by Jef Spaleta
Modified: 2014-01-21 22:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-06-14 15:21:17 UTC


Attachments (Terms of Use)

Description Jef Spaleta 2005-06-14 14:34:43 UTC
Description of problem:
yum-2.3.2-7

Okay i realize now that this is a dumb thing to do without using quotes.
But this is tracing back so clearly the protectfromidiotuser() function needs a
little love.

yum resolvedep kernel-devel-i686 = 2.6.11-1.1369_FC4smp
Searching Packages for Dependency:
Setting up repositories
Reading repository metadata in from local files
0:kernel-devel-2.6.11-1.1381_FC5.i686
Traceback (most recent call last):
  File "/usr/bin/yum", line 15, in ?
    yummain.main(sys.argv[1:])
  File "/usr/share/yum-cli/yummain.py", line 72, in main
    result, resultmsgs = do()
  File "/usr/share/yum-cli/cli.py", line 545, in doCommands
    return self.resolveDepCli()
  File "/usr/share/yum-cli/cli.py", line 1151, in resolveDepCli
    pkg = self.returnPackageByDep(arg)
  File "__init__.py", line 1217, in returnPackageByDep
ValueError: need more than 1 value to unpack

Comment 1 Seth Vidal 2005-06-14 15:21:17 UTC
Thanks, Fixed upstream.

it won't resolve that dep b/c it is unquoted but now it doesn't traceback, it
treats that as 3 strings to resolve.




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