Bug 442380 - TypeError: sequence item 0: expected string, tuple found
TypeError: sequence item 0: expected string, tuple found
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
rawhide
All Linux
low Severity low
: ---
: ---
Assigned To: Seth Vidal
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-04-14 12:16 EDT by Nicolas Chauvet (kwizart)
Modified: 2008-04-14 21:47 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-04-14 15:39:51 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
anaconda fails installing F-9 xen guest i386 on F-8 x86_64 (51.93 KB, text/plain)
2008-04-14 12:17 EDT, Nicolas Chauvet (kwizart)
no flags Details

  None (edit)
Description Nicolas Chauvet (kwizart) 2008-04-14 12:16:04 EDT
Description of problem: I'm trying to install Rawhide i386 as a xen guest from
F-8 x86_64
The install fails somewhere before the dependencies resolution (after choosing
some packages from the KDE set, but the default set of package will make the
install to fail also.)



Version-Release number of selected component (if applicable):
last anaconda to date anaconda-11.4.0.71-1


How reproducible: Always


Steps to Reproduce: Install Rawhide as a xen guest
1.
2.
3.
  
Actual results:
the anaconda fails with :
TypeError: sequence item 0: expected string, tuple found
see the attached complete log


Expected results:


Additional info: The French keyboard wasn't properly detected (it was with
previous anaconda version but xen virtual fb wasn't).
Comment 1 Nicolas Chauvet (kwizart) 2008-04-14 12:17:20 EDT
Created attachment 302359 [details]
anaconda fails installing F-9 xen guest i386 on F-8 x86_64
Comment 2 Jeremy Katz 2008-04-14 14:56:19 EDT
I think this is fixed up with the patch that Seth has brought in to yum earlier,
but I'm not 100% sure
Comment 3 Seth Vidal 2008-04-14 15:39:51 EDT
yes, it's been corrected upstream
Comment 4 Nicolas Chauvet (kwizart) 2008-04-14 21:47:00 EDT
I'm not sure...

If you mean a good testing case would be to download the newest yum
recreate the local repo with createrepo  -c ../cache/ -d -g repodata/comps.xml .
And test again... Then it fails with the same error.

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