Bug 250037

Summary:	yum INFO / CLEAN ALL error
Product:	[Fedora] Fedora	Reporter:	Ric <cras9_3>
Component:	yum	Assignee:	Jeremy Katz <katzj>
Status:	CLOSED NEXTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	7	CC:	james.antill
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-07-30 02:04:01 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ric 2007-07-29 22:44:39 UTC

Description of problem:
yum is unable of cleaning the headers of livna, but it does fine with the rest
(packages, metadata, dbcache, plugins), so the command "yum clean all, and yum
clean headers" get stuck


Version-Release number of selected component (if applicable):
yum-3.2.1-1.fc7

How reproducible:
always

Steps to Reproduce:
[crash@psilocybe ~]$ su -c 'yum clean all'
Contrase�a:
Loading "installonlyn" plugin
Cleaning up Everything
Error: Error accessing directory //var/cache/yum/livna/headers, [Errno 2] No
existe el fichero o el directorio: '//var/cache/yum/livna/headers'
[crash@psilocybe ~]$ su -c 'yum clean headers'
Contrase�a:
Loading "installonlyn" plugin
Error: Error accessing directory //var/cache/yum/livna/headers, [Errno 2] No
existe el fichero o el directorio: '//var/cache/yum/livna/headers'
[crash@psilocybe ~]$
  

Additional info:

http://bugzilla.livna.org/show_bug.cgi?id=1576

I did
su -c 'mkdir //var/cache/yum/livna/headers'
and fix the issue but them, not sure if this is related (watch the final lines):

[crash@psilocybe ~]$ yum info vino
Loading "installonlyn" plugin
Installed Packages
Name   : vino
Arch   : i386
Version: 2.18.0
Release: 1.fc7
Size   : 1.4 M
Repo   : installed
Summary: Un sistema de escritorio remoto para GNOME

Traceback (most recent call last):
  File "/usr/bin/yum", line 29, in <module>
    yummain.main(sys.argv[1:])
  File "/usr/share/yum-cli/yummain.py", line 94, in main
    result, resultmsgs = base.doCommands()
  File "/usr/share/yum-cli/cli.py", line 266, in doCommands
    return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd,
self.extcmds)
  File "/usr/share/yum-cli/yumcommands.py", line 164, in doCommand
    base.listPkgs(ypl.installed, 'Installed Packages', basecmd)
  File "/usr/share/yum-cli/output.py", line 102, in listPkgs
    self.infoOutput(pkg)
  File "/usr/share/yum-cli/output.py", line 73, in infoOutput
    print _("Description:\n%s") % pkg.description.encode("UTF-8")
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 87: ordinal
not in range(128)

[crash@psilocybe ~]$ su -c 'yum clean all'
Contrase�a:
Loading "installonlyn" plugin
Cleaning up Everything
[crash@psilocybe ~]$ yum info vino
Loading "installonlyn" plugin
Error: Cannot open/read repomd.xml file for repository: livna
[crash@psilocybe ~]$

Comment 1 Seth Vidal 2007-07-30 02:04:01 UTC

These are two separate bugs but both of them have been fixed in yum 3.2.2. It is
available in updates-testing. Please test it and report back if your issues are
fixed.

Comment 2 Ric 2007-07-30 02:49:56 UTC

(In reply to comment #1)
> These are two separate bugs but both of them have been fixed in yum 3.2.2. It is
> available in updates-testing. Please test it and report back if your issues are
> fixed.

I installed yum 3.2.2 as suggested, "yum info package" is working again. "But"
if you do:

[crash@psilocybe ~]$ su -c 'yum clean all'
Contraseña:
Cleaning up Everything
[crash@psilocybe ~]$ yum info vino
Error: Cannot open/read repomd.xml file for repository: livna
[crash@psilocybe ~]$

It will work fine again after "yum update" (even when "No Packages marked for
Update/Obsoletion") but not sure if this is the way it should work.

Comment 3 Seth Vidal 2007-07-30 03:12:27 UTC

yes, that's correct behavior. If you run as a user and there is no metadata
available it won't be able to carry out your command b/c it cannot access the
information.

Comment 4 Ric 2007-07-30 03:34:34 UTC

(In reply to comment #3)
> yes, that's correct behavior. If you run as a user and there is no metadata
> available it won't be able to carry out your command b/c it cannot access the
> information.

Then,the issues are solved, yum 3.2.2 has fixed the bug, and I confirm is
working correctly. Good job and thx for the help.